Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id OAA07823 for ; Sat, 8 Apr 2000 14:06:09 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id OAA06104; Sat, 8 Apr 2000 14:05:37 -0400 (EDT) To: Henk van Lingen cc: pgsql-interfaces@postgresql.org Subject: Re: ODBC and crypted passwords In-reply-to: References: Comments: In-reply-to Henk van Lingen message dated "Sat, 08 Apr 2000 16:35:13 +0200" Date: Sat, 08 Apr 2000 14:05:37 -0400 Message-ID: <6101.955217137@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200004/49 Henk van Lingen writes: > I'm playing with the ODBC driver (which works fine) but I like passwords > to travel encrypted, which is not supported at the moment. > Is there any work being done on this? The TODO says (in 1998) that the > priority is low. Why is that? I think that just means that Bryan doesn't care about it very much ;-). If you do, step right up and submit a patch. The way things work around here is that tasks get done when someone is motivated enough to do them. > 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?) regards, tom lane