7 ms·
This is a great move, but given my history I found this quote funny: "Finally, a word to software authors who might be considering SSL interception: If you wan
by ChuckMcM 12y ago
This is a great move, but given my history I found this quote funny:
"Finally, a word to software authors who might be considering SSL interception: If you want to add features to the Web, don’t intercept, make an extension. All of the major browsers offer extension frameworks (see these links for Firefox, Chrome, IE, Safari, and Opera)."
It's funny because the whole intercept thing is an escalation between ad networks and browser writers.
Basically if you can simulate a search engine, and get someone to put ads on those pages, you can make a bit of money. Back in the day it was all about creating a toolbar that had some features, and oh by the way changed your default search engine. Didn't matter whether those results came from Google, Bing, Blekko, or more recently Yandex. The money was made when the person clicked an ad. (and yes the search provider got some form of remuneration, either for returning the results or as a share of the advertising revenue (or both in some cases).
But given the abuse of the extension eco-system all of the browsers now have really strong protections against switching your search choice, and if you don't do that the toolbar is pretty worthless. So to continue in their business of providing ads when they were not wanted, the folks in "Download Valley"[1] switched to trying to get between you and your search engine of choice and then "helping" it with a few more ads.
[1] Hat tip to Matt Cutts who clued me into that particular name for the cluster of folks who build all this adWare.
- x0x0 12y agoIt would have been a lot better if they'd broken superfish even if installed -- they're potentially leaving the least technically savvy people vulnerable.
- TazeTSchnitzel 12y agoIt wouldn't. They'd see Fx wasn't working, IE was, and assume Fx was broken: https://www.youtube.com/watch?v=ngCIU7b5j-M https://www.youtube.com/watch?v=ngCIU7b5j-M
- userbinator 12y agoIt's funny because the whole intercept thing is an escalation between ad networks and browser writers. ...and what I think is more unfortunate, those who do interception to filter out ads and other crap are caught in the crossfire. Browsers have extensions but to have to write and/or install one for each browser you use (which can be several, particularly if you're a web developer) and keep them in agreement with each other is a pain. It doesn't work for the browsers that are either embedded in apps or don't support any extensions (mobile...), and the abuse of extensions has lead to a situation in which browser vendors are trying to control what extensions you can use: Chrome: https://news.ycombinator.com/item?id=7237725 https://news.ycombinator.com/item?id=7237725 Firefox: https://news.ycombinator.com/item?id=9061592 https://news.ycombinator.com/item?id=9061592 What you can do in an extension with respect to blocking content is also limited by the fact that e.g. a div to be removed would have to be parsed and loaded by the browser before an extension could work on and remove it, whereas a filtering proxy could strip it out completely and spare the browser from having to read a single byte of it. In light of that, I see their "make an extension" statement as basically saying "instead of doing something more generic and cross-browser, we'll tell you to use something that we can have more control over, because security." No thanks.
- RubyPinch 12y agofrom the other view, you get to remove a div as how the browser understands it, as opposed to some non-matching XML/HTML library and then, you are still parsing and loading that part of the page, just in a different program.
- tmzt 12y agoI would say the entire mechanism for extensions that can interact with pages is broken. First, taking Chrome as an example, extensions are given the permission to see, track and interact with all pages loaded in the browser. Essentially, they can inject code, but they can also directly pull data from fill-in forms and other places. Of course, these are the things that people use extensions for, so the ability to modify pages makes sense. Take one of the original extensions that was was used to modify pages at runtime, Greasemonkey. It was designed to attach a user.css to the page, or to run a transform on the page and inject specific DOM elements. Of course, there was nothing stopping an injected piece of script for posting data to a third party, but a cursory examination of the particular Greasemonkey customization would show that immediately, and the script could be flagged and removed from the collection. Now we have extensions that do much more than these user scripts did in Greasemonkey and are self contained and harder to break apart and study. Two examples, Feedly which is my chosen replacement for Reader, has an extension which places a Feedly icon on every page. It doesn't add it to the browser chrome but actually adds it to the DOM of every single page that loads. As similar example is a Chrome extension for managing cookies, but which had a donation function that placed links on pages to donate to the project or something of the sort. Either of these could be accomplished with a small installable transform, and neither required the extension itself to have access to the DOM, the transform script could have handled the limited functionality of enumerating RSS/ATOM links or whatever the other extension did. But both of those extensions requested the amorphous permission of modifying every page you access. In Firefox, at least until recently, unsigned extensions could execute native code in the form of XPCOM libraries, they could modify the entire chrome and run with the same permissions as the browser itself. They could intercept not only DOM calls but low level calls in browser js files which also ran with chrome permissions. By reading a configuration file for a unique string, or, in some cases, guessing, you could find a path where placing a zip file or directory was enough to install an extension, so these extensions rode alongside installers for applications, BHOs in Internet Explorer that also installed themselves into Firefox, and other places that would have a chance of destroying a users experience and perception of Firefox.
- deleted 12y ago[deleted]
- 12y ago