Produces persistent, respawning "super" cookies in a browser, abusing over a dozen techniques. Its goal is to identify users after they've removed standard cookies and other privacy data such as Flash cookies (LSOs), HTML5 storage, SilverLight storage, and others.
PD: I don't know if this is posible but JS could generate a SSL client key and browser would store it. Then server ascoiates SSL fingerprint with cookie. But user may notice that key is saved on some browsers.
I got the idea that http://www.html5rocks.com/en/tutorials/file/filesystem/ can be used to store a copy of the cookie.
PD: I don't know if this is posible but JS could generate a SSL client key and browser would store it. Then server ascoiates SSL fingerprint with cookie. But user may notice that key is saved on some browsers.