diff options
| author | landley <landley@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2006-05-16 02:38:26 +0000 |
|---|---|---|
| committer | landley <landley@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2006-05-16 02:38:26 +0000 |
| commit | 4271c1e194ba1fd98436fd5fa44ae488050e6c75 (patch) | |
| tree | e8a8ee0a912d46c699fab3b5fba67c33fcced333 /docs | |
| parent | d0682dab80382a4f5ac1edd2f77062e17f12ffdf (diff) | |
| download | busybox-w32-4271c1e194ba1fd98436fd5fa44ae488050e6c75.tar.gz busybox-w32-4271c1e194ba1fd98436fd5fa44ae488050e6c75.tar.bz2 busybox-w32-4271c1e194ba1fd98436fd5fa44ae488050e6c75.zip | |
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.
git-svn-id: svn://busybox.net/trunk/busybox@15088 69ca8d6d-28ef-0310-b511-8ec308f3f277
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions