This is the mail archive of the
libc-hacker@sourceware.cygnus.com
mailing list for the glibc project.
Re: glibc 2.0.103
> From: smurf@noris.de (Matthias Urlichs)
> Newsgroups: dist.glibc
> Date: 26 Nov 1998 08:03:41 +0100
> drepper@cygnus.com (Ulrich Drepper) writes:
> > glibc-2.0.103.tar.gz
> > As usual, let me know about success and failures.
> >
> I wonder why glibc does not export its MD5 code.
Because those programs that need it have their own implementations,
and because MD5 should not be used in new designs according to its
author (try SHA instead).
Also, your patch needs to make the md5 functions weak, and add new
versions with underscores which -lcrypt can use.
If we really wanted to do this sort of thing, we should implement a
proper security library, probably including GSS-API---this would be
good for Secure RPC, since it's not really `secure' at present. At
present, all the cryptographic interfaces provided by glibc are only
provided for historical or compatibility reasons, except for crypt()
using MD5.
There are already a lot of security libraries available, though.
--
Geoffrey Keating <geoffk@ozemail.com.au>