mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-20 10:12:15 +01:00
prepare the 0.2.2.13-alpha changelog
This commit is contained in:
parent
09be26dc51
commit
8afc7d563d
26
ChangeLog
26
ChangeLog
@ -1,3 +1,29 @@
|
||||
Changes in version 0.2.2.13-alpha - 2010-04-24
|
||||
o Major bugfixes:
|
||||
- Relays now close idle circuits early if it looks like they were
|
||||
intended for directory fetches. Relays are also more aggressive
|
||||
about closing TLS connections that have no circuits on them. Such
|
||||
circuits are unlikely to be re-used, and tens of thousands of them
|
||||
were piling up at the fast relays, causing the relays to run out
|
||||
of sockets and memory. Bugfix on 0.2.0.22-rc (where clients started
|
||||
tunneling their directory fetches over TLS).
|
||||
|
||||
o Minor features:
|
||||
- Finally get rid of the deprecated and now harmful notion of
|
||||
"clique mode", where directory authorities maintain TLS connections
|
||||
to every other relay.
|
||||
- Directory authorities now do an immediate reachability check as soon
|
||||
as they hear about a new relay. This change should slightly reduce
|
||||
the time between setting up a relay and getting listed as running
|
||||
in the consensus. It should also improve the time between setting
|
||||
up a bridge and seeing use by bridge users.
|
||||
- Directory authorities no longer launch a TLS connection to every
|
||||
relay as they startup. Now that we have 2k+ descriptors cached,
|
||||
the resulting network hiccup is becoming a burden. Besides,
|
||||
authorities already avoid voting about Running for the first half
|
||||
hour of their uptime.
|
||||
|
||||
|
||||
Changes in version 0.2.2.12-alpha - 2010-04-20
|
||||
Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
|
||||
handle and vote on descriptors. It was causing relays to drop out of
|
||||
|
@ -1,7 +0,0 @@
|
||||
o Major bugfixes:
|
||||
- Relays now close idle circuits early if it looks like they were
|
||||
intended for directory fetches. Such circuits are unlikely to
|
||||
be re-used, and tens of thousands of them were piling up at the
|
||||
fast relays, causing the relays to run out of sockets and memory.
|
||||
Bugfix on 0.2.0.22-rc (where clients started tunneling their
|
||||
directory fetches over TLS).
|
@ -1,6 +0,0 @@
|
||||
o Major bugfixes:
|
||||
- Make relays more aggressive about closing TLS connections that
|
||||
have no circuits on them. Tens of thousands of them were piling
|
||||
up at the fast relays, causing the relays to run out of sockets
|
||||
and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
|
||||
their directory fetches over TLS).
|
@ -1,7 +0,0 @@
|
||||
o Minor features:
|
||||
- Directory authorities now do an immediate reachability check as soon
|
||||
as they hear about a new relay. This change should slightly reduce
|
||||
the time between setting up a relay and getting listed as running
|
||||
in the consensus. It should also improve the time between setting
|
||||
up a bridge and seeing use by bridge users.
|
||||
|
@ -1,4 +0,0 @@
|
||||
o Minor features:
|
||||
- Finally get rid of the deprecated and now harmful notion of
|
||||
"clique mode", where directory authorities maintain TLS connections
|
||||
to every other relay.
|
@ -1,6 +0,0 @@
|
||||
o Minor features:
|
||||
- Directory authorities no longer launch a TLS connection to every
|
||||
relay as they startup. Now that we have 2k+ descriptors cached,
|
||||
the resulting network hiccup is becoming a burden. Besides,
|
||||
authorities already avoid voting about Running for the first half
|
||||
hour of their uptime.
|
Loading…
Reference in New Issue
Block a user