On Sun, Jan 20, 2008 at 05:24:11PM -0000, Greg Sabino Mullane wrote: > 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().
md5() was added with the following commit message: > Attached are two small patches to expose md5 as a user function -- > including documentation and regression test mods. It seemed small and > unobtrusive enough to not require a specific proposal on the hackers > list -- but if not, let me know and I'll make a pitch. Otherwise, if > there are no objections please apply. http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/varlena.c#rev1.94 > 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 do not expect this file to be used for general purpose MD5'ing of > large amounts of data, only for generating hashed passwords from > limited input. Have a nice day, -- Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/ > Those who make peaceful revolution impossible will make violent revolution > inevitable. > -- John F Kennedy
signature.asc
Description: Digital signature