This seems like a cool idea, but also somewhat questionable from a security standpoint? Isn’t distributing the encrypted content alongside the means to decrypt it (i.e. bundling this all in one file which is sent to the client) essentially equivalent to providing physical access to an encrypted drive? Like an attacker with enough time and effort could bypass the encryption.

[–] Mike1576218@lemmy.ml 12 points 2 months ago

It is not a problem to distribute the decryption algorithm. The question remains against what this will protect. Normal https encrypts the traffic safely during transit. With this, the data is also encrypted on the server. But if you can access the server, you can modify the javascript code to send the password back to a server.

It could be used on something like IPFS, where all data is basically public but you can be sure it hasn't been modified.

[–] CosmicTurtle0@lemmy.dbzer0.com 8 points 2 months ago (1 children)

Exactly. This shouldn't be used to store your taxes, for example. But it might be good if you want to post details about your baby shower without your parents getting the details.

[–] elliot_crane@lemmy.world 3 points 2 months ago

Yep, definitely situational depending on your risk model/tolerance; pretty cool idea nonetheless.