News for hackers. Stuff that matters.
Re:Spying on HTTPS by dspillett on Monday August 12, 2019 @08:47AM (#20674900)
> That's the ISP's problem.

No. It is the user's problem, created by the ISP.

> Mine doesn't do that.

Otherwise put: "It isn't a problem for me, so why is anyone working on the issue instead of something that I do care about"

> I trust it more than Google, at any rate.

Fair enough. Though for many, choosing not to use Google properties is a lot easier than choosing not to use an ISP that they don't entirely trust.

Re:Spying on HTTPS by icebraining on Monday August 12, 2019 @08:53AM (#20674954)
How do I choose not to use Google properties, including their ad services, analytics, captcha, maps, etc? Is there at least a comprehensive list of their domains, if I choose to block it all (despite that rendering half the web unusable)?
Re:Spying on HTTPS by minitech on Monday August 12, 2019 @11:54AM (#20676567)
Blocking third parties with a tool like uMatrix will get you some of the way. Then you can generally avoid their products and block them at the top level manually, although it might be hard to avoid visiting websites that use Google Cloud, e-mailing people that use Gmail, or using software maintained by Google.
Re:Spying on HTTPS by dspillett on Monday August 12, 2019 @11:35AM (#20676379)
> How do I choose not to use Google properties

Sorry, I wasn't specific enough. The poster I was replying to was commenting on their browser and I was expanding that to mean their browser and other applications.

Blocking all access to all Google services could be an uncompletable task, unless you start from blocking everything and using a white-list approach only which it unlikely to be practical (on top of creating the whitelist you'd have to monitor it and react when they or one of their related entities buy out or otherwise co-opt services you might have whitelisted in the past.

There are fairly comprehensive (though given the volunteer effort involved I'm sure they aren't 100%) lists available, but I don't know of one specific to Google so you would end up blocking other similar services unless you add your own filter to the filter list before using it.

> if I choose to block it all (despite that rendering half the web unusable)?

I doubt it would make nearly that much unusable. The only one of their services that blocking would stop you using other things is recapcha and I dare say anything "hidden" behind that is also available elsewhere. Blocking analytics isn't going to affect you as a user, maps blocks itself a lot ATM anyway ("this site is configured incorrectly" messages where a map should be because the rules for inlining maps have changed (or their enforcement has) and people haven't updated their pages to reflect the policy change at Google), etc.

Re:Spying on HTTPS by eitland on Monday August 12, 2019 @10:05AM (#20675505)
Host list that lists every one of their domains with ip 0.0.0.0
Re:Spying on HTTPS by syrrim on Monday August 12, 2019 @10:31AM (#20675734)
including every single 1e100 server domain? good luck
Re:Spying on HTTPS by dspillett on Monday August 12, 2019 @11:37AM (#20676393)
Not with a simple hosts file entry, but surely some DNS resolvers support wildcards in their configuration to make this easier?
Re:Spying on HTTPS by userbinator on Monday August 12, 2019 @08:29PM (#20681619)
Otherwise put: "It isn't a problem for me, so why is anyone working on the issue instead of something that I do care about"

No, I mean it's a technological workaround to what is ultimately a policy problem, and those never end well. It also happens to be a workaround that gives Google (and basically all the other anti-user corporatocracy) more power and ostensibly good PR in the form of "security".