Thierry Zoller wrote:
These factors do not come into play when you're talking about P2P protocols that use seeded chunks to share their files. When a particular file is split up into chunks and each chunk is appropriately named on the host, the file itself (depending on the P2P protocol) doesn't always harbor a descriptive name. The name of the file is stored in the protocol and file names/dates can very well be different.You forget that the hash is not the only unique thing that specific file has in common with the pirated file/material.
Calculate the following probability:
- The file/chunck has the same MD5 (or whatever HASH) as the pirated material in question. - The file has the EXACT same filename (if there would be a collission how is the probability in mathametic terms that the file the collission takes place has the exact same filename?) - The file has the EXACT same size (The file has the EXACT same date etc.pp)
These aren't the same issues as verifying a filesystem that you control. It's a lot more complex than that.
-Barry
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
