(Hi Slashdot & The Register readers. Make sure to check the 2nd part on killing iPhone Evercookie's too) Samy Kamar recently released his tool, evercookie. This uses multiple persistent data stores to set unique identifiers that can be used to identify your browser to a website. While my default Firefox browsing setup is safe against it, I noticed that the "disposable" Safari instance I used was not. I sometimes use a clean Safari instance to test or access things the tinfoil on my Firefox does not let me. Killing the Evercookie - Dominic White
UPDATE: An iPhone developer has turned this into an awesome little SBSetting addon. You'll still need a jailbroken phone but can install it via Cydia. My previous experiments in killing the Evercookie in Safari sparked similar posts describing how to do the same for Chrome and Firefox. Killing the Evercookie - Part2 MobileSafari - Dominic White
samy's home page || follow my twitter || blog || email me || samy kamkar October 11, 2010: Reported on the front page of the New York Times Cookie found: uid = currently not set Click to create an evercookie. Don't worry, the cookie is a random number between 1 and 1000, not enough for me to track you, just enough to test evercookies.
April 4, 2014 , 3:41 pm IE 12 to Support HSTS Encryption Protocol Microsoft confirmed today it will support HTTPS Strict Transport Protocol (HSTS) in Internet Explorer 12, bringing its browser in line with other major vendors in its support of the protocol. Read more...