Podcast
Root Causes 227: Let's Talk About Cookies
Hosted by
Jason Soroko
Fellow
Original broadcast date
May 27, 2022
In this episode we explain the fundamentals of cookies and why, despite their obvious benefits, they present troublesome privacy concerns. We discuss the many ways web users can be tracked including cross-site cookies, tracking pixels, and browser fingerprinting.
Podcast transcript
Lightly edited for flow and brevity.
TCTim CallanWe want to talk about cookies.
TCTim CallanSure. Cookies are a World Wide Web thing. If I had to hazard a quest, I’m going to gamble here and then people are going to yell at their screens that I’m stupid. I bet you that that was a Netscape invention.
In 1994, you went into Netscape and so, why are they called cookies? Think about a fortune cookie. That’s actually where the idea comes from. Which is the idea that it’s something where a message is embedded or a piece of data is embedded. Just like a fortune cookie.
That’s where the term apparently actually came from. The idea of a cookie or a magic cookie, which is what it was called, the idea of a piece of data, a packet of data, that was created, sent and received without changing it, was actually used in Linux for other purposes even before that idea was brought to Netscape and then became the cookie that we know and love, and sometimes not love, today. That’s kind of the history, and I think that’s important to make people understand, but what, there’s a lot of types of cookies. Now they all are formed very, very basically. A cookie contains a name, the cookie’s name, and then there’s a value, and all cookies are based on these pairs of name value, name value, name value. And, of course, you can have a cookie name like just some block of text, and then the value could be – this is the domain that you're at, or this is a piece of data that’s hashed, something or other that’ll allows us to understand from a database entry that we’ve just created that something is in your shopping cart. Therefore, let me just spell it out. Cookies were put into browsers because the World Wide Web essentially is stateless. Every time you make a request of your browser, as a client makes a request to a webserver, it is essentially stateless if you go down far enough into the technology. In order to have something like a shopping cart, which means you’re browsing away, and it remembers the fact that you’ve chosen certain things or the fact that you’ve - and this is where it gets close to us, close to our hearts, Tim – authentication.
TCTim CallanYou are who you are. This is really your online shopping account this is really your social media account; this is really your bank account.
So, there are many other types. That’s a non-exhaustive list, but I think those are the ones interesting to us. I think what’s important now, Tim, is to just recognize. I don’t think it’s the normal session cookies giving cookies a bad name. It’s those persistent and third-party cookies that are problem.
TCTim CallanExactly. Nobody’s upset about the fact that I go back to my online shopping account, and it knows who I am. That doesn’t bother any human being who I’ve ever met. If we didn’t want that, we could just disable cookies, and all these problems would go away, but who among us would be willing to live without that particular bit of functionality?
TCTim CallanWhat you said to me was very much subject to interpretation. I understand that’s a paraphrase, but if it was rather general like that, then I think we would need to ask ourselves the question, who’s supposed to be the arbiter of whether or not this is working for its original intended purpose?
TCTim CallanThat’s why we see those warnings, we all see everywhere.
I’m going to get into two other topics that are related to cookies in a moment, but we’re going to talk about what the browsers have done because if cookies are going to be that difficult and a lot of people are just going to be rejecting all because of the fact that the European laws are going to change such that they have to make it easy to reject cookies, and therefore, maybe most people or enough people would reject all so that their business models might change. What is the industry reaction?
TCTim CallanThis is worth talking about. There’s a famous quote, you are the product. A good rule of thumb is if someone is providing something to you for free that costs them money to produce, such as a social media site, there is a reason why. The reason why has to do with you as somebody who is being tracked or measured or sold to or something along those lines, and that is heavily enabled by cookies. If everyone universally rejected cookies and everyone in the world said I am not going to do anything that involves cookies, then those businesses fundamentally wouldn’t be able to exist, or if they did exist, they’d exist in a radically different way. If advertising had to be general and just poured out to the masses, rather than specific to your usage in some way or your demographics in some way, then that would cut down on the revenue traumatically because you wouldn’t be able to have this targeted advertising model. It’s huge and maybe I’m going to come across as a defender of this stuff here, but at the end of the day if somebody is going to put together something very expensive, like a social media business or some kind of online entertainment business or something like that and they do have to fund it financially and that has to be, let’s say, through advertising, then they are going to pursue the strategy that is most expedient for them to sell the advertising for what they need to operate the site. And your part of the bargain for getting this thing for free is that there’s going to be some kind of tracking built in. If some of us individually can opt out of that bargain, if a small enough number of people do it, that’s fine, but you do kind of get into this prisoner’s dilemma situation. Where, if everybody does it, then it kind of all falls apart for everybody. So, I think what you’re saying, if I may paraphrase, Jason, is the question is being asked, well how do we preserve people’s privacy without just destroying this whole construct that we’ve collectively come up with over the past 25 years. Is that right?
Tons of business models are based off of this. So, we do not want to throw out the baby with the bathwater. In order to make this podcast even juicier, Tim, and not make it just about something just so mundane like cookies, I want to talk about two more topics quickly.
And that is, there are other technologies out there that do similar things - -
TCTim CallanThat essentially do the same thing.
So, tracking pixels to me, I first became aware of that when I was actually helping out a marketing department way, way, way back in the day, and the idea was if you open up an e-mail there’s a snippet of code in the HTML of the e-mail that actually downloads a single pixel. That single pixel was defined as such that the request of that download would notify the marketer - -
TCTim CallanThat the e-mail had been opened.
Let’s talk about, and this is the final bit here, Tim. Let’s talk about browser fingerprinting for a moment because I don’t think people realize just how deep this goes. Even if you got rid of cookies, browser fingerprinting, the science of it has gotten to the point where you could even be using a banner ad blocker. An advertising blocker extension, of which there are many extensions, in your browser and you could still come up completely unique and be able to be fairly uniquely identified. Let me give you an example. A lot of people think that a browser profile is your IP address. That’s one, maybe one data point. It’s not even one of the great ones. A lot of people who are technical enough to know that when your browser makes a request, there’s something called a user agent that you actually give to the website that you're browsing to, and it’s part of the request header, and that’s read and it contains information like you’re using Safari, or you're using Chrome, what version, etc. There’s a user agent. But again, that’s not terribly, terribly unique. You and I, Tim – if we were both using Safari on the same day, we might have a very similar user agent, especially if we were all up to date, etc. Keep in mind, when you are browsing, you are also giving up information such as what’s your primary language set to? In my case, it would be English; what’s my time zone; what’s my operating system? But what a lot of people don’t realize is, well, there are things such as your screen size, your color depth, your system fonts, because web servers want to know how to serve you information, and you're giving up that information through your browser. Additionally, there’s something called a DNT header that you might, as part of your request, say – do not track me. Believe it or not, that also is a – I’m going to introduce this idea, Tim – a bit of entropy that uniquely identifies you because not everybody has the DNT header on. I do, but a lot of people don’t. And that actually more uniquely identifies me.
I’ve got one more little piece to this because I’m going to show you how deep it goes. There’s something out there called a Fingerprint JS Library, short for Fingerprint JavaScript Library. What this does, it actually runs in the background, kind of unbeknownst to you, it’s almost like that single pixel idea. It will run an HTML 5 Canvas or a Web GL function, which essentially is, I’m sure you’ve been to websites, Tim, that look really elaborately fancy and beautiful graphics, etc. Well, if that were cut down to its absolute minimum, HTML 5 Canvas and Web GL also will give a webserver information about your GPU, your graphics drivers. Information that ultimately becomes hashed as what’s known as the canvass fingerprint or the Web GL fingerprint, all the way down to, like, your graphics driver version number. It’s incredible.
TCTim CallanMaybe you’re not truly unique, but the level of intersection of exact matching between two systems has to be phenomenally low.
TCTim CallanYou mean, like, my output device, my volume level, things like that?
So, a bit of shoutout to them just because I found it very fun to go to that site because they’ll tell you how you unique you are with your browser. They’ll tell you whether you trackable. They will calculate your entropy based on your computer browser combination, and they’ll tell you the amount of bits of entropy that you actually are giving out publicly when you are browsing to websites. So very interestingly, when I did this, Tim, it told me that out of the greater than 200,000 browsers that the EFF had tested in the past 45 days, I was completely 100% unique and therefore, utterly trackable, which I found very interesting.
TCTim CallanI was going to guess that for your typical website, probably everyone or damn near everyone who goes there is uniquely trackable.
TCTim CallanI think that’s a great starting point. It’s a great level set. I can start to imagine some of the abuses that can come if you really could say I can uniquely identify any given machine. Then you start to imagine, well, if I know that this machine that was on the site is the same as that machine that was on that site you can start to put together pieces and essentially violate people’s privacy, so that does seem like – you see why people would be concerned about that. You see in particular why the EFF and the EU would be pushing on that as two entities that care very much about these things, and, let’s leave it there, and I’d love to come to the next session, and we’ll talk about the response.