README.rdoc in evercookie-0.0.6 vs README.rdoc in evercookie-0.1.0

- old
+ new

@@ -8,22 +8,25 @@ It's javascript is based on https://github.com/samyk/evercookie javascript. Please note, that evercookie can't be fully reliable for detecting previous visiting of your site/application. For people who know the job it's simple enough to override it. As written on original javascript {site}[http://samy.pl/evercookie/], when creating a new cookie, it uses the following storage mechanisms when available: * Standard {HTTP Cookies}[http://en.wikipedia.org/wiki/HTTP_cookie] -* {Local Shared Objects}[http://en.wikipedia.org/wiki/Local_Shared_Object] (Flash Cookies) -* {Isolated Storage}[http://www.silverlight.net/learn/quickstarts/isolatedstorage/] Silverlight (removed in gem) -* Storing cookies in RGB values of auto-generated, force-cached PNGs using HTML5 Canvas tag to read pixels (cookies) back out -* Storing cookies in and reading out {Web History}[http://samy.pl/csshack/] (removed in gem) +* Flash {Local Shared Objects}[http://en.wikipedia.org/wiki/Local_Shared_Object] (Flash Cookies) +* Silverlight {Isolated Storage}[http://www.silverlight.net/learn/quickstarts/isolatedstorage/] (disabled in gem, due to possible issues with different browsers) +* CSS {History Knocking}[http://samy.pl/csshack/] (turned off in gem due to network intensiveness) * Storing cookies in HTTP {ETags}[http://en.wikipedia.org/wiki/HTTP_ETag] * Storing cookies in {Web cache}[http://en.wikipedia.org/wiki/Web_cache] * {window.name}[http://en.wikipedia.org/wiki/HTTP_cookie=window.name] caching -* Internet Explorer {userData}[http://msdn.microsoft.com/en-us/library/ms531424(VS.85).aspx] storage +* Internet Explorer {userData storage}[http://msdn.microsoft.com/en-us/library/ms531424(VS.85).aspx] +* HTML5 Canvas - Cookie values stored in RGB data of auto-generated, force-cached PNG images * 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}[http://dev.w3.org/html5/webdatabase] via SQLite +* 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] (disabled in gem due to possible user permission request) +* 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. (disabled in gem due to possible user permission request) == Information === RDoc @@ -39,11 +42,11 @@ You can see an example of evercookie working in test/dummy application of this gem == Getting started -Evercookie works was written and tested on Rails 3.2. You can add in to your Gemfile with: +Evercookie works was written and tested on Rails 3.2/4. You can add in to your Gemfile with: gem 'evercookie' Run the bundle command to install it. @@ -112,6 +115,13 @@ # cookie name for png storage config.cookie_png = :evercookie_png # cookie name for etag storage config.cookie_etag = :evercookie_etag - end + end + +=== Hiding evercookie presence in your application + +If you really want to hide that you are using evercookie you should do several things (as I see it): +* precompile assets with compression enabled, it will remove all comments and will change some variables of evercookie JS class +* configure the gem to use paths that don't have 'evercookie' name in them +* but remember, if someone wants to find presence of evercookie, he will \ No newline at end of file