4 ms·
You could already add E2EE encryption yourself, just encrypt the content before you hash it and share the hash? Still, I wouldn't want anything I want to be pr
by diggan 3y ago
You could already add E2EE encryption yourself, just encrypt the content before you hash it and share the hash?
Still, I wouldn't want anything I want to be private to be on a public network, be it IPFS, S3 or the internet at large. Who knows when the encryption will be broken? Simply too little benefits compared to the massive drawback in case the encryption doesn't hold in the future.
- ianopolous 3y agoYou can do that and also require auth to retrieve the cipher text blocks: https://peergos.org/posts/bats https://peergos.org/posts/bats
- kevincox 3y agoYes, but having it be disjointed from the protocol adds friction. You can't just browse the files using native tools and gateways. I think it would be great to be built-in. In fact I would argue that all data should be encrypted. But by default it could be encrypted with its own hash or similar so that it can still be deduplicated but has strong protection from people who don't already know the content (or hash) and can be pinned on untrusted nodes. This would resemble the Google Docs "public link" sharing. The only downside would be slight CPU overhead and longer keys.