Show HN: Peer-to-peer secure file transfer using WebRTC

Re:Show HN: Peer-to-peer secure file transfer using WebRTC by StavrosK on Sunday February 28, 2016 @10:02PM (#11193396)

Just encrypt the data and pass the key in the url, like so:

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.

[ Parent | on HN ]

Re:Show HN: Peer-to-peer secure file transfer using WebRTC by STRML on Sunday February 28, 2016 @10:48PM (#11193491)

We 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/

[ Parent | on HN ]

Re:Show HN: Peer-to-peer secure file transfer using WebRTC by sneak on Sunday February 28, 2016 @10:15PM (#11193420)

The server can silently decide to start sniffing the keys at any time. That isn't security.

[ Parent | on HN ]

Re:Show HN: Peer-to-peer secure file transfer using WebRTC by Rhapso on Sunday February 28, 2016 @10:09PM (#11193408)

that 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

[ Parent | on HN ]

Re:Show HN: Peer-to-peer secure file transfer using WebRTC by StavrosK on Monday February 29, 2016 @06:33AM (#11194856)

You can trivially ensure that by just downloading the page. These things are usually a single HTML page you can run locally.

[ Parent | on HN ]