News for hackers. Stuff that matters.
Re:µBlock for Firefox by mdellabitta on Tuesday January 20, 2015 @10:38AM (#8917373)
I decided to dump extension-based privacy stuff and installed Privoxy instead.

I used to have Ghostery, Disconnect, ABP, and some other things running simultaneously. When you think about it, that's a lot of JS running and iterating the DOM multiple times every time you load a page.

Now there's a single, purpose-built, standalone process written in C doing it. Not going back.

Re:µBlock for Firefox by Tobu on Tuesday January 20, 2015 @02:10PM (#8918788)
This doesn't work with the push to HTTPS. Either you use proxy connect, and Privoxy is no better than /etc/hosts blocking. Or you'd rely on the proxy's poorer and slower implementation of TLS. Certificate verification will suffer (no certificate pinning, no certificate blacklist, no OCSP stapling, no way to verify incomplete chains), no SPDY, no sunsetting of bad ciphers or bad protocols.
Re:µBlock for Firefox by pekk on Tuesday January 20, 2015 @03:13PM (#8919202)
Is there some reason in principle why you can't constructively MITM yourself without using piles of Javascript in the browser?
Re:µBlock for Firefox by euid on Tuesday January 20, 2015 @04:16PM (#8919651)
There is no reason in principle, and you can even do it for kicks.[1] The only issue here is a practical one, as the parent poster described: from an end-user perspective, browsers do SSL/TLS better than ad-blocking proxies.

[1]: An example from the other side of the coin: http://www.wired.com/2010/03/packet-forensics/

Re:µBlock for Firefox by Mandatum on Tuesday January 20, 2015 @02:56PM (#8919101)
Unfortunately HTTPS makes proxy-based privacy stuff unusable without invalidating your SSL/TLS certificate in the browser. Extensions are the only reliable method AFAIK for browsing ad-free, securely. That is, if you consider the extension secure.
Re:µBlock for Firefox by dsl on Tuesday January 20, 2015 @10:16PM (#8921262)
Actually it can make your setup far more secure.

You could move all SSL validation off to your proxy, and generate certificates from your own CA on the fly. Then within your browser or OS you can remove everything except your own CA from the trust store.

Re:µBlock for Firefox by Mandatum on Thursday January 22, 2015 @05:09PM (#8932099)
That would open up sniffing on your local machine/network would it not? I see the benefit of blocking malicious domains at a proxy or hosts file level. But aren't you sacrificing a lot of usability by blocking at a network level?
Re:µBlock for Firefox by notsony on Tuesday January 20, 2015 @10:46AM (#8917437)
Any issues connecting to sites over SSL using Privoxy? I'm thinking mainly of banking web-sites.
Re:µBlock for Firefox by Nanzikambe on Tuesday January 20, 2015 @12:39PM (#8918135)
I've used Privoxy since late 2002 on a Linux gateway box - never had a single issue with SSL.

In fact the only issue I've ever had was building it an forgetting to enable threaded mode ..

Re:µBlock for Firefox by mdellabitta on Tuesday January 20, 2015 @01:05PM (#8918335)
I don't recall any problems, but I use Foxyproxy to connect to it. In the worst case, you can just toggle it off quickly for that site, then turn it on again.
Re:µBlock for Firefox by sdfjkl on Tuesday January 20, 2015 @11:30AM (#8917665)
I've used Privoxy & friends (Glitterblocker on OS X) since the days of junkbusters.com, but with SSL on the rise this no longer works very well for me.
Re:µBlock for Firefox by avree on Tuesday January 20, 2015 @12:02PM (#8917878)
Anyone looking to follow up on this comment should search for "GlimmerBlocker", not GlitterBlocker.

Useful stuff, though, thanks!

Re:µBlock for Firefox by Mandatum on Tuesday January 20, 2015 @02:54PM (#8919084)
GlimmerBlocker works the same as Privoxy, only offering support for HTTP.
Re:µBlock for Firefox by sdfjkl on Saturday January 24, 2015 @12:07PM (#8940147)
Oops, brain fart - sorry :-!
Re:µBlock for Firefox by dormento on Tuesday January 20, 2015 @12:07PM (#8917913)
For anyone searching for a blocking solution on OSX, the name is actually Glimmerblocker. It still works on Yosemite.
Re:µBlock for Firefox by pjc50 on Wednesday January 21, 2015 @11:03AM (#8923641)
It really ought to be possible to have a dynamic browser hook in Firefox's parsing phase to allow pre-manipulation of the DOM (or raw HTML) in native code. However actually finding the right spot in the giant codebase to do this is another matter.
Re:µBlock for Firefox by driverdan on Tuesday January 20, 2015 @01:47PM (#8918627)
What about when you're doing development work on a site that uses content you'd normally block (Analytics, ads, etc)? When I spend a day working I don't want to have to toggle Privoxy every time I want to search for something.
Re:µBlock for Firefox by Torgo on Tuesday January 20, 2015 @05:33PM (#8920121)
You really probably want to use a separate browser profile with no plugins installed. It really sucks when you're trying to debug a problem and it turns out it's some combination of extensions you have installed causing the problem.
Re:µBlock for Firefox by dserodio on Tuesday January 20, 2015 @03:38PM (#8919375)
Use FoxyProxy and create rules that "whitelist" the sites you're working on
Re:µBlock for Firefox by 01Michael10 on Tuesday January 20, 2015 @01:46PM (#8918619)
I agree, you had to many things running... What is the advantage of Disconnect when have ABP and Ghostery installed?
Re:µBlock for Firefox by ultramancool on Tuesday January 20, 2015 @02:14PM (#8918818)
Disconnect is an open alternative to Ghostery as Ghostery has some sketchy sponsors.
Re:µBlock for Firefox by 01Michael10 on Tuesday January 20, 2015 @03:07PM (#8919170)
Unfortunately, Disconnect (new version is $5/month for any protection) is not as good as Ghostery and the sketchy part of it is Ghostrank which is easily disabled.

Your answer was unrelated to my question... mdellabitta stated he was running Disconnect with ABP and Ghostery all together which is redundant and I was asking why he would be doing that.

Re:µBlock for Firefox by scholia on Tuesday January 20, 2015 @07:21PM (#8920661)
Ghostrank is easily disabled, but it's off by default so you don't need to....
Re:µBlock for Firefox by scholia on Wednesday January 21, 2015 @08:43AM (#8923002)
So simple statements of fact get downvoted? HN aspires to be Reddit ;-)
Re:µBlock for Firefox by aerique on Tuesday January 20, 2015 @11:03AM (#8917537)
I used to run Privoxy for years and then came the time of AdBlock, NoScript, etc. Perhaps it is indeed time to look back again.
Re:µBlock for Firefox by exadeci on Tuesday January 20, 2015 @02:18PM (#8918842)
Did you manage to make it work with skype ? (it seems that skype doesn't use the proxy parameters for ads)
Re:µBlock for Firefox by kogus on Tuesday January 20, 2015 @11:46PM (#8921493)
I've found it effective to just watch Skype with Fiddler, and add whatever ad servers it touches to my hosts file, and redirect them to 127.0.0.1 Entries like this work for me:

  #BEGIN: Skype ad servers
  127.0.0.1       rad.msn.com
  127.0.0.1       a.rad.msn.com
  127.0.0.1       secure.adnxs.com
  127.0.0.1       m.adnxs.com
  127.0.0.1       ads1.msads.net
  #END: Skype ad servers
Re:µBlock for Firefox by arthurfm on Tuesday January 20, 2015 @07:03PM (#8920589)
To disable the banner ad you could add https://apps.skype.com/ to your restricted sites list.[1]

[1] http://www.reddit.com/r/LifeProTips/comments/27dihm/lpt_you_...

Re:µBlock for Firefox by X-combinator on Tuesday January 20, 2015 @12:21PM (#8918001)
All I notice is that websites like Wired.com load faster with a ad-blocker.
Re:µBlock for Firefox by mdellabitta on Tuesday January 20, 2015 @01:15PM (#8918418)
Privoxy blocks ads, too.