From: Josh Close <narshe@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: protocol, md5 authentication
Date: Wed, 22 Feb 2006 11:11:23 -0600
Message-ID: <4a0cafe20602220911n15c1e01eo1c8e11f39653ae3c@mail.gmail.com> (raw)
In-Reply-To: <12762.1140626935@sss.pgh.pa.us>
References: <4a0cafe20602220622g77666533k7564b439e83ce55@mail.gmail.com>
<12762.1140626935@sss.pgh.pa.us>
>
> 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 need
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: narshe@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: protocol, md5 authentication
In-Reply-To: <4a0cafe20602220911n15c1e01eo1c8e11f39653ae3c@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox