Selaa lähdekoodia

r16923@tombo: nickm | 2008-07-11 15:12:12 -0400
Mark proposal 150 accepted; add risks section; revise English a bit.


svn:r15845

Nick Mathewson 16 vuotta sitten
vanhempi
commit
c319497886

+ 2 - 2
doc/spec/proposals/000-index.txt

@@ -72,7 +72,7 @@ Proposals by number:
 147  Eliminate the need for v2 directories in generating v3 directories [ACCEPTED]
 147  Eliminate the need for v2 directories in generating v3 directories [ACCEPTED]
 148  Stream end reasons from the client side should be uniform [ACCEPTED]
 148  Stream end reasons from the client side should be uniform [ACCEPTED]
 149  Using data from NETINFO cells [OPEN]
 149  Using data from NETINFO cells [OPEN]
-150  Exclude Exit Nodes from a circuit [DRAFT]
+150  Exclude Exit Nodes from a circuit [ACCEPTED]
 151  Improving Tor Path Selection [DRAFT]
 151  Improving Tor Path Selection [DRAFT]
 
 
 
 
@@ -84,7 +84,6 @@ Proposals by status:
    133  Incorporate Unreachable ORs into the Tor Network
    133  Incorporate Unreachable ORs into the Tor Network
    141  Download server descriptors on demand
    141  Download server descriptors on demand
    144  Increase the diversity of circuits by detecting nodes belonging the
    144  Increase the diversity of circuits by detecting nodes belonging the
-   150  Exclude Exit Nodes from a circuit
    151  Improving Tor Path Selection
    151  Improving Tor Path Selection
  OPEN:
  OPEN:
    121  Hidden Service Authentication
    121  Hidden Service Authentication
@@ -105,6 +104,7 @@ Proposals by status:
    140  Provide diffs between consensuses
    140  Provide diffs between consensuses
    147  Eliminate the need for v2 directories in generating v3 directories
    147  Eliminate the need for v2 directories in generating v3 directories
    148  Stream end reasons from the client side should be uniform
    148  Stream end reasons from the client side should be uniform
+   150  Exclude Exit Nodes from a circuit
  META:
  META:
    000  Index of Tor Proposals
    000  Index of Tor Proposals
    001  The Tor Proposal Process
    001  The Tor Proposal Process

+ 28 - 17
doc/spec/proposals/150-exclude-exit-nodes.txt

@@ -3,34 +3,45 @@ Title: Exclude Exit Nodes from a circuit
 Version: $Revision$
 Version: $Revision$
 Author: Mfr
 Author: Mfr
 Created: 2008-06-15
 Created: 2008-06-15
-Status: Draft
+Status: Accepted
 
 
 Overview
 Overview
 
 
-   Right now, Tor user can manually exclude a node of all the part of
+   Right now, Tor users can manually exclude a node from all positions
-   circuits created using the directive ExcludeNodes.  
+   in their circuits created using the directive ExcludeNodes.
-   This proposal makes this exclusion, less restrictive, allowing to 
+   This proposal makes this exclusion less restrictive, allowing users to
-   exclude a node only on the exit part of a circuit.
+   exclude a node only from the exit part of a circuit.
 
 
 Motivation
 Motivation
 
 
-   Helping the integration into vidalia (tor exit branch)or other tools,
+   This feature would Help the integration into vidalia (tor exit
-   of features to exclude a country for exit without reducing 
+   branch) or other tools, of features to exclude a country for exit
-   circuits possibilities, an privacy.
+   without reducing circuits possibilities, and privacy.  This feature
-   This feature could help people from a country were many sites 
+   could help people from a country were many sites are blocked to
-   are blocked to exclude this country for browsing, giving them a 
+   exclude this country for browsing, giving them a more stable
-   more stable navigation.
+   navigation.  It could also add the possibility for the user to
-   Add the possibility for the user to exclude the current used exit
+   exclude a currently used exit node.
-   node. 
+
-   
-   
 Implementation
 Implementation
 
 
    ExcludeExitNodes is similar to ExcludeNodes except it's only
    ExcludeExitNodes is similar to ExcludeNodes except it's only
    the exit node which is excluded for circuit build.
    the exit node which is excluded for circuit build.
-   
+
    Tor doesn't warn if node from this list is not an exit node.
    Tor doesn't warn if node from this list is not an exit node.
 
 
 Security implications:
 Security implications:
 
 
-   Open also possibilities for a future user bad exit reporting.
+   Open also possibilities for a future user bad exit reporting
+
+Risks:
+
+   Use of this option can make users partitionable under certain attak
+   assumptions.  However, ExitNodes already creates this possibility,
+   so there isn't much increased risk in ExcludeExitNods.
+
+   We should still encourage people who exclude an exit node because
+   of bad behavior to report it instead of just adding it to their
+   ExcludeExit list.  It would be unfortunate if we didn't find out
+   about broken exits because of this option.  This issue can probably
+   be addressed sufficiently with documentation.
+