10 ms·
The browser vendors could start taking the idea of asking for permission seriously. For WebRTC, browsers could block local addresses. uBlock Origin can do thi
by amluto 11y ago
The browser vendors could start taking the idea of asking for permission seriously.
For WebRTC, browsers could block local addresses. uBlock Origin can do this on Firefox already.
For battery: browsers could treat it like location and ask for permission. Why does the average site need to know my battery status?
For fonts: browsers could standardize a list of system fonts available on each platform. It's 2016 already: web fonts are here, are widely supported, and no legitimate website should be relying on some oddball manually installed font.
This problem is hard to solve, but the Tor browser has it mostly solved. Other browsers could learn from it.
- Freak_NL 11y ago> browsers could standardize a list of system fonts available on each platform. It would probably make sense to completely disable support for local fonts unless permitted by the user (for legacy websites that depend on it). All modern browsers support @font-face, and without @font-face you can always depend on the special keywords serif, sans-serif, and monospace; these will load the system's default font for that category.
- Klathmon 11y agoI hope there is another way to solve it, as I have installed web-fonts to my PC to improve page loading speed for some common fonts I keep seeing (the most recent being the Roboto font stack from google). It would be a shame to have to keep re-downloading that every time.
- Freak_NL 11y agoYou don't have to. Fonts should be (and usually are) offered to the web browser with the instruction to cache them indefinitely. You will only have to re-download them when your cache is cleaned up (due to its size, private browsing, or manually cleaning it). Upcoming technology WOFF2 helps further compress them by a significant margin as well (I've seen up to 50% improvement in size over plain WOFF). The problem is that the behaviour you are describing is also one of the ways a fingerprinter gets its data on your fonts; by specifying an @font-face declaration that first tries for a local font, and only loads a remote font if that is not found. Do this for a short-list of popular but distinct fonts (such as Roboto), and you have a nice amount of bits of identifying data to add to the stack. Also, tricks like these exist (using rendering metrics to detect fonts): http://www.lalit.org/lab/javascript-css-font-detect/ http://www.lalit.org/lab/javascript-css-font-detect/
- Klathmon 11y agoBrowser caches are extremely unreliable and pretty small in the grand scheme of things. On some mobile platforms the browser cache can be replaced entirely by some heavy pages! Plus, even if we assumed "cached forever" actually worked for a significant amount of time, it still doesn't solve the problem that I am hoping to solve. I know many websites use the Roboto font. By installing it I no longer need to ever download that font again. It doesn't matter if it's the first time i'm seeing the site, if they use a CDN, if they link to the bold/light/regular version or their own packed font, etc... I understand that it's a privacy issue, but I'm hoping there is a way to solve that privacy issue without removing that feature.
- cm3 11y agoI would go further and disable remote fonts as well since it's not crucial like images and is an attack vector that should have been avoided. The better solution would have been a shared set of web fonts distributed with browsers, just like certificates.
- WalterSear 11y agoI don't see why fonts are any different from images.
- cm3 11y agoFonts are different in that they're not as crucial to the content as images. You cannot replace an image with an alternative text form while retaining the content, but you can display the content completely with WOFF missing.
- kbenson 11y agoI think the logical conclusion of that argument is to also disable all CSS. Fonts are styling for text, CSS is styling for markup. I think most the arguments against disabling CSS can be used against disabling fonts (barring that people do crazy shit with CSS most often now, so it complicates the issue). Really, in the end, all input accepted from the remote side (including text/html) needs to be vetted and processed by security conscious routines. I don't personally have a reason to assume a font library is more likely to be exploitable than an HTML+CSS parser and layout engine. Based on complexity, I would actually assume the opposite, which is probably right, except we've already found and fixed a lot of the exploits for the HTML parser and layout engine.
- cm3 11y agoOf course you're right, and I didn't mention CSS but thought of it as another utilitarian piece. I agree that the most complex parts are HTML+CSS+JS+DOM+GFX, but some parts cannot be reasonably disabled without breaking it completely.
- 11y ago
- rz2k 11y agoActually, that makes me wonder — if I spoof 5% battery charge will I get fewer annoying features on any sites?
- cm3 11y agoGood idea.
- WalterSear 11y agoYou'll get more ads for chargers and laptop batteries.
- blacksmith_tb 11y ago> Why does the average site need to know my battery status? I would go further and suggest that really no site needs to know it (I am sure there could be a few reasonable uses, but still). Which makes me wonder if we could strike back by abusing the WebRTC spec and fuzzing values like these, instead of simply blocking them.
- jsprogrammer 11y ago> For WebRTC, browsers could block local addresses. That would defeat a huge selling point of WebRTC, the ability to create in-browser p2p connections over the user's local network.
- vitd 11y agoI'm not familiar with WebRTC. What's the use case there? I can't remember ever wanting to create an in-browser p2p connection on my local network. What would it be used for?
- slac 11y agoPlease read the Chrome 48 release notes, WebRTC's default behavior has changed. https://groups.google.com/d/msg/discuss-webrtc/_5hL0HeBeEA/H9Ov1w4QCwAJ https://groups.google.com/d/msg/discuss-webrtc/_5hL0HeBeEA/H...
- MichaelGG 11y agoBut it still ignores the proxy settings and will use STUN to discover your "external IP". Thus users that think they are using a proxy end up not actually doing so.
- greggman 11y agoin-company hangouts, video conferencing, etc. Without p2p on local network that would have go outside the company and back in. Others have pointed out this behavior has changed in Chrome 48. You don't get the local IP unless the page asks for access to the mic/camera which the user has to give permission for.
- jsprogrammer 11y agoWebRTC is a secure real-time protocol for audio, video, and data. You'd want to use it any time you want a high-speed network connection with another user. For example, a multiplayer game or video teleconference.
- slac 11y agoFor WebRTC, this behavior is now default in Chrome since version 48. Please see the release notes here: https://groups.google.com/d/msg/discuss-webrtc/_5hL0HeBeEA/H9Ov1w4QCwAJ https://groups.google.com/d/msg/discuss-webrtc/_5hL0HeBeEA/H...
- voltagex_ 11y agoExactly - most sites don't need my exact location, or access to WebAudio or whatever. It should be a red flag for most sites, however most users won't know how to react in such a situation.