Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 79C00475DBD for ; Fri, 29 Nov 2002 13:43:04 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id C5163475D0F for ; Fri, 29 Nov 2002 13:43:03 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id gATIgvsX027855; Fri, 29 Nov 2002 13:42:57 -0500 (EST) To: Mitch Vincent Cc: pgsql-interfaces@postgresql.org Subject: Re: libpq / crypt / md5 question In-reply-to: <01345636-03C4-11D7-A869-0003938024CA@doot.org> References: <01345636-03C4-11D7-A869-0003938024CA@doot.org> Comments: In-reply-to Mitch Vincent message dated "Fri, 29 Nov 2002 10:57:19 -0700" Date: Fri, 29 Nov 2002 13:42:57 -0500 Message-ID: <27854.1038595377@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200211/159 X-Sequence-Number: 3407 Mitch Vincent 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