3 ms·
Just encrypt the data and pass the key in the url, like so: https://bitf.ly/1b4b7ee4fe39312afbfffbe47d831f99#someaeskey https://bitf.ly/1b4b7ee4fe39312afbfffbe
by StavrosK 11y ago
Just encrypt the data and pass the key in the url, like so:
https://bitf.ly/1b4b7ee4fe39312afbfffbe47d831f99#someaeskey https://bitf.ly/1b4b7ee4fe39312afbfffbe47d831f99#someaeskey
That way, the server never sees the key (it's client-side and fragments don't get sent), but nobody except the recipient can decrypt the data.
- Rhapso 11y agothat only works if you have a way to assure the JS has not being modified every time the page is ever loaded everywhere. That only works on a content addressed protocol like IPFS
- StavrosK 11y agoYou can trivially ensure that by just downloading the page. These things are usually a single HTML page you can run locally.
- sneak 11y agoThe server can silently decide to start sniffing the keys at any time. That isn't security.
- STRML 11y agoWe do this on securesha.re. Yes, you can't be sure the client hasn't changed the JS - I'm going to start putting md5s in the script tags but it's up to the client to check they haven't changed. However, the client is open source [1], so you could always run your own client. 1. https://github.com/STRML/securesha.re-client/ https://github.com/STRML/securesha.re-client/