Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/samyk/evercookie

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.
https://github.com/samyk/evercookie

Last synced: about 19 hours ago
JSON representation

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.

Awesome Lists containing this project

README 

        
Evercookie

==========



Evercookie is a Javascript API that produces extremely persistent cookies in a

browser. Its goal is to identify a client even after they've removed standard

cookies, Flash cookies (Local Shared Objects or LSOs), and others.



This is accomplished by storing the cookie data on as many browser storage

mechanisms as possible. If cookie data is removed from any of the storage

mechanisms, evercookie aggressively re-creates it in each mechanism as long as

one is still intact.



If the Flash LSO, Silverlight or Java mechanism is available, Evercookie can even propagate cookies

between different browsers on the same client machine!



By [Samy Kamkar](https://samy.pl), with awesome [contributions from others](https://github.com/samyk/evercookie/graphs/contributors)



Browser Storage Mechanisms

--------------------------



Client browsers must support as many of the following storage mechanisms as

possible in order for Evercookie to be effective.



- Standard [HTTP Cookies](https://en.wikipedia.org/wiki/HTTP_cookie)

- Flash [Local Shared Objects](https://en.wikipedia.org/wiki/Local_Shared_Object)

- Silverlight [Isolated Storage](http://www.silverlight.net/learn/quickstarts/isolatedstorage/)

- CSS [History Knocking](https://samy.pl/csshack/)

- Storing cookies in [HTTP ETags](https://en.wikipedia.org/wiki/HTTP_ETag) ([Backend server](#backend-server) required)

- Storing cookies in [Web cache](https://en.wikipedia.org/wiki/Web_cache) ([Backend server](#backend-server) required)

- [HTTP Strict Transport Security (HSTS)](https://sites.google.com/a/chromium.org/dev/Home/chromium-security/client-identification-mechanisms#TOC-Lower-level-protocol-identifiers) Pinning (works in Incognito mode)

- [window.name caching](https://en.wikipedia.org/wiki/HTTP_cookie#window.name)

- Internet Explorer [userData storage](http://msdn.microsoft.com/en-us/library/ms531424.aspx)

- HTML5 [Session Storage](http://dev.w3.org/html5/webstorage/#the-sessionstorage-attribute)

- HTML5 [Local Storage](http://dev.w3.org/html5/webstorage/#dom-localstorage)

- HTML5 [Global Storage](https://developer.mozilla.org/en/dom/storage#globalStorage)

- HTML5 [Database Storage via SQLite](http://dev.w3.org/html5/webdatabase/)

- HTML5 Canvas - Cookie values stored in RGB data of auto-generated, force-cached PNG images ([Backend server](#backend-server) required)

- HTML5 [IndexedDB](http://www.w3.org/TR/IndexedDB/)

- Java [JNLP PersistenceService](http://docs.oracle.com/javase/1.5.0/docs/guide/javaws/jnlp/index.html)

- Java exploit [CVE-2013-0422](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0422) - Attempts to escape the applet sandbox and write cookie data directly to the user's hard drive.



To be implemented someday (perhaps by you?):



- [TLS Session Resumption](https://www.ietf.org/rfc/rfc5077.txt) Identifiers/Tickets (works in Incognito mode)

- Generating [HTTP Public Key Pinning (HPKP)](https://www.wikiwand.com/en/HTTP_Public_Key_Pinning) certificates per user

- Caching in [HTTP Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication)

- Google Gears

- Using Java to produce a unique key based off of NIC info

- Other methods? Please comment!



The Java persistence mechanisms are developed and maintained by [Gabriel Bauman](http://gabrielbauman.com)

[over here](https://github.com/gabrielbauman/evercookie-applet).



Backend Server

--------------

Some of the storage mechanisms require a backend server. This package comes with PHP implementation of the etag, cache and png backend servers.

- For Node.js version, please visit [node-evercookie](https://github.com/truongsinh/node-evercookie).

- For Django version, please visit [Django Evercookie](https://github.com/gdmka/django_evercookie)



Caveats

-------



Be warned! Evercookie can potentially cause problems for you or your users.



- Some storage mechanisms involve loading Silverlight or Flash in the client

  browser. On some machines this can be a very slow process with lots of disk

  thrashing. On older mobile devices this can render your site unusable.



- CSS History Knocking can cause a large number of HTTP requests when a cookie

  is first being set.



- In some circles, it is considered rude to use Evercookie. Consider your

  reputation and your audience when using Evercookie in production.



- Browser vendors are doing their best to plug many of the holes exploited by

  Evercookie. This is a good thing for the Internet, but it means what works

  today may not work so well tomorrow.



You are responsible for your own decision to use Evercookie. Choose wisely.



Got an idea?

------------



Open a pull request!