X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 82332D8101 for ; Mon, 29 Aug 2005 21:49:32 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 53847-02 for ; Tue, 30 Aug 2005 00:49:29 +0000 (GMT) Received: from dfmm.org (treehorn.dfmm.org [66.180.195.213]) by svr1.postgresql.org (Postfix) with ESMTP id D3111D6E21 for ; Mon, 29 Aug 2005 21:49:27 -0300 (ADT) Received: (qmail 99128 invoked by uid 1000); 30 Aug 2005 00:49:31 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Aug 2005 00:49:31 -0000 Date: Mon, 29 Aug 2005 17:49:31 -0700 (PDT) From: Jason Stone X-X-Sender: jason@treehorn.dfmm.org To: pgsql-admin@postgresql.org Subject: Re: password authentication with external passwd file In-Reply-To: <20050827133049.GA59344@winnie.fuhr.org> Message-ID: <20050829174059.F2358@treehorn.dfmm.org> References: <20050827001001.L70885@treehorn.dfmm.org> <20050827133049.GA59344@winnie.fuhr.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 required=5 tests=[none] X-Spam-Level: X-Archive-Number: 200508/375 X-Sequence-Number: 18694 -----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-----