pgsql: Remove support for libmhash/libmcrypt.

From: neilc(at)svr1(dot)postgresql(dot)org (Neil Conway)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Remove support for libmhash/libmcrypt.
Date: 2005-03-21 05:17:19
Message-ID: 20050321051719.261AA5668A@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Remove support for libmhash/libmcrypt.

libmcrypt seems to dead, maintainer address bounces,
and cast-128 fails on 2 of the 3 test vectors from RFC2144.

So I see no reason to keep around stuff I don't trust
anymore.

Support for several crypto libraries is probably only
confusing to users, although it was good for initial
developing - it helped to find hidden assumptions and
forced me to create regression tests for all functionality.

Marko Kreen

Modified Files:
--------------
pgsql/contrib/pgcrypto:
Makefile (r1.12 -> r1.13)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/Makefile.diff?r1=1.12&r2=1.13)
README.pgcrypto (r1.7 -> r1.8)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/README.pgcrypto.diff?r1=1.7&r2=1.8)

Removed Files:
-------------
pgsql/contrib/pgcrypto:
mhash.c
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/mhash.c)

Browse pgsql-committers by date

  From Date Subject
Next Message Neil Conway 2005-03-21 05:18:46 pgsql: * construct "struct {} list [] = {}" confuses pgindent - split
Previous Message Tom Lane 2005-03-21 01:24:05 pgsql: Convert index-related tuple handling routines from char 'n'/' '