Re: [GENERAL] SHA1 on postgres 8.3 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [GENERAL] SHA1 on postgres 8.3
Date
Msg-id 5835.1207155914@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] SHA1 on postgres 8.3  (sanjay sharma <sanksh@hotmail.com>)
List pgsql-hackers
sanjay sharma <sanksh@hotmail.com> writes:
> md5 is not being recommended anywhere because it contains hash
> collision.

For the purposes we are using it for, that's just about 100% irrelevant.

> Would replacing md5 with SHA1 in core involve much work?

Yes, it would be a tremendous problem, because the use of md5 is part of
our password protocol.  We'd have to change client-side code in sync
with the servers to do that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [GENERAL] SHA1 on postgres 8.3
Next
From: PFC
Date:
Subject: Re: first time hacker ;) messing with prepared statements