Full Disclosure mailing list archives
Re: Re: Case ID 51560370 - Notice of Claimed Infringement
From: Randall Perry <lists () domain-logic com>
Date: Thu, 07 Apr 2005 15:41:52 -0500
At 03:21 PM 4/7/2005, you wrote:
Dear Thomas Sutpen, >> More nice will be if this .iso file is just 451,486k of /dev/random junk. >> Any proves that this file __IS__ Sybase Powerbuilder 9 Enterprise.iso? >> MD5? Something? The problem is much simpler, if 200 persons are sharing this ISO and if it is confirmed to be a "pirated" version by downloading from ONE of these users you can tell that the other 199 are also sharing the same pirated versions, knowing that most (all) p2p applications use hashes to identify the files. In other words, if 200 sources are listed all of them are sharing the exact same file, at least if you trust the p2p application code. (Which you can't proof does indeed work flawlessy in this regards, but you get my point).
No, it isn't quiet that clean. The initial post was regarding eDonkey/eMule client. The files are broken into chunks. The files are 'verified' by a one-way hash.By merely having a single chunk with the same hash is enough 'evidence' that you are in complete possesion of that file. (whether or not it is a successful full copy on your machine, they will ONLY know if ALL sources came from ONLY YOU and they were able to rebuild the entire ISO from all those chunks FROM ONLY YOU). Otherwise, it is _possible_ to have a chunk with the same fingerprint and make it appear that you have said chunk of their iso. (of course a 256 or 512 string would be more accurate and less to chance of being false positive).
It's like saying that a brown Brinks money bag was stolen from the bank. You possess such a brinks money bag, but that doesn't mean it is theirs. (those with cryptography experience can better explain than myself).I am not very comfortable with this grey area being enough 'concrete' evidence to condemn criminals.
What kind of computer training course do their attorneys even go through? (or do they assume these hashes are 'fingerprints') http://www.domain-logic.com _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Current thread:
- Re: Case ID 51560370 - Notice of Claimed Infringement Jason Coombs (Apr 04)
- Re: Re: Case ID 51560370 - Notice of Claimed Infringement Tim O'Guin (Apr 04)
- Re: Re: Case ID 51560370 - Notice of Claimed Infringement Dunceor . (Apr 05)
- Re: Re: Case ID 51560370 - Notice of Claimed Infringement Ag. System Administrator (Apr 05)
- Re: Re: Case ID 51560370 - Notice of Claimed Infringement Thomas Sutpen (Apr 06)
- Re: Re: Case ID 51560370 - Notice of Claimed Infringement Dunceor . (Apr 07)
- Re: Re: Case ID 51560370 - Notice of Claimed Infringement Thierry Zoller (Apr 07)
- Re: Re: Case ID 51560370 - Notice of Claimed Infringement Randall Perry (Apr 07)
- Re: Re: Case ID 51560370 - Notice of Claimed Infringement Thierry Zoller (Apr 07)
- Re: Re: Case ID 51560370 - Notice of Claimed Infringement Randall Perry (Apr 07)
- Re: Re: Case ID 51560370 - Notice of Claimed Infringement Thierry Zoller (Apr 07)
- RE: Re: Case ID 51560370 - Notice of ClaimedInfringement Poof (Apr 07)
- RE: Re: Case ID 51560370 - Notice of ClaimedInfringement Ron DuFresne (Apr 07)
- Re: Re: Case ID 51560370 - Notice of ClaimedInfringement Michael Holstein (Apr 08)
- Re: Re: Case ID 51560370 - Notice of ClaimedInfringement buford.t.pisser (Apr 08)
- Re: Re: Case ID 51560370 - Notice of Claimed Infringement Thomas Sutpen (Apr 06)
- Re: Re: Case ID 51560370 - Notice of Claimed Infringement bkfsec (Apr 08)
- Re: Re: Case ID 51560370 - Notice of Claimed Infringement Mike Owen (Apr 07)
- Re: Re: Case ID 51560370 - Notice of Claimed Infringement Valdis . Kletnieks (Apr 07)