> The md5.h/md5c.c files allow "copy and use", but no modification of > the files. There are some alternative implementations, i.e. in glibc, > openssl, so a replacement should be sage. Any other requirements when > considering a replacement? > > Matthias
I believe the "plan" for md5 and sha1 and such is to use the much faster openssl versions "in the future" (based on a long thread debating future interfaces to such things on python-dev last summer). That'll sidestep any tedious license issue and give a better implementation at the same time. i don't believe anyone has taken the time to make such a patch yet. -g -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
