X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id A07A59DC857 for ; Wed, 22 Feb 2006 12:49:00 -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 42915-07 for ; Wed, 22 Feb 2006 12:48:58 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id BFA6A9DC838 for ; Wed, 22 Feb 2006 12:48:57 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k1MGmtE2012763; Wed, 22 Feb 2006 11:48:55 -0500 (EST) To: "Josh Close" cc: pgsql-interfaces@postgresql.org Subject: Re: protocol, md5 authentication In-reply-to: <4a0cafe20602220622g77666533k7564b439e83ce55@mail.gmail.com> References: <4a0cafe20602220622g77666533k7564b439e83ce55@mail.gmail.com> Comments: In-reply-to "Josh Close" message dated "Wed, 22 Feb 2006 08:22:51 -0600" Date: Wed, 22 Feb 2006 11:48:55 -0500 Message-ID: <12762.1140626935@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.111 required=5 tests=[AWL=0.111] X-Spam-Score: 0.111 X-Spam-Level: X-Archive-Number: 200602/71 X-Sequence-Number: 6035 "Josh Close" writes: > I can't seem to get the md5 authentication to work with the postgres > protocol version 3. Define "work" --- what are you trying to do and what is happening? If you are using any of the standard client libraries such as libpq, the use of password encryption should be completely transparent to you. You certainly do not hand in a pre-encrypted password or anything like that. regards, tom lane