Received: from me.tm.ee (ppp109.tele2.ee [212.107.33.109])
	by hub.org (8.9.3/8.9.3) with ESMTP id GAA63884
	for <pgsql-interfaces@postgresql.org>;
	Wed, 12 Apr 2000 06:49:26 -0400 (EDT) (envelope-from hannu@tm.ee)
Received: from tm.ee (IDENT:hannu@localhost.localdomain [127.0.0.1])
	by me.tm.ee (8.9.3/8.9.3) with ESMTP id MAA01741;
	Wed, 12 Apr 2000 12:46:51 +0300
Message-ID: <38F4460B.CBC6909B@tm.ee>
Date: Wed, 12 Apr 2000 12:46:51 +0300
From: Hannu Krosing <hannu@tm.ee>
X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.12-20 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Peter Mount <petermount@it.maidstone.gov.uk>
CC: "'Henk van Lingen'" <henkvl@cs.uu.nl>, pgsql-interfaces@postgresql.org
Subject: Re: ODBC and crypted passwords
References: 
 <1B3D5E532D18D311861A00600865478C70C446@exchange1.nt.maidstone.gov.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200004/80

Peter Mount wrote:
> 
> One thing that may be useful, is not to check against the unix password
> file, but to use PAM. That way, you could even authenticate against the
> dreadded NT accounts, unix password file, dbm file etc...
> 
> Anyhow, this is something to think about for the future ;-)

IMHO this defeats the purpose of crypt - not to send plaintext passwords 
over the net.

OTOH, it could be done over a secure (SSL/TLS) channel of course.

-----------
Hannu