From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] SHA1 on postgres 8.3 |
Date: | 2008-01-20 17:24:11 |
Message-ID: | d65d30f72328bdc396b15a29e0dbab05@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general 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(at)turnstep(dot)com
PGP Key: 0x14964AC8 200801201218
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFHk4NIvJuQZxSWSsgRA83ZAJ0SIk36sYvLF30q7hog2sBaQU1+LACeOv15
WkDwrzgzHyrwmNFP85plbBA=
=6P4y
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2008-01-20 17:54:01 | Re: Sun acquires MySQL |
Previous Message | Pavel Stehule | 2008-01-20 17:04:25 | Re: Sun acquires MySQL |
From | Date | Subject | |
---|---|---|---|
Next Message | Rick Vernam | 2008-01-20 17:46:55 | select statement details |
Previous Message | Martijn van Oosterhout | 2008-01-20 16:38:46 | Re: SHA1 on postgres 8.3 |