From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] SHA1 on postgres 8.3 |
Date: | 2008-01-20 18:47:12 |
Message-ID: | 47939730.1010802@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Martijn van Oosterhout wrote:
>> In summary: what would objections be to my writing a sha1() patch?
>
> There wasn't any discussion about it last time. It does seem a bit
> wierd to support one but not the other. It's also interesting to note
> that the implementation in the backed is commented with:
I proposed md5 without sha1 because we already had md5 code in the
backend, and we did not have sha1 (and still don't). At the time I was
afraid that if I proposed sha1 as well it would become a debate and we
would have ended up with neither.
Personally I'm in favor of having sha1 and one or more of the newer
replacements in the backend. I'd also like to see HMAC built in. But I
think we need to be careful about running afoul of various export
regulations. Keeping the crypto stuff separate allows distributions to
leave the crypto out if they need to. Perhaps cryptographic hashes/HMAC
are not an issue though. Anyone know?
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2008-01-20 19:18:00 | Re: Sun acquires MySQL |
Previous Message | Tom Lane | 2008-01-20 18:42:21 | Re: [GENERAL] SHA1 on postgres 8.3 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-01-20 19:08:42 | Re: Friendly help for psql |
Previous Message | Tom Lane | 2008-01-20 18:42:21 | Re: [GENERAL] SHA1 on postgres 8.3 |