3 ms·
Yes Fnoord, this is one potential use case but not the primary one. Our focus is on giving people an EASY and SECURE way to send their file to each other. Most
by Walterion 7y ago
Yes Fnoord, this is one potential use case but not the primary one.
Our focus is on giving people an EASY and SECURE way to send their file to each other.
Most other services out there are easy to use but not secure or private, or very secure, but you need to be a semi developer to use them. If anyone shares their file publicly, it will be their responsibility.
- DanHulton 7y agohttps://send.firefox.com/ https://send.firefox.com/ is probably the easiest way to securely send a file that I can think of off the top of my head. You don't need to be a developer, and the file is automatically deleted after a period of time. With a file stored on the blockchain, I remain continuously and permanently vulnerable to a data breach or any other loss of secrecy control. The moment that link/password combo is compromised, that file is permanently public. Now, you could argue that the moment a file is briefly public, it can be downloaded and thus is outside of your control anyway, and you'd be correct. But the case I'm more specifically thinking of is trying to send a large, reasonably secret file through email. You can't attack 1GB to mail, so you upload it somewhere and send the email with the url/password. If you use Firefox Send, that file gets to its recipient, and then shortly thereafter, the link becomes invalid. If I use this service, that link stays valid forever. If my company's email archive is then later exfiltrated by a hacker or disgruntled employee, that secure file in the first case remains secure. In the second case, it's now compromised. This doesn't invalidate certain uses of your service, but to not mention anywhere on your site that uploaded files will remain available irrevocably and forever is negligent.