Date: Wed, 09 Mar 2005 14:38:14 -0500 From: Richard Coleman <rcoleman@criticalmagic.com> To: Colin Percival <cperciva@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libmd Makefile sha256.3 sha256.h sha256c.c shadriver.c src/sbin/md5 Makefile md5.c Message-ID: <422F50A6.907@criticalmagic.com> In-Reply-To: <200503091923.j29JN4Ti063868@repoman.freebsd.org> References: <200503091923.j29JN4Ti063868@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Colin Percival wrote: > cperciva 2005-03-09 19:23:04 UTC > > FreeBSD src repository > > Modified files: > lib/libmd Makefile shadriver.c > sbin/md5 Makefile md5.c > Added files: > lib/libmd sha256.3 sha256.h sha256c.c > Log: > In light of the recent 2^69 operation collision-finding attack on SHA1, > add support for SHA256. Is there a reason that there are multiple versions of md5/sha1/sha256/etc in the source tree? There are versions in at least three places (lib/libmd, sys/kern/crypto, and crypto/openssl/crypto). I think md5 is located in a few other places as well. It seems if these could be centralized, then it would be easier to have assembly accelerated versions for each platform, or better yet to utilize crypto hardware. I was just curious. Richard Coleman rcoleman@criticalmagic.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?422F50A6.907>