To: Magnus Hagander <mha@sollentuna.net>
cc: Henk van Lingen <henkvl@cs.uu.nl>, pgsql-interfaces@postgresql.org
Subject: Re: ODBC and crypted passwords 
In-reply-to: 
 <215896B6B5E1CF11BC5600805FFEA82103046150@sirius.edu.sollentuna.se>
References: 
 <215896B6B5E1CF11BC5600805FFEA82103046150@sirius.edu.sollentuna.se>
Comments: In-reply-to Magnus Hagander <mha@sollentuna.net>
	message dated "Sun, 09 Apr 2000 19:15:52 +0200"
Date: Sun, 09 Apr 2000 13:31:10 -0400
Message-ID: <9661.955301470@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Magnus Hagander <mha@sollentuna.net> writes:
>>>> Is there something which makes a 'crypt' implementation hard?
>> 
>> I imagine the problem is that he doesn't want to depend on the 'crypt'
>> library, which is standard on Unixen but not (AFAIK) on Windows.
>> Otherwise it'd be easy to transpose libpq's code into the odbc driver.
>> (OTOH, I believe there are ports of libpq for Windows, so 
>> maybe crypt() is available there?  Anyone know?)

> Actually, the crypt()ed authentication is not supported on libpq for Win32.
> I meant to do this, but I had completely forgotten... 

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...)

			regards, tom lane