By the way,
I've already implemented this in phpPgAdmin trivially using the md5()
function. I can't be bothered using a C library function :D
Dave Page wrote:
>>From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>>Sent: 19 December 2005 05:37
>>To: Christopher Kings-Lynne
>>Cc: Peter Eisentraut; pgsql-hackers(at)postgresql(dot)org; Andreas
>>Pflug; Dave Page
>>Subject: Re: [HACKERS] [pgadmin-hackers] Client-side password
>>Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
>>>>So it appears that pg_md5_encrypt is not officially
>>exported from libpq.
>>>>Does anyone see a problem with adding it to the export
>>list and the
>>>Is it different to normal md5? How is this helpful to the
>>It would be better to export an API that is (a) less random (why one
>>input null-terminated and the other not?) and (b) less tightly tied
>>to MD5 --- the fact that the caller knows how long the result must be
>>is the main problem here.
>> char *pg_gen_encrypted_passwd(const char *passwd, const
>>with malloc'd result (or NULL on failure) seems more future-proof.
> Changing the API is likely to cause fun on Windows for new apps that
> find an old libpq.dll. Perhaps at this point it should become
> Regards, Dave.
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
In response to
pgsql-hackers by date
|Next:||From: Alvaro Herrera||Date: 2005-12-20 02:01:58|
|Subject: Re: [pgadmin-hackers] Client-side password encryption|
|Previous:||From: Albert Chin||Date: 2005-12-19 23:41:28|
|Subject: Re: Trouble building 8.1.1 on Tru64 UNIX 5.1|