6 ms·
There should be a feature in torrent clients which add some random bytes to videos when downloading them without braking the video itself so md5 checks would be
by malinens 10y ago
There should be a feature in torrent clients which add some random bytes to videos when downloading them without braking the video itself so md5 checks would be useless for illegal content downloads
- mattmanser 10y agoThat would making seeding it impossible though as you wouldn't be able to verify the chunk is what you claim it is and eventually lead to the whole video being corrupt.
- RubyPinch 10y agoas long as the torrent client knows how to reverse the changes it made to the file (why wouldn't it?) then there won't be any problem. Its just a really really simple form of "encryption", which most torrent clients do support
- wallmani 10y agoIf it's reversible like that it is still possible for PayPal and others to implement it too.
- RubyPinch 10y agoIts encryption, you apply a transform before putting it onto the dropbox, and then you apply a transform after you pull it back, and the key it'd be encrypted against would be per user (like most encryption)
- heartsucker 10y agoAnd then DropBox runs that on every file, so you you have the normal md5 and the torrent-obfuscation-reversed md5. They check both. We have now achieved nothing.
- Morgawr 10y agoWhat about having a client-side only "corruption" function that is unique for each client? The file is visually the same, the md5 hash is different but when the torrent client is sending the data it just "uncorrupts" the file. When the file is received by another client, that one person's client will take care of uniquely corrupting their own version for storage.
- niij 10y agoThis is not possible. The torrent protocol works by checking the hash of each file that it downloads so it can reseed the file. If these files were changed by even 1 bit then they couldn't be reseeded back into the torrent network.
- RubyPinch 10y agounless the "corruption" is reversible by the torrent client, which it would be
- corobo 10y agoIf the corruption is reversible then the people doing the checking can also reverse it. They'll have both the corrupt version and the reverse-fixed version and just have to check an extra hash per thing they're scanning for
- reitanqild 10y agoI guess as long as Public Key Encryption works, something like this should be theoretically possible?
- niij 10y agoCan you explain how Public Key Encryption would be related? I was thinking more in terms of a torrent client corrupting a predictable last bit of each saved file (which could cause tons serious corruption issues in itself for non-media files). This appears to only be feasible if each user had their own private key that could be used to compute where the corrupted bit is added to media files.
- rplnt 10y agoAren't the files matched by checksums though? I.e. you have a checksum and that's how tracker knows what you want?
- friendzis 10y agoI guess GP meant that torrent client could e.g. pad a file on disk (safest option) and store that metadata along with original hash. Hashes would not change over the torrent network, but would be different in other networks
- VMG 10y agoThey'd use some other method of fingerprinting then. It'd be an interesting arms race.