[Dbconfig-common-devel] Why does dbconfig-common use a none exiting local user

[sean finney]

hi karsten,

On Wed, Jan 18, 2006 at 11:09:16PM +0100, Karsten Hilbert wrote:
> > "out of the box": "password" and "ident" -based authentication.
> ... but maybe not "out of the box"

i was referring to the default postgres configuration for debian
systems, which i believe support local ident and local/remote
password based authentication.  there's certainly more of course,
but from a dbc perspective we're currently only concerned with :

- whether a password is required
- whether we need to run code as a specific local user

and the psql utility takes care of the rest.

> To make a long story short: the dbc default should be to
> supply a password and not worry about whether it is needed
> or not. If it isn't needed it isn't used.

that's an interesting idea i hadn't considered.  it'd clean up the
code a bit, anyway :)

in any case, i'm thinking about changing the default pgsql behavior to
use passwords instead of ident, as it's far more common for the former.
this would solve uwe's issue for the time being, and i could think a bit
more about how to support overriding it later.


	sean

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/attachments/20060119/11ffa61f/attachment.pgp