From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Jeff MacDonald <jeff(at)hub(dot)org> |
Cc: | pgsql-general(at)hub(dot)org |
Subject: | Re: [GENERAL] cgi with postgres |
Date: | 2000-01-15 00:15:07 |
Message-ID: | Pine.BSF.4.21.0001142014370.46499-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, 14 Jan 2000, Jeff MacDonald wrote:
> hey folks,
>
> this is a security issue i'd like to get some info
> on, i'm sure it's more with cgi than postgres, but
> heck.
>
> issue: how to secure cgi's that access postgres
>
> problem: passwords for postgres database are stored
> in plain text in scripts. (lets assume, perl,
> not a compiled language)
>
> points:
> make cgi dir 711
> big deal, they can get the name of the file
> from the web, and copy it.
>
> set an obscure cgi script alias in apache
> big deal, they can read the cgi conf file.
Side point ... why isn't the apache conf file secure? Only user root
needs to be able to read it, no?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Burrows | 2000-01-15 00:35:43 | More Rule creation problems (and nowhere near 8K) |
Previous Message | Kevin Heflin | 2000-01-14 23:08:27 | problem with date range |