News for hackers. Stuff that matters.
Re:Firefox exploit found in the wild by rplnt on Friday August 07, 2015 @06:32AM (#10021736)
Wouldn't selinux be enough? Browsers have no business touching files outside of ~/.mozilla or whatever.
Re:Firefox exploit found in the wild by bm98 on Friday August 07, 2015 @03:26PM (#10024461)
I've run Firefox in a Red Hat/Fedora SELinux sandbox [1] [2] for the past 5 years or so. It is a little more tedious for things such as file uploads/downloads and cut-and-paste -- but worth it, IMHO.

[1] http://danwalsh.livejournal.com/31146.html

[2] http://www.bress.net/blog/archives/195-Firefox-in-a-sandbox-...

Re:Firefox exploit found in the wild by blfr on Friday August 07, 2015 @08:38AM (#10022066)
Wouldn't this prevent you from opening local .html files?
Re:Firefox exploit found in the wild by anc84 on Friday August 07, 2015 @09:09AM (#10022197)
How would you handle uploads or downloads then?
Re:Firefox exploit found in the wild by fluidcruft on Friday August 07, 2015 @10:00AM (#10022501)
Explicitly configure appropriate permissions for ~/Download/Firefox?
Re:Firefox exploit found in the wild by anc84 on Friday August 07, 2015 @10:04AM (#10022524)
I organise my files, I don't put everything into the same directory. I save them all over my file system. Same for uploads, I do not put them into one directory prior to uploading.
Re:Firefox exploit found in the wild by kccqzy on Friday August 07, 2015 @11:44AM (#10023105)
I think a better method is what Apple has done in OS X. When the app needs to read from or write to a user specified file, the app calls a specific API that presents a file picker dialog. The file picker dialog is running in a separate process from the sandboxed app, and the app will temporarily be granted permissions to access this particular chosen file through this API.
Re:Firefox exploit found in the wild by fluidcruft on Friday August 07, 2015 @10:18AM (#10022601)
If you have a directory that you want to expose, you can set that up. It doesn't have to be just ~/Downloads/Firefox. If you want to expose something like ~/Documents but deny access to ~/Documents/Private you can do that. With a little effort, you can probably even configure a helper utility that toggles access on and off dynamically with a status charm in the notifications area.
Re:Firefox exploit found in the wild by anc84 on Friday August 07, 2015 @10:25AM (#10022632)
That sounds incredibly cumbersome, akin to things like umatrix or noscript (which I use but 99% of users would never touch or be able to correctly control).
Re:Firefox exploit found in the wild by fluidcruft on Friday August 07, 2015 @10:32AM (#10022674)
It's only as cumbersome as you choose to make it.