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 D9885D919E for ; Fri, 23 Sep 2005 12:32:33 -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 00222-02 for ; Fri, 23 Sep 2005 15:32:31 +0000 (GMT) Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id DAB19D917C for ; Fri, 23 Sep 2005 12:32:29 -0300 (ADT) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 23 Sep 2005 10:32:28 -0500 Subject: Re: alter user From: Scott Marlowe To: wim.bertels@khleuven.be Cc: pgsql-admin@postgresql.org In-Reply-To: <200509230232.58668.wim.bertels@khleuven.be> References: <200509230232.58668.wim.bertels@khleuven.be> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1127489548.30825.90.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Fri, 23 Sep 2005 10:32:28 -0500 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200509/272 X-Sequence-Number: 19009 On Thu, 2005-09-22 at 19:32, Wim Bertels wrote: > On Friday 23 September 2005 01:51, Scott Marlowe seinde rooksignalen: > > Instead of using a general purpose account, why not give everyone an > > account, then make them a member of a group, and give that group the > > access. > > > > That way you can easily add / remove people from the group instead of > > trying to do it this way. > > not an option, its for scripting and testing purposes I don't see why my method(s) excludes scripting and testing. > > > > Otherwise, don't use a password, set the machine to use trust or ident or > > something like that where a password wouldn't matter. > > although it is then a user/pasword known by a lot of people, > it is still beter than no password No, it really isn't. Once everyone (or a large enough subset of everyone) knows the password, it's no better than an account that can log in without one. If it's a generic read only account with the same name as the database, give it select only permission, and add a line like this: host sameuser all 10.1.1.1 255.255.255.0 trust where the 10.1.1.1 / 255.255.255.0 are replaced with the appropriate mask to let your test machines log in. Put the host / md5 lines after this one for the same line but with all in place of sameuser and you're gold.