[core-dev] download corruption checking & THEX

Hi,

I have been looking into verifying files on the fly. Because I don't really like 
the way LimeWire's GUI freezes up every time it is trying to identify corrupted 
parts (and I would like to get rid of the overlap checking). I still have issues 
with the possibility of an attacker uploading bad hash trees for a file, causing 
a possible victim to redownload parts of the file over and over again. One 
solution would be to include the TigerTree root hash in all query hits.

Is there any way for LimeWire to become a little less SHA1-centric? Ultimately, 
support for the plain SHA1 URN should IMO be phased out until it is completely 
replaced by the Tiger-Tree root hash.

Another thing is that I would really like to be able to request small hash trees 
for subranges of a file that are small enough to be created on the fly. This is 
would allw you to reduce the overhead caused by corruptions significantly since 
you could e.g. identify corrupted 1KB blocks without transferring the leaf 
hashes for every 1KB block of the file. (At the moment it seems very likely that 
BT2 is going to offer that feature.)

What do you think?

mfg
gregorio
_______________________________________________
core-dev mailing list
[email protected]
http://www.limewire.org/mailman/listinfo/core-dev