From: John Tobey <[EMAIL PROTECTED]>
Date: Sun, 2 Mar 2003 13:04:22 -0500
On Sun, Mar 02, 2003 at 12:26:40PM -0500, Bob Rogers wrote:
> In a nutshell, I use the PostgreSQL "ident" authentication feature,
> and restrict access to the DB server to connections coming from the
> loopback address. This has the distinct advantage of making a password
> unnecessary: Since the DB server can securely and reliably query the
> name of the user who makes the incoming connection, each user must first
> prove who they are to the OS's satisfaction, and then the DB server can
> confidently grant access to that DB user account, and no other.
But the name of the user is "www" and is not a trusted account, since
other users can write code that runs as www too. Only the script
ownership is trustworthy.
As I said in the paragraph before the one you quote,
[This] doesn't help with Joel's original problem, since it requires
separate UIDs for separate servers
But if you can change UID safely with suExec or cgiwrap, then that would
work just as well.
-- Bob
_______________________________________________
Boston-pm mailing list
[EMAIL PROTECTED]
http://mail.pm.org/mailman/listinfo/boston-pm
