r12983@Kushana: nickm | 2007-05-18 16:46:15 -0400

Note that we do not permit you to exit to port 0, no matter what.  Closes bug 409.


svn:r10211
This commit is contained in:
Nick Mathewson 2007-05-18 21:19:58 +00:00
parent e527dc7e3d
commit 7ae13fad2a
2 changed files with 4 additions and 3 deletions

View File

@ -417,7 +417,7 @@ $Id$
[Any number]
These lines describe the rules that an OR follows when
These lines describe an "exit policy": the rules that an OR follows when
deciding whether to allow a new stream to a given address. The
'exitpattern' syntax is described below. The rules are considered in
order; if no rule matches, the address will be accepted. For clarity,
@ -570,7 +570,8 @@ $Id$
port ::= an integer between 1 and 65535, inclusive.
[Some implementations incorrectly generate ports with value 0.
Implementations SHOULD accept this, and SHOULD NOT generate it.]
Implementations SHOULD accept this, and SHOULD NOT generate it.
Connections to port 0 are never permitted.]
addrspec ::= "*" | ip4spec | ip6spec
ipv4spec ::= ip4 | ip4 "/" num_ip4_bits | ip4 "/" ip4mask

View File

@ -611,7 +611,7 @@ see tor-design.pdf.
where ADDRESS can be a DNS hostname, or an IPv4 address in
dotted-quad format, or an IPv6 address surrounded by square brackets;
and where PORT is encoded in decimal.
and where PORT is a decimal integer between 1 and 65535, inclusive.
[What is the [00] for? -NM]
[It's so the payload is easy to parse out with string funcs -RD]