On Sat, 21 Dec 2002, Darren Landrum wrote:
But wait, there's more! :) This now brings us to
the "prevention of
upload of copyrighted sample sets / loops / patches" part of the design.
If we have a working checksum database to check against stored
metadata, why not gather all of the checksums we can for every loop
library for Acid, every sample set for Gigasampler / Unity Session /
etc. that we can get our hands on (legally)? Remember, we're only
running these through MD5 to get a checksum, then uploading the
checksum to the server.
Here's the good part, although I'm sure most of you are ahead of me.
Whenever a user uploads a loop or sample set, the server will first
decompress the file, then run an MD5 on it, which will then be compared
to the checksum database. Any matches are flagged for removal by an
administrator.
This might not be good enough. Modifying a file in the slightest way will
change the MD5 enought to get past a filter, but not a lawyer. It'll only
guard against innocent uploading, not malecious.
Taybin
--
http://www.piratesvsninjas.com