cvs commit: src/lib/libmd Makefile sha256.3 sha256.h sha256c.c shadriver.c src/sbin/md5 Makefile md5.c

Richard Coleman rcoleman at criticalmagic.com
Wed Mar 9 11:37:33 PST 2005


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 at criticalmagic.com


More information about the cvs-src mailing list