X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id A1FDC9DC850 for ; Wed, 8 Feb 2006 17:37:12 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 60521-01 for ; Wed, 8 Feb 2006 17:37:13 -0400 (AST) X-Greylist: delayed 01:23:31.902602 by SQLgrey- Received: from post5.inre.asu.edu (post5.inre.asu.edu [129.219.110.120]) by postgresql.org (Postfix) with ESMTP id 45E2F9DC815 for ; Wed, 8 Feb 2006 17:37:10 -0400 (AST) Received: from conversion.post5.inre.asu.edu by asu.edu (PMDF V6.1-1X6 #30769) id <0IUD00401XGFC2@asu.edu> for pgsql-admin@postgresql.org; Wed, 08 Feb 2006 13:12:15 -0700 (MST) Received: from smtp.asu.edu (smtp.asu.edu [129.219.110.107]) by asu.edu (PMDF V6.1-1X6 #30769) with ESMTP id <0IUD002SJXGF0B@asu.edu> for pgsql-admin@postgresql.org; Wed, 08 Feb 2006 13:12:15 -0700 (MST) Received: from teancum.pp.asu.edu (teancum.pp.asu.edu [129.219.69.212]) by smtp.asu.edu (8.12.10/8.12.10/asu_smtp_relay, nullclient, tcp_wrapped) with ESMTP id k18KCEj5029428 for ; Wed, 08 Feb 2006 13:12:14 -0700 (MST) Received: by teancum.pp.asu.edu (Postfix, from userid 1000) id AA81FE7E; Wed, 08 Feb 2006 13:12:14 -0700 (MST) Date: Wed, 08 Feb 2006 13:12:14 -0700 From: David Bear Subject: auth methods To: pgsql-admin@postgresql.org Reply-to: David.Bear@asu.edu Message-id: <20060208201214.GC21865@asu.edu> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.36 required=5 tests=[AWL=-0.120, DNS_FROM_RFC_ABUSE=0.479, UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.36 X-Spam-Level: X-Archive-Number: 200602/85 X-Sequence-Number: 20506 after reading through http://www.postgresql.org/docs/8.0/static/auth-methods.html I'm still left wondering how to solve something that should be simple. Ident method looks like it might work. All I really want to do is prevent user jack, who is logged in and properly authenticated to the system as jack, from connecting to pg as user joe. I have kerb authentication working for all ssh connections to the data base server. I don't want another layer of authentication for postgresql. I'm currently using the trust method, but any user can connect to pg as any other pg user. the trouble is that ident seems to be non existent in suse linux (at least, it doesn't seem to be installed ) any pointers would be appreciated. -- David Bear phone: 480-965-8257 fax: 480-965-9189 College of Public Programs/ASU Wilson Hall 232 Tempe, AZ 85287-0803 "Beware the IP portfolio, everyone will be suspect of trespassing"