Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f74H59654772 for ; Sat, 4 Aug 2001 13:05:09 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f74H52C29266; Sat, 4 Aug 2001 13:05:02 -0400 (EDT) To: Richard Hodges cc: pgsql-docs@postgresql.org Subject: Re: Differences in crypt hash? In-reply-to: References: Comments: In-reply-to Richard Hodges message dated "Fri, 03 Aug 2001 18:41:27 -0700" Date: Sat, 04 Aug 2001 13:05:02 -0400 Message-ID: <29263.996944702@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200108/2 X-Sequence-Number: 889 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. In the meantime, you'll just have to use a different auth method. Plain "password" would work. (If you're concerned about someone sniffing your TCP connection, consider using SSL.) regards, tom lane