fix up a confusion on the release notes (thanks karsten)
svn:r15793
This commit is contained in:
parent
4a16d044fc
commit
33a1210ec3
|
@ -1422,7 +1422,7 @@ Changes in version 0.2.0.9-alpha - 2007-10-24
|
|||
"Unnamed". Now we can list servers that happen to pick the same
|
||||
nickname as a server that registered two years ago and then
|
||||
disappeared. Partially implements proposal 122.
|
||||
- If the consensus list a router as "Unnamed", the name is assigned
|
||||
- If the consensus lists a router as "Unnamed", the name is assigned
|
||||
to a different router: do not identify the router by that name.
|
||||
Partially implements proposal 122.
|
||||
- Authorities can now come to a consensus on which method to use to
|
||||
|
|
|
@ -226,9 +226,9 @@ Changes in version 0.2.0.30 - 2008-07-xx
|
|||
at least 100KB/s, and consider their bandwidth adequate to be a
|
||||
Guard if it is at least 250KB/s, no matter the medians. This fix
|
||||
complements proposal 107.
|
||||
- Directory authorities now never mark more than 3 servers per IP as
|
||||
Valid and Running. Implements proposal 109, by Kevin Bauer and
|
||||
Damon McCoy.
|
||||
- Directory authorities now never mark more than 2 servers per IP as
|
||||
Valid and Running (or 5 on addresses shared by authorities).
|
||||
Implements proposal 109, by Kevin Bauer and Damon McCoy.
|
||||
- If we're a relay, avoid picking ourselves as an introduction point,
|
||||
a rendezvous point, or as the final hop for internal circuits. Bug
|
||||
reported by taranis and lodger.
|
||||
|
|
Loading…
Reference in New Issue