News for hackers. Stuff that matters.
Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by rvern on Monday September 26, 2016 @02:08AM (#12579576)
What makes you believe Chromium has better sandboxing than Firefox? That may have been true in the past, I doubt it has much truth to it today. Furthermore, if you use GNU/Linux it should be trivial to give your web browser better sandboxing than what it does by itself. (You can use AppArmor or SELinux, you can run it in a systemd-nspawn container, you can use Firejail…)
Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by viraptor on Monday September 26, 2016 @03:22AM (#12579920)
> What makes you believe Chromium has better sandboxing than Firefox?

https://wiki.mozilla.org/Security/Sandbox#Linux and https://chromium.googlesource.com/chromium/src/+/master/docs...

There's more details than I can easily describe in a HN post, but in general read those links to learn why

> if you use GNU/Linux it should be trivial to give your web browser better sandboxing than what it does by itself

There's a difference between sandbox separating it from the system (what apparmor/selinux can do) and sandbox of each content and plugin (what browser itself can do, mostly with seccomp). Or in a practical example - why do I care that a website can't write to my home directory, if it still has full access to my bank in another tab.

e10s helps a bit, but it's still in early stages. It wasn't even enabled for everybody until 12th Sept this year. Even now, I believe (please correct me if untrue) that there's only one child for all web content, not one per tab.

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by AgentME on Monday September 26, 2016 @02:18AM (#12579634)
Chrome has a process for each tab that's sandboxed so that most exploits would be trapped and unable to escalate out of the sandbox. Firefox has nothing like that yet, but it's coming eventually with the new multiprocess architecture that they're ramping up.
Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by rvern on Monday September 26, 2016 @02:21AM (#12579647)
Firefox has sandboxing for tabs as well, and has had it before e10s.
Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by esprehn on Monday September 26, 2016 @07:16AM (#12580861)
What sandbox are you referring to?
Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by gcb0 on Monday September 26, 2016 @11:52AM (#12582843)
that's not how processes works...
Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by AgentME on Monday September 26, 2016 @05:50PM (#12585900)
Processes don't imply sandboxing, but once you have things split up into multiple processes there are powerful process-sandboxing tools that are available for Firefox to use in the coming future.
Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by pjmlp on Monday September 26, 2016 @02:11AM (#12579593)
Not something that the average joe and jane can do.
Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by rvern on Monday September 26, 2016 @02:16AM (#12579617)
Neither the article nor Hacker News are intended for the average Joe.
Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by pjmlp on Monday September 26, 2016 @03:23AM (#12579922)
You right, average Joe only uses Chrome, Edge and Safari on their mobile phones and desktop computers.
Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by NTripleOne on Monday September 26, 2016 @03:23AM (#12579927)
But the issue itself is one that both affects and is caused by the "average Joe".
Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by startling on Monday September 26, 2016 @02:45AM (#12579755)
All of that is only marginally helpful without X sandboxing.
Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by danieldk on Monday September 26, 2016 @02:48AM (#12579767)
I agree, but the same applies to Chrome on X11.
Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by startling on Monday September 26, 2016 @02:52AM (#12579791)
No, I mean that even if you add additional layers of sandboxing, the chrome process can still access the X socket. A process with the ability to read and write to the X socket can record keypresses, issue mouse and key events, etc etc.

(There's not a well-supported way to avoid this, but there are some tools that use Xpra for it.)

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by danieldk on Monday September 26, 2016 @04:19AM (#12580136)
I know. My point was that Chrome does not have a security advantage over Firefox on X11, since the discussion was about the security advantages of Chrome/Chromium over Firefox.

We are in full agreement. On X11, the security model is: every application can see/do everything. You should only run an application in X11 when you fully trust it.