From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mitch Vincent <mitch@doot.org>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: libpq / crypt / md5 question
Date: Fri, 29 Nov 2002 13:42:57 -0500
Message-ID: <27854.1038595377@sss.pgh.pa.us> (raw)
In-Reply-To: <01345636-03C4-11D7-A869-0003938024CA@doot.org>
References: <01345636-03C4-11D7-A869-0003938024CA@doot.org>
Mitch Vincent <mitch@doot.org> writes:
> On the client side, am I responsible for making the password an MD5
> hash, or does libpq take care of that on it's own?
libpq does it. This is necessary, since the client shouldn't be
expected to know which way the password is to be encrypted on the wire.
The password given to libpq must always be cleartext.
> It seems that courier can only connect to the PG database when the auth
> type is set to crypt in the pg_hba.conf file. This is somewhat strange
I suspect it means that courier is linked to an old version of libpq.
regards, tom lane
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: tgl@sss.pgh.pa.us, mitch@doot.org
Subject: Re: libpq / crypt / md5 question
In-Reply-To: <27854.1038595377@sss.pgh.pa.us>
* 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