8 ms·
Google can track surfing habits without need for HTTP cookies
- polaritron 8y agoHowever, continuous user tracking via TLS session resumption is only possible as long as the browser is not restarted, because this clears the TLS cache. https://svs.informatik.uni-hamburg.de/publications/2018/2018-12-06-Sy-ACSAC-Tracking_Users_across_the_Web_via_TLS_Session_Resumption.pdf https://svs.informatik.uni-hamburg.de/publications/2018/2018...
- lalos 8y agoI wonder if that deletion can be scriptable and triggered on-demand without restarting by a Firefox extension.
- marichards 8y agoSo DNS over HTTPS sounds great.
- judge2020 8y agoI don't see ISPs starting DOH servers up within the next 5 years, so either way, you'll be performing dns lookups to a central server.
- marichards 8y agoI'm under the impression Firefox intends to do DOH with Cloudflare shortly. Does this allow Cloudflare to tie together user sessions to different HTTPS domains? If X and Y are Cloudflare fronted domains, can they now pair sessions? I'm guessing a DOH session queries for domain X and immediately an HTTPS connection appears for X, then queries for Y and another appears at Y. Then the whole DOH session becomes identifiable once Cloudflare fronts any service with email sign in. Unless I'm mistaken at least UDP DNS made the guess work a lot harder because you couldn't pin a session down behind an internet gateway as easily.
- auslander 8y agoCloudflare is not as bad as it looks. It is much worse :) As a reverse proxy, it strips SSL, in fact MITMs your traffic. All your data is in plaintext to Cloudflare, which leaks not only history, but also logins/passwords, IPs, credit card numbers, coin wallets, everything. I don't see obvious solution today for DNS queries be private. Pointing your system to Google or Cloudflare DNS is plainly giving away your browsing history, for free, DOH (dns over https) or not. As of today, all my devices are using always-on VPN, and using my VPN provider's DNS.
- Nerada 8y agoMitigated by uMatrix and other Firewall tools, no? I don't find myself ever needing to allow Google Fonts/Analytics to view a page.
- kawsper 8y agohttps://www.easyjet.com https://www.easyjet.com had a hilarious bug where their menu bar wouldn't work if you were blocking Analytics. But yes, it is often not a problem at all to block Google Fonts/Analytics - almost everything works as expected.
- mook 8y agoThere's actually a bunch of sites that are similarly broken; if any script fails to load (including, yes, analytics) nothing works. That was why I originally started using uBlock origin… it had a thing to shim in that, as opposed to uMatrix which didn't.
- auslander 8y ago> not a problem at all to block Google Fonts Just checked my uBlock Origin on smh.com.au: fonts.gstatic.com are loaded ...
- bogomipz 8y agoThe author states: >"Eight years later, everyone in the business seems keen to point out that TLS version 1.3 will finally address this issue by encrypting session data, although it isn't obvious if the measures taken by IETF actually work." Can someone say why it not yet if the measure taken by the IETF in TLS 1.3 work? Is it simply that this part of the spec hasn't been finalized yet? Or does the author mean something else?
- toast0 8y agoSo, TLS 1.2 servers offer session identifiers in cleartext and client resumption sends them in cleartext also. Which probably means someone watching lots of traffic to Google can correlate users even as they move across ips. TLS 1.3 servers send the session identifiers encrypted to the client, and then the client sends it back in cleartext, but each successful handshake will generate a new identifier; a passive observer will not be able to correlate sessions -- except for retries, but the service owner still could. In TLS 1.3, the server can establish a session ticket any time after the handshake is complete, so conceivably, the server could wait until it had some idea of who you are, and establish a token then which contains your userid. (Anyway, it could always associate a random session id with your userid later)
- bogomipz 8y agoThanks for the clear explanation. Would it not have been more accurate for the author to have stated then that "the measures taken by the IETF in TLS 1.3 will work, although with some caveats"?
- toast0 8y agoI must admit that I had only skimmed the article, and hadn't read the bit about TLS 1.3, until after it was edited. I agree with what it says now :D
- asdfasgasdgasdg 8y agoThere are a lot of dark patterns Google could use to track you if it wanted to. Does it? Who can say besides those on the inside. If you think they're using this, then there are probably half a dozen other methods you also think they are using, so this shouldn't bother you (at least, not any more than you are already bothered). If you don't think they're using any of those half a dozen other methods, you probably shouldn't worry about this one too much either.
- auslander 8y ago> ... if it wanted to Made me smile. Google needs to track you, its their core business model. Defeat is not an option, all methods should be found and blocked. Thankfully Chrome is not the only usable browser, and network requests are detectable.
- stubish 8y agoGoogle does not need to track anyone. Google needs to sell ads, and Google needs to be perceived as the best place to spend your advertising budged. What business case is there for Google to work hard at tracking people, defeating anti-tracking measures? There is a cost to doing that, and I don't see a financial incentive for doing it. There are certainly business cases for Google to not defeat anti-tracking measures, as collecting that sort of data is a liability. However, per previous lawsuits like the mapping cars sniffing WIFI data, perhaps they are still just trying to collect everything they can without thought to if it is a benefit, waste, or liability.
- auslander 8y agoKeyword is targeted ads, it revolutionised the market and made FB and Google rich. The only way to sell an ad placement to white males, with >100k income, in this zip code, with specific health problem is to track those people, and Google tracks them all. FB gets data from your posts and messages, Google gets it from your emails, files, searches, location. Both get data from your browsing history (Like buttons, G-Analytics scripts), as do all the rest of third party trackers (cookies).
- phillipseamore 8y agoSo theoretically possible != proof. A high TLS resumption lifetime is used to decrease latency and it can have a huge impact. The RFC itself recommends a TTL of 24 hours (RFC4346).
- phillipseamore 8y agoAnd this is strange "They found that 80% of websites make a correct use, unsuitable for tracking repeat visitors — just resuming an existing session within the last ten minutes." Just Cloudflare has a 48 hour TTL. (Previously I stated 2 hours)
- phillipseamore 8y agoSorry. Looked at the wrong column. Cloudflare actually has a 48 hour TTL.
- _jal 8y agoThis is why you block the surveillance shops' IP space. They are professional panty-sniffers, dependent on doing so for their dinner. Like trolls and narcissists, your only value to them is instrumental. Assuming you care about these things, communicating with them in any way is against your interests. The internet is a much nicer, safer place when you blackhole the commercial-Stasi-wannabes.
- aawc 8y agoDid you turn on that 'Block dangerous and deceptive content' feature in Firefox' security tab? It works by consulting Google each time you visit a new website. You can imagine the rest. Patently wrong. Here's how the API works: The Update API lets your client applications download hashed versions of the Safe Browsing lists for storage in a local database. URLs can then be checked locally. Only if a match is found in the local database does the client need to send a request to the Safe Browsing servers to verify whether the URL is included on the Safe Browsing lists. From: https://developers.google.com/safe-browsing/v4/update-api https://developers.google.com/safe-browsing/v4/update-api Source: Safe Browsing engineer on Chrome.
- yjftsjthsd-h 8y agoSo then it semi-randomly sends Google URLs you visit? That's better, but I wouldn't say patently wrong. Statistically usually wrong?
- lixtra 8y ago> So then it semi-randomly sends Google URLs you visit? No, it computes a 4 byte hash of the URL (domain?) and if this matches a local DB entry then it asks google for all malicious URLs with that hash (explained in the link of parent). Depending how many entries there are your browser contacts google fairly frequently and then google using techniques mentioned in the article can link your TLS-Cookie to your IP.
- manicdee 8y agoA four byte hash is unique to two billion sites. The collision space with non-mainstream sites you might visit is going to be tiny. It’s as good as sending the actual URL, and possibly even the full path to the document you requested, if the browser has previously asked Google for another site and Google has seen a pattern of browsing from Site A to Site B in browsers not using this “security” feature.
- lixtra 8y ago
- econ4all 8y agoThis unsubstantiated nonsense.
- yuhong 8y agoSide note, I just posted: https://news.ycombinator.com/item?id=17930752 https://news.ycombinator.com/item?id=17930752 I am looking for responses.
- gruez 8y agosecurity.ssl.disable_session_identifiers = true on firefox mitigates this.
- lwansbrough 8y agoAny reason for Mozilla to not have this disabled by default?
- tlarkworthy 8y agoThose session resumption tokens save you redownloading 1- 10kb of certificates every fresh connection and the multiple round trips for the TLS handshake. Its a bandwidth and latency optimization.
- yborg 8y agoThis doesn't seem to be present on 63b2.
- gruez 8y agoit's hidden by default. see: https://bugzilla.mozilla.org/show_bug.cgi?id=967977#c17 https://bugzilla.mozilla.org/show_bug.cgi?id=967977#c17
- badrabbit 8y agoNot just google but run of the mill commercial site use fingerprinting. E.g.: https://github.com/jackspirou/clientjs/blob/master/README.md https://github.com/jackspirou/clientjs/blob/master/README.md https://github.com/Valve/fingerprintjs/blob/master/README.md https://github.com/Valve/fingerprintjs/blob/master/README.md
- tapirl 8y agoThe largest company which tracks surfing habits without need for HTTP cookies is Amazon. When you visit every website hosted on AWS, Amazon tracks you, without saving/reading any cookies. The same is for any server hosting provider companies.
- Dunedan 8y ago> When you visit every website hosted on AWS, Amazon tracks you Is that just an unsubstantial accusation or do you have a source for that?
- nkristoffersen 8y agoAgreed. Would love facts on this.
- rapnie 8y agoYes, that would be interesting to know more about. Potentially there is a lot of data to be harvested, isn't there?
- tapirl 8y agoSurely, there is a lot of lot of. Mainly your IP addresses and your browser fingerprints. Through the two, a server hosting company can collect your browsing habits when you visit the websites they are hosting, without your awareness. Whether or not they really do this is another thing. I mean they just can.
- scrollaway 8y agoAmazon stands to lose billions of dollars if what you say is found to be true. They host governments, banks, health care facilities, payment providers and more, all of which would sue the shit out of AWS if they found this out. So I'm going to go on a limb and say you are probably wrong.
- tapirl 8y ago
- acd 8y agoIs it possible to make a browser extension that replaces Google fonts? In order to replace that function. “Libre fonts” Also remember using free Google dns 8.8.8.8 is not that free they track your dns requests.
- singularity2001 8y agoGo to about:config search for mozilla and google and disable all urls (by prepending wtf_).
- eaburto 8y agoWhat's the impact if using temporary containers in Firefox? Does it still shares TLS session between containers?