From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Ken Tanzer <ken(dot)tanzer(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Disable executing external commands from psql? |
Date: | 2010-06-02 02:10:56 |
Message-ID: | 20100602021056.GY21875@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
* Ken Tanzer (ken(dot)tanzer(at)gmail(dot)com) wrote:
> OK one more question on this thread. It occurs to me that for the web
> app, DB username and password is read from a configuration file. (I
> understand this to be a common method for web applications.) But since
> apache needs to read the file, then all users can read each others'
> passwords. Arrghh. I'm just wondering how web hosters typically deal
> with this issue (or is your info for, say, Wordpress exposed to other
> users if they know where to look for it?) Sorry if this is too
> off-topic...
Have the username/password for each user site passed through
environment variables which are in the apache config file for the
virtual site they have access to the web root of. Then deny access to
the apache config files (the users don't really need access to it
anyway, and neither does www-data; apache will read them as root during
startup).
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2010-06-02 02:11:37 | Re: server-side extension in c++ |
Previous Message | John R Pierce | 2010-06-02 02:09:26 | Re: PosttgreSQL on AIX |