I wrote about this on some earlier MU submission, so I won't repeat all that here, but all in all, even if you knew that file X existed on Mega's servers, it would be pretty damn haphazard to just outright delete it, because you might be hurting many legitimate users by doing so.Īnyway, I think Mega could secure user's files simply by encrypting the locator keys they have with the user's own key, and this data only gets decrypted and parsed client-side when the user uses Mega with the user's own key. The thing with copyrighted content, though, is that even if the file you're checking might be infringing on copyrights in certain cases, in other cases it might as well be completely legit. >then serve it to Mega along with a DMCA takedown notice. (and replicated if need be) across hosts in a gnunet system to balance load."Įfficient Sharing of Encrypted Data - Krista Bennett, Christian Grothoff, Tzvetan Horozov, Ioana Patrascu These files can then be split into small blocks and distributed Otherwise it's easy to bust you for having the data.Įdit: GNUet quote:"The gnunet encryption scheme is remarkable in that it allows identical filesĮncrypted under different keys to yield the same ciphertext, modulo a smallīlock of metadata. Therefore this approach doesn't remove need for pre-encrypting sensitive data. But if I know what I'm looking for, I can confirm if my cache contains that data or not. It makes things easier for service provider, they don't want to know what they're storing. If I really don't anyone want to know that I got this data, that's failed scenario. Because same plaintext encrypts to same ciphertext there is huge problem with that. Yes, there's exactly the same problem as with Freenet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |