Re: SHA1 authentication - Mailing list pgsql-general

From Brian Mathis
Subject Re: SHA1 authentication
Date
Msg-id 183c528b0510271327s464fac54jcf5bd3a3c80a848@mail.gmail.com
Whole thread Raw
In response to Re: SHA1 authentication  (Bruno Wolff III <bruno@wolff.to>)
List pgsql-general
On 10/27/05, Bruno Wolff III <bruno@wolff.to> wrote:
On Mon, Oct 24, 2005 at 11:33:50 +0200,
  Martijn van Oosterhout <kleptog@svana.org> wrote:
>
> By all means, submit a patch but there's no real hurry right now. We
> should probably move straight to something more secure anyway, maybe
> SHA-256 or something.

This makes more sense. There is little point in going to the effort to
changing to SHA-1 only to change again later.
There isn't any hurry to change now, so it might be better to wait until
the next group of hash functions is designed, built on lessons learned from
the attacks against MD5 and SHA-1.

It might be a good step to go through and figure out what needs to be changed, then implement a plugin type system to reduce the need for changes when the next generation of hashes gets "broken".  It might even allow for authentication to external sources, like LDAP or some other plugin.

pgsql-general by date:

Previous
From: "Keith C. Perry"
Date:
Subject: Re: Why database is corrupted after re-booting
Next
From: Scott Marlowe
Date:
Subject: Re: Why database is corrupted after re-booting