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

From Greg Sabino Mullane
Subject Re: [GENERAL] SHA1 on postgres 8.3
Date
Msg-id b55a46c32865ce74143e295294eee9c1@biglumber.com
Whole thread Raw
In response to Re: [GENERAL] SHA1 on postgres 8.3  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [GENERAL] SHA1 on postgres 8.3  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [GENERAL] SHA1 on postgres 8.3  (David Fetter <david@fetter.org>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> There isn't enough agreement to move some things from pgcrypto
> to the core so this thread is being removed from the patch queue.

I don't agree that we should just close discussion. Nobody seems happy
with the status quo, which is that we provide md5 but not sha1, and
are thus encouraging people to use md5 everywhere. At the very least,
I think we need to add sha1. Adding sha* would be better, and adding
other hashes would be better still (and make PG a better product, in
my opinion: having things builtin vs. contrib is a huge distinction).

I'd also like to emphasize that this is not a pgcrypto issue: while
it provides the same functionality that this proposal does, so does
creating a Pl/Perl function, which is the route I usually go, as it
is much easier and portable. So I see this as adding missing features
to core. We will obviously never replace pgcrypto entirely, due to the
silly state of encryption legislation.

- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200804020906
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkfzhMQACgkQvJuQZxSWSsiTCwCgvauRh/hqOK0BEMEPoKXhzCf5
+GkAn0ma+cZy3fas1Y/uQ0Zf8WAqfLo8
=tTlK
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: GiST opclass and varlena
Next
From: Alvaro Herrera
Date:
Subject: Re: varadic patch