From: Jason Stone <pgsql-admin@dfmm.org>
To: pgsql-admin@postgresql.org
Subject: Re: password authentication with external passwd file
Date: Mon, 29 Aug 2005 17:49:31 -0700 (PDT)
Message-ID: <20050829174059.F2358@treehorn.dfmm.org> (raw)
In-Reply-To: <20050827133049.GA59344@winnie.fuhr.org>
References: <20050827001001.L70885@treehorn.dfmm.org>
<20050827133049.GA59344@winnie.fuhr.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>> I would like to know first, if I'm mistaken, or if external passwd files
>> are now specified in some other way, or must be enabled at compile time or
>> something like that; ie, am I doing something wrong?
>
> The 7.3 Release Notes have the following items:
>
> * Remove secondary password file capability and pg_password utility (Bruce)
> * Add variable db_user_namespace for database-local user names (Bruce)
> [...]
> See the documentation for db_user_namespace:
hm. well, I can probably hack this to work, but I notice that the
documentations also says:
Note: This feature is intended as a temporary measure until a
complete solution is found. At that time, this option will be
removed.
so... how temporary is temporary? is it expected that the complete
solution will be at all similar? I don't want to spend a lot of time
building on this if the next upgrade will make it all obsolete again....
out of curiosity, why was the secondary password file capability removed?
I really liked the simplicity of being able to manage users completely
outside of the database, and to be able to do maintainence on the user
accounts without the database's even running.
anyway, thanks for the pointer - I'll start considering how I can use
db_user_namespace.
-Jason
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)
Comment: See https://private.idealab.com/public/jason/jason.gpg
iD8DBQFDE60bswXMWWtptckRAnGkAKDg96CVnZ55Oe0VANp2gDl1bojs5gCgltE4
2t985/6iyokjujrL9OUtHts=
=U30b
-----END PGP SIGNATURE-----
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: pgsql-admin@dfmm.org
Subject: Re: password authentication with external passwd file
In-Reply-To: <20050829174059.F2358@treehorn.dfmm.org>
References: <20050827001001.L70885@treehorn.dfmm.org> <20050827133049.GA59344@winnie.fuhr.org> <20050829174059.F2358@treehorn.dfmm.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox