Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f74ISp672944 for ; Sat, 4 Aug 2001 14:28:51 -0400 (EDT) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.10.1/8.10.1) id f74ISPJ13625; Sat, 4 Aug 2001 14:28:25 -0400 (EDT) From: Bruce Momjian Message-Id: <200108041828.f74ISPJ13625@candle.pha.pa.us> Subject: Re: Differences in crypt hash? In-Reply-To: <29263.996944702@sss.pgh.pa.us> "from Tom Lane at Aug 4, 2001 01:05:02 pm" To: Tom Lane Date: Sat, 4 Aug 2001 14:28:25 -0400 (EDT) CC: Richard Hodges , pgsql-docs@postgresql.org X-Mailer: ELM [version 2.4ME+ PL90 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200108/3 X-Sequence-Number: 890 > Richard Hodges writes: > > The problem is that my Solaris client does not authenticate against > > my server (7.0.3 built on FreeBSD). > > Indeed, one of the nasty things about the 'crypt' authentication method > is that it assumes the crypt() library call acts the same on both client > and server machine. As you've just discovered, that ain't always so. > > There have been plans for some time to supersede our present password > auth methods with something more secure and portable (probably MD5 > double hashing at both ends). I think Vince V. is working on that, > but I've not heard anything about it lately. You can read all about it > in the pghackers mail archives if you care. I am trying to get it done for 7.2. I have Vince's md5 code. I just need to plug it into the authentication code. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026