Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox Tweaks – An attempt to make Firefox suck less

github.com

Post reply on HN
Print view View original

61–67 of 67 posts

Re: Firefox Tweaks – An attempt to make Firefox suck less

#61

Post by thaumasiotes »

J_Darnley wrote: post #50
thaumasiotes wrote: post #36

Earlier quoted context omitted.

Who are all these people who apparently run their browser maximized? Web pages generally get worse as the window gets wider. (Unless, of course, they control their own width, but that's its own obvious prompt to stop wasting all your screen space .)

Only with a rubbish, widescreen display are modern websites crap. Get a nice 4:3 or 5:4 display and everything looks good when maximised.

No, it would still have to be a small squarish display. Fixing the aspect ratio won't fix the problem that you have way more space than the website will take.

Re: Firefox Tweaks – An attempt to make Firefox suck less

#62

Post by JoshMnem »

logn wrote: post #17
pbiggar wrote: post #6

Not a great attempt IMO. The networking and UI things are a valiant effort. Mixing them with non-mainstream security concerns are a bad idea. You may feel that safe-browsing is tracking by the man, but advising newbies to turn it off is borderline irresponsible. Similar argument for ipv6 (wtf), error reporting (congrats: your bugs will never be fixed cause firefox doesn't know about them), and geolocation ("why doesn…

> caveat emptor: when firefox upgrades it usually wont change these settings for you It's not so bad. You can sort prefs by user-defined, they're in bold, and each one has a reset-to-default option. Also you can do a whole browser reset which preserves only passwords/bookmarks. Instructions: https://support.mozilla.org/en-US/kb/refresh-firefox-reset-a... And firefox profiles might be handy for this too (from the comm…

You can put the settings in a user.js file that goes in your Firefox Profile folder. Example: https://github.com/j127/firefox-tweaks/blob/master/user.js

Re: Firefox Tweaks – An attempt to make Firefox suck less

#63

Post by TD-Linux »

okasaki wrote: post #44
TD-Linux wrote: post #31

Earlier quoted context omitted.

>only allowed to read files You just let through the vulnerability in PDF.js.

No, you give it read-only access to the files it needs (e.g. /usr/ ) and then everywhere else like /home it can only open *.pdf. Also, no networking.

AppArmor can't do a *.pdf restriction. Even if it could, you still let through access to every pdf on your system.

The point here is that the sandboxing needs to be watertight, or it's simply not effective. pdf.js runs in the JS sandbox, but here the file origin checking failed. Placing an OS-level sandbox around it doesn't help unless it is just as tight.

Re: Firefox Tweaks – An attempt to make Firefox suck less

#64

Post by okasaki »

TD-Linux wrote: post #63
okasaki wrote: post #44

Earlier quoted context omitted.

No, you give it read-only access to the files it needs (e.g. /usr/ ) and then everywhere else like /home it can only open *.pdf. Also, no networking.

AppArmor can't do a *.pdf restriction. Even if it could, you still let through access to every pdf on your system. The point here is that the sandboxing needs to be watertight, or it's simply not effective. pdf.js runs in the JS sandbox, but here the file origin checking failed. Placing an OS-level sandbox around it doesn't help unless it is just as tight.

Uh, yes it can

    allow /**/*.pdf r,

Re: Firefox Tweaks – An attempt to make Firefox suck less

#66

Post by JoshMnem »

tdkl wrote: post #40

Disregarding the majority of rants here, I think it's a great list for everyone to just cherry-pick from for their own needs. It ain't all or nothing.

Yes... it inspired me to make my own version that only has what I need: https://github.com/j127/Better-Firefox

Re: Firefox Tweaks – An attempt to make Firefox suck less

#67

Post by TD-Linux »

okasaki wrote: post #64
TD-Linux wrote: post #63

Earlier quoted context omitted.

AppArmor can't do a *.pdf restriction. Even if it could, you still let through access to every pdf on your system. The point here is that the sandboxing needs to be watertight, or it's simply not effective. pdf.js runs in the JS sandbox, but here the file origin checking failed. Placing an OS-level sandbox around it doesn't help unless it is just as tight.

Uh, yes it can allow /**/*.pdf r,

Wow okay, didn't realize that (was still thinking in extended-attributes SELinux land).
Post reply on HN