News for hackers. Stuff that matters.
Re:Spying on HTTPS by jakub_g on Monday August 12, 2019 @08:17AM (#20674675)
I assume you've never heard of ISPs or vendors that _inject_ ads and other shenanigans on non-https and decrypted https websites?
Re:Spying on HTTPS by userbinator on Monday August 12, 2019 @08:19AM (#20674689)
That's the ISP's problem. Mine doesn't do that. I trust it more than Google, at any rate.
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".

Re:Spying on HTTPS by Andrex on Monday August 12, 2019 @10:19AM (#20675613)
You should absolutely not trust an ISP more than Google. Google monetizes your data themselves, while ISPs will pass it around to anyone with a couple bucks...

If data privacy is your goal, keeping both at arms length would be ideal... except most people can't choose how much data* ISPs scoop up, or even choose to switch to a competitor if they disagree with an ISP's policies.

*In contrast, you can control a decent amount of what Google collects on you.

Re:Spying on HTTPS by ignoramous on Monday August 12, 2019 @01:22PM (#20677604)
Agree. But...

> Google monetizes your data themselves

That's what I thought abt Facebook and Twitter: It looks like they might ship anonymized (or not) data to third-parties when appropriate. Amazon, too, make a lot of data available to sellers on their platform.

Google could be doing that, too, in the guise of claiming to do something else. Or, it already is.

Re:Spying on HTTPS by userbinator on Monday August 12, 2019 @09:10PM (#20681864)
My goal isn't really "data privacy", but to oppose Google acting like it owns the Internet and doing whatever it wants to further its agenda.
Re:Spying on HTTPS by sascha_sl on Monday August 12, 2019 @08:29AM (#20674765)
Being able to choose your ISP is a luxury many people, especially in the US, do not have. Elsewhere there might be choice, but none are really trustworthy.

This is about disincentivising ISPs. If it's hard for them to pull off, they wouldn't do it and it would become something normal every ISP does.

Re:Spying on HTTPS by stiray on Monday August 12, 2019 @08:39AM (#20674834)
This is the thing US brought to itself. Liberal market with minimum regulations. If in my country ISP would touch the traffic, they would get prosecuted by the state. Selling browsing history? Under wiretapping act (you can imagine some jail time). And I can choose between 3 ISPs in country with 2 million people. And optics with at least 100/100 is normal in "larger" city (village in US terms :D) for $60 including iptv and equipment. LTE practically everywhere.

US people will need to start to complain a lot. You are beeing abused.

Re:Spying on HTTPS by zzzcpan on Monday August 12, 2019 @09:08AM (#20675033)
There are a lot of regulations concerning ISPs in the US, they are just all pro-monopoly regulations, not to enable competition.
Re:Spying on HTTPS by inetknght on Monday August 12, 2019 @10:27AM (#20675693)
In what country do you live?
Re:Spying on HTTPS by zzzcpan on Monday August 12, 2019 @08:34AM (#20674800)
> Being able to choose your ISP is a luxury many people, especially in the US, do not have. Elsewhere there might be choice, but none are really trustworthy.

If you don't trust your ISP you really should use a VPN. You still have to trust your ISP if you don't and nothing that megacorps do can help you there.

Re:Spying on HTTPS by sascha_sl on Monday August 12, 2019 @08:42AM (#20674859)
TLS mitigates 90% of the things a VPN promises to do for you rather well. But you can get that up to 95 running a local DNS resolver with tls upstream.
Re:Spying on HTTPS by kbenson on Monday August 12, 2019 @01:00PM (#20677362)
Isn't that one of the reasons for DNS over HTTPS, which is being rolled out now[1] in some browsers? You can keep your ISP from seeing/intercepting/replacing DNS requests.

1: https://support.mozilla.org/en-US/kb/firefox-dns-over-https

Re:Spying on HTTPS by zzzcpan on Monday August 12, 2019 @01:15PM (#20677525)
There is no 90% or 95% neither with TLS nor with DoH. There are still IP addresses, OS-specific data in IP packets, response sizes, traffic patterns, SNI, active probing data, etc. ISPs can get so much stuff on you, you really should use a VPN if you don't trust your ISP.
Re:Spying on HTTPS by sascha_sl on Wednesday August 14, 2019 @05:04AM (#20693806)
ISPs aren't the NSA, and the NSA has no issue watching your VPN egress.

SNI is probably the most critical here, and it is getting opportunistic encryption.

Threat modeling. Do it.

Re:Spying on HTTPS by zzzcpan on Wednesday August 14, 2019 @06:42AM (#20694183)
ISPs rely on DPI equipment vendors, which do all those things. And no, this is not an NSA level stuff, just your basic commercial traffic analyzing. And in fact, the most common spying ISPs do is not on DNS or HTTP, but just on IP sessions, i.e. netflow data, they record and store it for months or years. This is likely the first thing you need to protect yourself from.

DoH not just doesn't help privacy, it makes it worse for everyone by letting another party to get their DNS data and by centralizing requests on that party to actually help NSA and large scale commercial spying. ISPs are still going to get that data too though. And theoretical possibility of encrypted SNI is definitely not going to prevent that, it's probably not going to be a thing at all, just remember how quickly all the megacorps jumped in to close the equivalent domain fronting technique under a little bit of pressure from governments forcing megacorps to allow governments to identify traffic to censor something specific or get all their networks blacklisted on the IP level.

Megacorp proposed "security" and "privacy" solutions generally do not do anything good for end users at all only take away control from end users. These are the times we live in.

Re:Spying on HTTPS by sascha_sl on Thursday August 15, 2019 @03:51AM (#20703386)