Received: from henry.newn.cam.ac.uk (henry.newn.cam.ac.uk [131.111.204.130]) by hub.org (8.9.3/8.9.3) with ESMTP id FAA39607 for ; Mon, 10 Apr 2000 05:36:14 -0400 (EDT) (envelope-from prlw1@newn.cam.ac.uk) Received: from [131.111.204.180] (helo=quartz.newn.cam.ac.uk) by henry.newn.cam.ac.uk with esmtp (Exim 3.13 #1) id 12eacF-0002Yg-00 for pgsql-interfaces@postgresql.org; Mon, 10 Apr 2000 10:36:19 +0100 Received: from prlw1 by quartz.newn.cam.ac.uk with local (Exim 3.13 #1) id 12eac9-0000Gq-00 for pgsql-interfaces@postgresql.org; Mon, 10 Apr 2000 10:36:13 +0100 Date: Mon, 10 Apr 2000 10:36:13 +0100 From: Patrick Welche To: pgsql-interfaces@postgresql.org Subject: Re: ODBC and crypted passwords Message-ID: <20000410103613.D1005@quartz.newn.cam.ac.uk> Reply-To: prlw1@cam.ac.uk References: <9661.955301470@sss.pgh.pa.us> <200004092022.QAA09151@averstak.campus.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i In-Reply-To: <200004092022.QAA09151@averstak.campus.vt.edu>; from averstak@vt.edu on Sun, Apr 09, 2000 at 04:22:58PM -0400 X-Archive-Number: 200004/54 On Sun, Apr 09, 2000 at 04:22:58PM -0400, Alex Verstak wrote: > > Tom Lane wrote: > > Hmm. Can we find a freely-distributable version of libcrypt anywhere? > > > > (Actually, now that I think about it, I'm not entirely sure that crypt() > > implements exactly the same transformation on every Unix platform. > > It may be that you have to have a version of crypt() that matches the > > one on your server's platform. That would be a pain in the neck ... > > but if we did find an open-source libcrypt, maybe we could standardize > > on using it in preference to vendor crypts...) > > I have no problem running the PostgreSQL server on Solaris and > using a FreeBSD client with crypt authentication. Both systems > use DES. Problems arise when systems try to work around the US > export restrictions and supply MD5 or other weak encryption. > > For the same reason, you cannot make strong authentication code > available on your website. The best you can do is provide > a pointer to some DES implementation outside the US and instruct > users to download and use this one if their systems do not work > together. Another alternative is to include MD5 in the distribution, > but use the system crypt by default, with a configuration option > to switch to MD5. I wonder whether SASL http://asg.web.cmu.edu/sasl/ is worth considering. AFAICT postgresql would say authenticate userid,password,mechanism, and sasl replies yes or no, and different mechanisms seem to plug in reasonably cleanly. Cheers, Patrick