Friday, December 23, 2011

Passive Aggressive Sunset Cookies

Sorry if I disappoint, but this entry is not some new recipe for a tasty bakery treat. 

This is all about swapping out the word “expire” with the term “sunset” and then applying such terminology to files deposited into someone’s file structure as a result of interacting with a web site.

First, the cookies I am referencing are basically scripts designed to provide open portals of communication between your computer and the source of the cookie so the source can chat it up with your computer based on the permissions you gave the cookie combined with the source deciding what it wants to take from you whenever it decides to (can’t let a piece of hardware go lonely for too long, otherwise insecurities might pop up!)

For example, when you access an account with a service provider, it is likely a cookie will be placed in your file structure containing information such as your log-in name and password.  The decision tree theory applied is that an end-user will find far more convenience in being a host to these little transmitters such as with some of the gaming sites that really load up the plate, let alone any analytics being deployed by an operator of a site playing the role of source.

These cookies take on a passive position in the minds of an end-user, usually sinking to the farthest of recesses of ones mind while poking holes in the notion that there is absolutely no such thing as “too aggressive” or even “illegal” about setting expiration dates beyond even a year or two, but even that duration has some elegant attributes that suggest even a 5 or 10 year cookie isn’t too aggressive of a contractual agreement between the host of the transmitter and the receiver of said data.

The representation of aggressive longevity intent is when these cookies are delivered with expiration dates in the 60’s…the 70’s…the 80’s…even the 90’s.  I’m not talking about 20th century references (long live rock n roll baby!), rather these dates all apply to the 21st century.  I’m talking 2060.  2070.  2080.

And although fierce debate typically surrounds attempts to embed some form of a sunset clauses into a variety of legislation to where a tax is promised to expire at a certain date and time, these types of cookies simply aren’t designed to expire through the potential for advancement of such a date each and every time someone visits the source of the cookie…despite the suggestive labeling.

Because these cookie-related activities are so invisible – and yet so active – it’s tough to believe all are yummy treats to be savored and harbored entirely intact, let alone at all.  Unfortunately (perhaps) this isn’t about some elephant convincing the rest of the world there are lives existing on a puff of nature and that proposed destruction would mean total and complete annihilation of a 6, 7 or 8 digit loss of life.  It’s all about wondering how anyone is supposed to keep track of such activities…

especially when a click continues to represent virtual permission to install the cookie in the first place.  No visible disclaimers pop-up prior to deposit.  No forestalling of any kind built into the browsers used to access a site.  Even with browser add-ons adding at least one or two extra steps, there is not one moment whatsoever to where the end-user is forced to at least glance at the permissions being given whenever one of these reaches a system.  There is no formal cookie review interface built into any operating system.

Nope.  If someone wants to take a peek at their list of cookies on their machines, it has to come from a manually-generated search for such items designed to intentionally search for such things, unless you know the directory tree branch such data is deposited into – which typically includes a series of clicks, rather than some form of a one-stop shopping place.

Ain’t it funny how much time and energy continues to be invested into securing a computer from “unwanted intrusions” compared to how much time and energy is spent monetizing all of the data being sucked into so many externally located machines.

Kinda like it being impossible to be guilty of illegal activities if the activities are not designated as illegal.  After all, we’re the ones doing the clicking in the first place.  What does it matter if this click activity gets sent all over the place for analysis, right?

I’d point out in matters plenty, but I think I’ll pass on the opportunity and instead sunset my way out of this particular entry.

A cookie that expires 1/2/2080???  Really???  Serious???

Oh wait!  That’s right.

Now if I could only find where I placed my delete button.