Earlier quoted context omitted.
> In a web app, a single compromised server will compromise all security instantly. This is only true if the server has access to the keys of your data. E2EE typically means that it doesn't, only you do.
And how does that work with Firefox Send? Isn't the key somehow in the payload or the URL?
Firefox Send: Free encrypted file transfer service
531–540 of 542 posts
Re: Firefox Send: Free encrypted file transfer service
#532Earlier quoted context omitted.
In a browser, the server serving the JS has an opportunity to access the keys.
This is the case with all E2EE tools. You have to trust that they do their crypto correct and that they aren't evil. As Firefox Send is open source you can setup your own server if you don't trust Mozilla, but then again, if you don't trust Mozilla you might want to eyeball their code carefully first...
Re: Firefox Send: Free encrypted file transfer service
#533Very clean and nice, but how is this financed? That is, who's paying for the server storage and the bandwidth?
First off, Mozilla believes in the service. Mozilla itself gets funding from donations and corporate backing (I think). The cost of bandwidth is small compared to other file share sites in that the files stored are temporary. The transient nature of the files means that the max storage space needed is relative to the concurrent number of users. Bandwidth also. That means sans a very clever DDoS their expenses should…
Re: Firefox Send: Free encrypted file transfer service
#534I've been building a fully featured CLI tool for Firefox Send, supporting this new release. For anyone that is interested: https://github.com/timvisee/ffsend
Re: Firefox Send: Free encrypted file transfer service
#535Re: Firefox Send: Free encrypted file transfer service
#536I don't understand the end-to-end encryption claim. 1. Bob uploads a file, but specifies no password. 2. ??? 3. Sue downloads the file. Best case, Bob's browser encrypts it (with javascript?) before uploading. Either Mozilla provides a key, or Bob sends the key he used. When Sue's browser downloads it, Mozilla sends the key and her browser decrypts it client side. In either case, Mozilla has the password for decrypti…
The client encrypts the file that is uploaded, along with some metadata. The key is appended to the share URL provided by the URL, in the fragment/hash, and is never sent to the remote server. Only people having the URL including the secret will be able to download and decrypt your shared file. See https://github.com/mozilla/send/blob/master/docs/encryption....
Re: Firefox Send: Free encrypted file transfer service
#537I've been building a fully featured CLI tool for Firefox Send, supporting this new release. For anyone that is interested: https://github.com/timvisee/ffsend
Re: Firefox Send: Free encrypted file transfer service
#538Re: Firefox Send: Free encrypted file transfer service
#539I've used this before to send sensitive documents to my attorney, who would have otherwise just wanted email attachments. It worked great.
Based on what I've read, the security model seems to be almost the same as email attachments?