Make md5 calculation always go through an the buffer so that A) we don't
authorRob Landley <rob@landley.net>
Tue, 16 May 2006 02:38:26 +0000 (02:38 -0000)
committerRob Landley <rob@landley.net>
Tue, 16 May 2006 02:38:26 +0000 (02:38 -0000)
commit34b5319d86eb639794dcccc56a443e7a35daf5d3
treee8a8ee0a912d46c699fab3b5fba67c33fcced333
parentd272dc7cb306995c6a8ec78c13a4aa1021d33a53
Make md5 calculation always go through an the buffer so that A) we don't
handle packets out of sequence if some data goes through the buffer and
some doesn't, B) it works on systems that can't handle aligned access,
C) we just have one code path to worry about.

While we're at it, sizeof() and RESERVE_CONFIG_BUFFER() really don't combine
well, which is why md5sum has been reading and processing data 4 bytes at a
time.  I suspect that the existence of CONFIG_MD5_SIZE_VS_SPEED to do loop
unrolling and such in the algorithm was an attempt to work around that bug.
coreutils/md5_sha1_sum.c
include/libbb.h
libbb/md5.c