3 ms·
Except then your ISP could see what you download, which I doubt many would like.
by tempaccount420 3y ago
Except then your ISP could see what you download, which I doubt many would like.
- jasonjayr 3y agoTrue, I guess. Are there any ways that could be mitigated?
- yencabulator 3y agoYou can derive an encryption key from both the plaintext content and a shared secret, and store content-addressed encrypted blobs on the open internet, so that only the parties that know the shared secret and a hash of the plaintext can decrypt the blobs. I don't have a great write-up published (only working code!) but if you know Graphviz, see https://github.com/bazil/plop/blob/main/doc/crypto.dot https://github.com/bazil/plop/blob/main/doc/crypto.dot -- or study Tahoe-LAFS. Of course, shared secrets scale poorly beyond individual users and groups of friends. But there's fundamental limitations there, you need to do access control by some secret knowledge.
- jasonjayr 3y agoThis is similar to Freenet, right? Content Addressable URLs that have a content hash + a key, and you have to have both to decrypt the content?
- yencabulator 3y agoProbably; I don't know Freenet internals all that well. As far as I know, Tahoe-LAFS improved on the state of the art by preventing the "Confirmation of File Attack". https://tahoe-lafs.readthedocs.io/en/latest/convergence-secret.html https://tahoe-lafs.readthedocs.io/en/latest/convergence-secr...