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

Re: [GENERAL] SHA1 on postgres 8.3

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-04-02 13:07:01
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
Hash: RIPEMD160

> There isn't enough agreement to move some things from pgcrypto
> to the core so this thread is being removed from the patch queue.

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, and
are thus encouraging people to use md5 everywhere. At the very least,
I think we need to add sha1. Adding sha* would be better, and adding
other hashes would be better still (and make PG a better product, in
my opinion: having things builtin vs. contrib is a huge distinction).

I'd also like to emphasize that this is not a pgcrypto issue: while
it provides the same functionality that this proposal does, so does
creating a Pl/Perl function, which is the route I usually go, as it
is much easier and portable. So I see this as adding missing features
to core. We will obviously never replace pgcrypto entirely, due to the
silly state of encryption legislation.

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation
PGP Key: 0x14964AC8 200804020906


In response to


pgsql-hackers by date

Next:From: Morris GoldsteinDate: 2008-04-02 14:31:21
Subject: Re: Can Postgres 8.x start if some disks containing tablespaces are not mounted?
Previous:From: Greg Sabino MullaneDate: 2008-04-02 12:55:40
Subject: Re: Friendly help for psql

pgsql-general by date

Next:From: Chris HooverDate: 2008-04-02 13:37:20
Subject: PGCon 2008, Are you going?
Previous:From: Zdenek KotalaDate: 2008-04-02 12:44:08
Subject: Re: Can Postgres 8.x start if some disks containing tablespaces are not mounted?

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