What a blow. I loved it.
What happened to Firefox Send?
71–80 of 267 posts
Re: What happened to Firefox Send?
#72This is due to people sharing malware: https://www.techradar.com/news/mozilla-suspends-firefox-send... The content can't be scanned server-side because uploaded files are encrypted
This seems like a feature, not a bug. People can send things privately to you. It's important, therefore, to verify who you're talking to. Maybe instead of blaming it on the lack of server-side malware scans (which are always easily defeated) they could blame it on lack of an appropriate way to build a framework of trust between endpoints?
You're assuming the good case of people sending naive users a virus. But think of two consenting parties sharing cp or something else. It's a legal hell hole.
Re: What happened to Firefox Send?
#73This is one thing they could have done better in partnership with someone whose main business is hosting and transferring files.
I said it yesterday: Mozilla and Dropbox should talk. Alone they will perish, united they’ll be a real alternative to FAANG.
Re: What happened to Firefox Send?
#74Interesting. I thought it was discontinued due to malware and hackers using it. I wonder if they were ever able to successfully mitigate these threats with an encrypted file sharing service. If they did, the community ought to know so other projects in the future can learn from Mozilla's efforts.
[1]: https://www.zdnet.com/article/mozilla-suspends-firefox-send-...
[2]: https://cybersecuritymag.com/firefox-send-suspended-hackers-...
Re: What happened to Firefox Send?
#75Interesting. I thought it was discontinued due to malware and hackers using it. I wonder if they were ever able to successfully mitigate these threats with an encrypted file sharing service. If they did, the community ought to know so other projects in the future can learn from Mozilla's efforts. [1]: https://www.zdnet.com/article/mozilla-suspends-firefox-send-... [2]: https://cybersecuritymag.com/firefox-send-suspen…
That's also what it says in the linked explanation contained in the article.
Re: What happened to Firefox Send?
#76Earlier quoted context omitted.
Mozilla Foundation, as owner of Mozilla Corp, is a non-profit. Thus the second argument is not that important. Also a single feature can be unprofitable if it helps to drive the related products. First argument is more relevant, I see it as underestimated the risk there and coming out of a technical experiment ... That all said: Mozilla Corp's "focussing" doesn't convince me.
> Mozilla Foundation, as owner of Mozilla Corp, is a non-profit. Thus the second argument is not that important. I included that argument because it's mentioned explicitly by them: > as we weighed the cost of our overall portfolio and strategic focus, we made the decision not to relaunch the service.
This doesn't imply the benefits that were weighted against the costs were monetary.
Re: What happened to Firefox Send?
#77Earlier quoted context omitted.
Between Unix-based machines on the same network my go-to is netcat. receiver$ nc -l 2000 > file sender$ nc receiver 2000 I usually check MD5 sums when I’m done.
SCP. simply for the encrypted transmission, and most *nix machines have ssh
It does require having an account on both machines though. I've used nc in situations where one machine is owned by someone else.
Re: What happened to Firefox Send?
#78And mere minutes after reading this, what should come in on my newsfeed?
https://news.ycombinator.com/item?id=24503077
Another tool for sending encrypted files from one machine to another. Viva la Hacker News!
Re: What happened to Firefox Send?
#79I once again don't have a good solution for 'how do I email a large file' but https://webwormhole.io/ is useful and simple, particularly for sending something big to someone you're video chatting with.
When I send files across the globe I use MegaUpload M E G A Upload to me today Send me a file Meeeeegaaaaaaa (mega.nz)
For those who migt've missed the reference: https://m.youtube.com/watch?v=o0Wvn-9BXVc
Re: What happened to Firefox Send?
#80This is due to people sharing malware: https://www.techradar.com/news/mozilla-suspends-firefox-send... The content can't be scanned server-side because uploaded files are encrypted
This seems like a feature, not a bug. People can send things privately to you. It's important, therefore, to verify who you're talking to. Maybe instead of blaming it on the lack of server-side malware scans (which are always easily defeated) they could blame it on lack of an appropriate way to build a framework of trust between endpoints?
But it tarnishes their name. People who get malware through Firefox Send will associate Firefox or Mozilla with viruses because that's where it's being served from. It doesn't matter to them that it's fully the fault of the person sharing the malware, they expect that if a site is serving them content then that site can ensure that it's safe.