Security/Anonymous Browsing
This page will serve as a design requirements and discussion for an Anonymous Browsing Mode. Whether or not it is implemented, the requirements and goals for such a mode will be documented here.
Anonymous Browsing Mode
Unlike Private Browsing, which mainly attempts to protect a user from a local attacker, Anonymous Browsing will serve to minimize the amount of identifying data that is available to a remote (web or network) attacker (for example, consider the EFF [panopticlick project]). The main motivations behind such a mode are to prevent user tracking and fingerprinting, but there are many use cases.
Scope of this Document
This working document will serve as an explanation of why users will want Anonymous Browsing, how such a mode would behave and what will need to be different in this mode from regular browsing sessions for such a mode to be useful.
Use Cases
...
User Agent Considerations
Caches and History
Fonts and Font Lists
Locale issues, standard font lists, etc.
Advertised Capabilities
User-Agent string, Accept headers, etc.
Plug-Ins
Extensions/Add-Ons
Security
SSL certs, etc.
Impact
How much will this impact web experience for the users? Sure we can break things in the name of anonymity if users opt for such a mode, but how much is tolerable?