Re: server authentication over Unix-domain sockets - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: server authentication over Unix-domain sockets
Date
Msg-id 20100611120726.GP21875@tamriel.snowman.net
Whole thread Raw
In response to server authentication over Unix-domain sockets  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: server authentication over Unix-domain sockets  (Magnus Hagander <magnus@hagander.net>)
Re: server authentication over Unix-domain sockets  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
* Peter Eisentraut (peter_e@gmx.net) wrote:
> The patch needs some portability work and possible refactoring because
> of that, but before I embark on that, comments on the concept?

I definitely like the idea but I dislike requiring the user to do
something to implement it.  Thinking about how packagers might want to
use it, could we make it possible to build it defaulted to a specific
value (eg: 'postgres' on Debian) and allow users a way to override
and/or unset it?

Having the option wouldn't do much unless users know of it and use it
and it strikes that will very often not be the case.

I'm impartial towards whatever PG wants to do with the default, just so
long as packagers can override it and set it to something specific.
Also, to that end, it's got to be name-based.  Exim in Debian did
something similar and actually tried to force a particular UID..  that
was horrid. :)  On Debian, at least, the user is almost always
'postgres', but the UID will vary depending on exactly when the packages
were installed (before or after other system-user-creating packages).
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Functional dependencies and GROUP BY
Next
From: Magnus Hagander
Date:
Subject: Re: server authentication over Unix-domain sockets