[tor-browser-spec/master] Attempt to clarify to browser makers why we split the requirements.

commit d3227737fd866d02d5fd45516b9aeb0271cb7bda Author: Mike Perry <mikeperry-git@fscked.org> Date: Fri Sep 30 15:22:59 2011 -0700 Attempt to clarify to browser makers why we split the requirements. --- docs/design/design.xml | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/design/design.xml b/docs/design/design.xml index 089cd26..52e0999 100644 --- a/docs/design/design.xml +++ b/docs/design/design.xml @@ -370,7 +370,9 @@ maintain and/or restore privacy properties to our users. The security requirements are primarily concerned with ensuring the safe use of Tor. Violations in these properties typically result in serious risk for -the user in terms of immediate deanonymization and/or observability. +the user in terms of immediate deanonymization and/or observability. With +respect to platform support, security requirements are the minimum properties +in order for Tor to support the use of a web client platform. </para> @@ -408,8 +410,10 @@ MUST BE documented. <para> The privacy requirements are primarily concerned with reducing linkability: -the ability for a user's activity on one site to be linked with their -activity on another site without their knowledge or explicit consent. +the ability for a user's activity on one site to be linked with their activity +on another site without their knowledge or explicit consent. With respect to +platform support, privacy requirements are the set of properties that cause us +to prefer one platform over another. </para>
participants (1)
-
mikeperry@torproject.org