Displaying 2 results from an estimated 2 matches for "rs_char_offset".
2002 Aug 04
1
MD4 bug in rsync for lengths = 64 * n
...check against any docs.)
I started with librsync 0.9.3 and the Intermezzo perl interface to
librsync written by Shirish Phatak. However, as I'm sure is well-known,
the Adler crc32 and MD4 computed by librsync don't match those in
rsync 2.5.5.
After swapping the crc32 endianess, changing RS_CHAR_OFFSET from 31 to
0, and adding rsync's checksum_seed to librsync's MD4 they now agree,
except in one case: when the total data length (including the 4 byte
checksum_seed) is a multiple of 64, the MD4 checksums in librsync and
rsync don't agree. After reviewing the code in librsync, rsync and...
2011 Jan 24
1
Java implementation - about weak checksum difference
Hi all,
I'm trying a java implementation of rsync for "fun and profits" ;-)
helped by librsync 0.9.7 and jarsync (a died java implementation)
So i started to implement rdiff command and for now i have a working
signature command.
With first test, i had the same signature file of
testsuite/mksum.input/COPYING.sig but when i try with another dummy
file, for each checksum pair :