mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-24 04:13:28 +01:00
rescue r12440's changelog entry from a dusty corner
of the 0.2.0.9-alpha release notes. svn:r12454
This commit is contained in:
parent
f762923cf8
commit
a5d7ff5f10
13
ChangeLog
13
ChangeLog
@ -13,6 +13,10 @@ Changes in version 0.2.0.10-alpha - 2007-11-10
|
|||||||
- Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
|
- Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
|
||||||
accommodate the growing number of servers that use the default
|
accommodate the growing number of servers that use the default
|
||||||
and are reaching it.
|
and are reaching it.
|
||||||
|
- Directory authorities use a new formula for selecting which nodes
|
||||||
|
to advertise as Guards: they must be in the top 7/8 in terms of
|
||||||
|
how long we have known about them, and above the median of those
|
||||||
|
nodes in terms of weighted fractional uptime.
|
||||||
|
|
||||||
o Major bugfixes:
|
o Major bugfixes:
|
||||||
- Stop servers from crashing if they set a Family option (or
|
- Stop servers from crashing if they set a Family option (or
|
||||||
@ -52,11 +56,6 @@ Changes in version 0.2.0.10-alpha - 2007-11-10
|
|||||||
2004.
|
2004.
|
||||||
|
|
||||||
o Minor features:
|
o Minor features:
|
||||||
- Directory authorities now decide whether routers are stable
|
|
||||||
enough to be guards based not on their MTBF or their uptime, but
|
|
||||||
on their fractional uptime: the fraction of the time that they
|
|
||||||
are online. (No router counts as having uptime until we've known
|
|
||||||
about it for at least 24 hours.)
|
|
||||||
- Clients now hold circuitless TLS connections open for 1.5 times
|
- Clients now hold circuitless TLS connections open for 1.5 times
|
||||||
MaxCircuitDirtiness, since it is likely that they'll need to build
|
MaxCircuitDirtiness, since it is likely that they'll need to build
|
||||||
a circuit over them within that timeframe. Previously, they held
|
a circuit over them within that timeframe. Previously, they held
|
||||||
@ -244,10 +243,6 @@ Changes in version 0.2.0.9-alpha - 2007-10-24
|
|||||||
should exist before trying to replace the current one.
|
should exist before trying to replace the current one.
|
||||||
- Use a more forgiving schedule for retrying failed consensus
|
- Use a more forgiving schedule for retrying failed consensus
|
||||||
downloads than for other types.
|
downloads than for other types.
|
||||||
- Adjust the guard selection formula that authorities use a little more:
|
|
||||||
require guards to be in the top 7/8 in terms of how long we have
|
|
||||||
known about them, and above the median of those nodes in terms of
|
|
||||||
weighted fractional uptime.
|
|
||||||
|
|
||||||
o Minor bugfixes (other directory issues):
|
o Minor bugfixes (other directory issues):
|
||||||
- Correct the implementation of "download votes by digest." Bugfix on
|
- Correct the implementation of "download votes by digest." Bugfix on
|
||||||
|
Loading…
Reference in New Issue
Block a user