Re:Researchers Expose Cunning Online Tracking Service That C...
by joeshaw on Saturday July 30, 2011 @12:38PM
(#2826094)
The main exceptions to this are Flash cookies. These are shared between all browsers for a given user, since they're stored by the Flash plugin itself and independent of individual browsers' profile storage.
Re:Researchers Expose Cunning Online Tracking Service That C...
by joshtynjala on Saturday July 30, 2011 @02:23PM
(#2826303)
"Starting with Flash Player 10.1, Flash Player actively supports the browser's private browsing mode, managing data in local storage so that it is consistent with private browsing. So when a private browsing session ends, Flash Player will automatically clear any corresponding data in local storage."
Source: http://www.adobe.com/devnet/flashplayer/articles/privacy_mod...
Local storage here refers to "Flash cookies".
Re:Researchers Expose Cunning Online Tracking Service That C...
by mooism2 on Saturday July 30, 2011 @03:51AM
(#2825211)
Does it work that way in other browsers too?
Re:Researchers Expose Cunning Online Tracking Service That C...
by thezilch on Saturday July 30, 2011 @05:45AM
(#2825386)
FF5 and IE9 function similar. Non-private and private sessions will not cooperate on the same cache, cookies, ETags, etc. Closing a private session will destroy all local cache, cookies, ETags, etc and is not reinstated when starting future private sessions.
http://imgur.com/a/LjjYf
Here I have a non-private session, where I have request i.js (a second time), invoking an If-None-Match check with my non-private ETag of i.js. Opening a private session, my request to i.js does not invoke my non-private session's ETag and subsequent If-None-Match -- i.js is fetched as if my session has no memory of the URI.
In the second shot, I had closed my private session opened in the first test, and I then opened a new private session, without closing my previous non-private session. Again, my private session requests a new i.js, with no idea of the non-private session's nor the first, now closed, private session's version.
The onus is on browsers to restrict inner-private-session storage from leaking between tabs, but it could be quite messy.