148
edits
Thirdparty: Difference between revisions
Jump to navigation
Jump to search
→Implementation
| Line 66: | Line 66: | ||
'''Step 3:''' Implement the first party carry-over rules described above, probably as a separate service such that localstorage etc. can use it. | '''Step 3:''' Implement the first party carry-over rules described above, probably as a separate service such that localstorage etc. can use it. | ||
= Further Steps = | |||
Other services such as localstorage should use a set of policies consistent with the above. | |||
Beyond that, there are many other ways to identify and thus track a browser. The EFF published an excellent study in May, detailing some of the various methods; see http://www.eff.org/deeplinks/2010/05/every-browser-unique-results-fom-panopticlick. From this, we can rank the various bits of information in order of importance (i.e. how useful they are in uniquely identifying a browser): things like UA string, what addons are installed, and (via Flash) the font list of the system. We need to go through these, one by one, and do what we can. For instance, for the UA, we could genericize it in third party contexts (remove specific browser version etc.), by using the same service implemented above. | |||