Re: [GENERAL] SHA1 on postgres 8.3

Поиск
Список
Период
Сортировка
От Greg Sabino Mullane
Тема Re: [GENERAL] SHA1 on postgres 8.3
Дата
Msg-id d65d30f72328bdc396b15a29e0dbab05@biglumber.com
обсуждение исходный текст
Ответы Re: [GENERAL] SHA1 on postgres 8.3  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: [GENERAL] SHA1 on postgres 8.3  (Martijn van Oosterhout <kleptog@svana.org>)
Re: [GENERAL] SHA1 on postgres 8.3  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [GENERAL] SHA1 on postgres 8.3  ("Marko Kreen" <markokr@gmail.com>)
Список pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> In MySQL I have a function SHA1, which is critical for storing and
> authenticating passwords.

It sure would be nice to have this in core. Yeah, there's pgcrypto, 
but it's a bit overkill for people who simply want to do a SHA1, 
especially when they see we already have a md5(). I also realize that 
SHA1 is not a great solution these days either, but I'd at least like 
to see a discussion on moving Postgres to somewhere between 
"only has md5()" and "all pg_crypto functions inside core", even if 
it only means a handful of SHA functions. Moving this over to -hackers.

In summary: what would objections be to my writing a sha1() patch? 

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200801201218
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8

-----BEGIN PGP SIGNATURE-----

iD8DBQFHk4NIvJuQZxSWSsgRA83ZAJ0SIk36sYvLF30q7hog2sBaQU1+LACeOv15
WkDwrzgzHyrwmNFP85plbBA=
=6P4y
-----END PGP SIGNATURE-----




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Gregory Stark
Дата:
Сообщение: Re: Transaction Snapshot Cloning
Следующее
От: Rick Vernam
Дата:
Сообщение: select statement details