News for hackers. Stuff that matters.
Re:Firefox Send: Private, Encrypted File Sharing by zeveb on Wednesday October 11, 2017 @02:22PM (#15451961)
Using WebCrypto doesn't defend against the insecurity: their JavaScript code can send a copy of the file anywhere it likes. Mozilla can, if it wishes or if it is compelled to, deliver malicious JavaScript which does exactly that to a single targetted IP address, or just every once in awhile in order to find potentially interesting files.

Using in-web-page crypto gives users a false sense of security. This is, I believe, a very real problem.

Re:Firefox Send: Private, Encrypted File Sharing by giaour on Wednesday October 11, 2017 @04:38PM (#15453245)
It's true; you're trusting Mozilla to deliver secure code. You'd be placing a similar amount of trust in Mozilla by using Firefox, since browsers automatically update themselves these days.

What WebCrypto guarantees is that it is truly Mozilla's code that you're trusting, since the WebCrypto APIs are only available in a secure context (HTTPS or localhost).

Re:Firefox Send: Private, Encrypted File Sharing by zeveb on Wednesday October 11, 2017 @05:01PM (#15453452)
> You'd be placing a similar amount of trust in Mozilla by using Firefox, since browsers automatically update themselves these days.

No, because I use the Debian Firefox, which means that I'm trusting the Debian Mozilla team. I feel much better about that than about directly trusting Mozilla themselves.

I don't trust auto-updates.

Re:Firefox Send: Private, Encrypted File Sharing by galaxyLogic on Saturday October 14, 2017 @01:28PM (#15473174)
Why would you trust Debian more than FireFox?

About the auto-updates. CCleaner recently had an incident where their version .33 something had a backdoor injected by some 3rd party. If you downloaded version 34 you were safe. If you loaded 32 and configured it auto-update you got the malicious update. But that didn't affect the auto-update setting as far as I know, so if you had it on you would in about 2 weeks time have gotten an automatically fixed clean version.

Point: The worst situation was if you did not have auto-updates on and downloaded v. 33. Then you were stuck with that until somebody told you you had malice on your machine.

You're damned if you do and damned if you don't.

https://www.piriform.com/news/blog/2017/9/18/security-notifi...

Re:Firefox Send: Private, Encrypted File Sharing by giaour on Wednesday October 11, 2017 @07:13PM (#15454377)
That's a very different position than the one you staked out above. It's not browser-based crypto you have a problem with, its crypto performed by an application whose patching is done outside of your control.

That's reasonably for a technically savvy user, but the vast majority of users do not use Debian. They use Windows or OSX and rely on trusted corporations like Apple, MSFT, Google, and Mozilla to keep their systems patched.

Re:Firefox Send: Private, Encrypted File Sharing by damnyou on Wednesday October 11, 2017 @05:02PM (#15453459)
Using any sort of application downloaded from the internet gives users a false sense of security.