Technology

58131 readers

4401 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

633

Google updates Chrome's Incognito Mode disclaimer to admit it is tracking users (www.ghacks.net)

submitted 8 months ago by throws_lemy@lemmy.nz to c/technology@lemmy.world

67 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] cttttt@lemmy.world 9 points 8 months ago* (last edited 8 months ago) (1 children)

And your ISP can still see which domains you’re going to if you use them as your DNS.

Just so you know, because TLS SNI is not encrypted and not yet universally obfuscated (adoption of this is pretty slow and one of the largest CDN providers had to pause their rollout last I checked), not-even-barely-deep packet inspection can be used to track the sites you visit regardless of your DNS provider or wherever resolution is encrypted. Just do a packet dump and see.

Also, if a website isn't fronted by one of the most popular CDN providers in existence, it can be possible to infer the sites you're visiting based on their server IP addresses.

Although this just shifts where tracking can occur, a VPN is the only reliable way to maybe prevent your ISP from tracking the sites you visit, if this is your desire.

[–] heyoni@lemm.ee 1 points 8 months ago

Yep, I’m aware. It’s how that one guy hacked his airplanes wireless, by setting up a certificate with his domain and the airlines and then using that domain + port 443 as an ssh or vpn tunnel.

So TLS rollout is slow because the websites can still be seen with packet inspection? We’re talking about TLS 1.4 right?