On Sat, Oct 02, 2004 at 06:52:40PM +0200, Richard Atterer wrote: > >$ jigdo-file mt -fi adduser_3.59_all.deb -j grr.jigdo -t grr.template adduser_3.59_all.deb >Match of `adduser_3.59_all.deb' at offset 0 >Finished - image size is 93882 bytes. >$ jigdo-file ls -t grr.template >need-file 0 93882 K3IwZGUJlF7q6sCv7t8PfA kRjI35yjRzk >image-info 93882 K3IwZGUJlF7q6sCv7t8PfA 1024 >$ jigdo-file ls -t grr.template --hex >need-file 0 93882 2b7230646509945eeaeac0afeedf0f7c 9118c8df9ca34739 >image-info 93882 2b7230646509945eeaeac0afeedf0f7c 1024 > >This means that the Rsync64Sum expected by jigdo-file is kRjI35yjRzk, or >9118c8df9ca34739 in hexadecimal. For the algorithm, this means that >lo=0xdfc81891, hi=0x3947a39c. > >The JTE-generated .template contains something else: > >$ jigdo-file ls -t sarge-i386-1.template|grep 52803584 >need-file 52803584 93882 K3IwZGUJlF7q6sCv7t8PfA gIOeQJMjgK4 >$ jigdo-file ls -t sarge-i386-1.template --hex|grep 52803584 >need-file 52803584 93882 2b7230646509945eeaeac0afeedf0f7c 80839e40932380ae > >So for JTE, lo=0x409e8380 and hi=0xae802393 - the bytes are not just >reordered like I initially suspected, but completely different. %-| Having >stared at JTE's implementation of the algorithm as well as jigdo-file's (in >src/rsyncsum.cc:73), I cannot figure out any differences. Grr, I'll have a >closer look tomorrow - unless Steve beats me in finding the bug. ;-) I can't promise anything at the moment; I'm stuck away from home with a family emergency right now. I tested this, so I'm surprised it doesn't work... :-( I'll see if I can take a look. -- Steve McIntyre, Cambridge, UK. steve@einval.com We don't need no education. We don't need no thought control.
Attachment:
signature.asc
Description: Digital signature