Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] SHA1 on postgres 8.3

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] SHA1 on postgres 8.3
Date: 2008-04-02 15:38:31
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
"Greg Sabino Mullane" <greg(at)turnstep(dot)com> writes:
> 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,

There may be a few people who are unhappy, but the above claim seems
vastly overblown.  md5 is sufficient for the purpose it is intended
for in core postgres (namely, obscuring the true source text of
passwords), and if you have needs much beyond that you'll soon be
installing pgcrypto anyway.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2008-04-02 15:48:02
Subject: Re: varadic patch
Previous:From: Alvaro HerreraDate: 2008-04-02 15:37:49
Subject: Re: varadic patch

pgsql-general by date

Next:From: Magnus HaganderDate: 2008-04-02 15:49:28
Subject: Re: [GENERAL] SHA1 on postgres 8.3
Previous:From: Tom LaneDate: 2008-04-02 15:33:35
Subject: Re: Foreign keys causing conflicts leading toserialization failures

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group