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 A2EBE9DC99D for ; Wed, 22 Feb 2006 13:11:27 -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 46885-08 for ; Wed, 22 Feb 2006 13:11:26 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.203]) by postgresql.org (Postfix) with ESMTP id A0C3D9DC93E for ; Wed, 22 Feb 2006 13:11:24 -0400 (AST) Received: by uproxy.gmail.com with SMTP id m3so796576ugc for ; Wed, 22 Feb 2006 09:11:24 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=ebDwmkRj5jolVqgN7gE5lRCtOs9Kl46OcivMGSCIfI5BOs6/Ufhp0H4UEchtiTc3KeAk5Kpps+ui2gklhF/hd/sXUiCP6qnbTiwE4KCE77PJpEiOvOlfw4Rel7esiexN56XgFisBst4tosUzTL8EA0Hy/OLj6TMbir37YztkS6E= Received: by 10.66.234.20 with SMTP id g20mr2700772ugh; Wed, 22 Feb 2006 09:11:23 -0800 (PST) Received: by 10.66.224.11 with HTTP; Wed, 22 Feb 2006 09:11:23 -0800 (PST) Message-ID: <4a0cafe20602220911n15c1e01eo1c8e11f39653ae3c@mail.gmail.com> Date: Wed, 22 Feb 2006 11:11:23 -0600 From: "Josh Close" To: "Tom Lane" Subject: Re: protocol, md5 authentication Cc: pgsql-interfaces@postgresql.org In-Reply-To: <12762.1140626935@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1293_28985855.1140628283718" References: <4a0cafe20602220622g77666533k7564b439e83ce55@mail.gmail.com> <12762.1140626935@sss.pgh.pa.us> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.442 required=5 tests=[AWL=0.441, HTML_MESSAGE=0.001] X-Spam-Score: 0.442 X-Spam-Level: X-Archive-Number: 200602/74 X-Sequence-Number: 6038 ------=_Part_1293_28985855.1140628283718 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > > 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. > I'm connecting via a socket and using Postgres protocol version 3. I'll nee= d to encrypt all that myself then. I must have made a mistake somewhere else in my code, because I think I'm doing the encryption write from what James said in his reply about his python method. -Josh ------=_Part_1293_28985855.1140628283718 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
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
y= ou.  You certainly do not hand in a pre-encrypted password or any= thing
like that.

I'm connecting via a socket a= nd using Postgres protocol version 3. I'll need to encrypt all that myself = then.

I must have made a mistake somewhere else in my code, because I thi= nk I'm doing the encryption write from what James said in his reply about h= is python method.

-Josh
------=_Part_1293_28985855.1140628283718--