That's a poor situation, but pretty common. If you have suEXEC in effect, you can use filesystem permissions to guard the keys. Make a small private connection sub as I show below, give it 0600 permissions in a directory outside webspace. The user/pass pair is hidden in a closure from the rest of the program.

### file Myconnection.pl use DBI; { my $dsn = 'whatever'; my $user = 'joe'; my $pass = 'joe'; my $opts = { RaiseError => 1, AutoCommit => 0, }; sub myconnect () { DBI->connect($dbs, $user, $pass, $opts); } }

Usage:

use lib '/home/user/lib/perl5'; # or wherever use 'Myconnection.pl'; my $dbh = myconnect();

Without suEXEC, you will lack the filesystem protection, making this scheme much less viable.

After Compline,
Zaxo


In reply to Re: MySQL CGI Security by Zaxo
in thread MySQL CGI Security by Phemur

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.