| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: sha1, sha2 functions into core? |
| Date: | 2011-08-10 19:02:01 |
| Message-ID: | 4E42D5A9.2040008@enterprisedb.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10.08.2011 21:45, Peter Eisentraut wrote:
> On ons, 2011-08-10 at 14:26 -0400, Robert Haas wrote:
>> On Wed, Aug 10, 2011 at 2:24 PM, Andrew Dunstan<andrew(at)dunslane(dot)net> wrote:
>>> It's come up before:
>>> <http://archives.postgresql.org/pgsql-hackers/2009-09/msg01293.php>
>>
>> I was about to wonder out loud if we might be trying to hit a moving target....
>
> I think we are dealing with a lot more moving targets than adding a new
> version of SHA every 12 to 15 years.
Moving to a something more modern for internal use is one thing. But
regarding the user-visible md5() function, how about we jump off this
treadmill and remove it altogether? And provide a backwards-compatible
function in pgcrypto.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-08-10 19:04:13 | Re: sha1, sha2 functions into core? |
| Previous Message | Heikki Linnakangas | 2011-08-10 18:54:06 | Re: "pgstat wait timeout" warnings |