fold in changes files so far

This commit is contained in:
Roger Dingledine 2011-03-14 17:28:38 -04:00
parent 626912a81a
commit 704a27b029
7 changed files with 41 additions and 39 deletions

View File

@ -1,3 +1,44 @@
Changes in version 0.2.2.24-alpha - 2011-0?-??
o Major bugfixes:
- Directory authorities now use data collected from their own
uptime observations when choosing whether to assign the HSDir flag
to relays, instead of trusting the uptime value the relay reports in
its descriptor. This change helps prevent an attack where a small
set of nodes with frequently-changing identity keys can blackhole
a hidden service. (Only authorities need upgrade; others will be
fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
- Fix a bug where bridge users who configure the non-canonical
address of a bridge automatically switch to its canonical
address. If a bridge listens at more than one address, it should be
able to advertise those addresses independently and any non-blocked
addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
bug 2510.
- If you configured Tor to use bridge A, and then quit and
configured Tor to use bridge B instead, it would happily continue
to use bridge A if it's still reachable. While this behavior is
a feature if your goal is connectivity, in some scenarios it's a
dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
o Minor bugfixes:
- When we restart our relay, we might get a successful connection
from the outside before we've started our reachability tests,
triggering a warning: "ORPort found reachable, but I have no
routerinfo yet. Failing to inform controller of success." This
bug was harmless unless Tor is running under a controller
like Vidalia, in which case the controller would never get a
REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
fixes bug 1172.
- When a relay has failed several reachability tests, directory
authorities are more accurate at recording when it became
unreachable, so we can in turn provide more accuracy at assigning
Stable, Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves
bug 2716.
o Packaging fixes:
- Create the /var/run/tor directory on startup on OpenSUSE if it is
not already created. Patch from Andreas Stieger. Fixes bug 2573.
Changes in version 0.2.2.23-alpha - 2011-03-08
Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
they restart they don't lose their bandwidth capacity estimate. This

View File

@ -1,9 +0,0 @@
o Minor bugfixes:
- When we restart our relay, we might get a successful connection
from the outside before we've started our reachability tests,
triggering a warning: "ORPort found reachable, but I have no
routerinfo yet. Failing to inform controller of success." This
bug was harmless unless Tor is running under a controller
like Vidalia, in which case the controller would never get a
REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
fixes bug 1172.

View File

@ -1,8 +0,0 @@
o Major bugfixes:
- Fix a bug where bridge users who configure the non-canonical
address of a bridge automatically switch to its canonical
address. If a bridge listens at more than one address, it should be
able to advertise those addresses independently and any non-blocked
addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
bug 2510.

View File

@ -1,6 +0,0 @@
o Major bugfixes:
- If you configured Tor to use bridge A, and then quit and
configured Tor to use bridge B instead, it would happily continue
to use bridge A if it's still reachable. While this behavior is
a feature if your goal is connectivity, in some scenarios it's a
dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.

View File

@ -1,3 +0,0 @@
o Minor packaging issues
- Create the /var/run/tor directory on startup on OpenSUSE if it is
not already created. Patch from Andreas Stieger. Fixes bug 2573.

View File

@ -1,5 +0,0 @@
o Minor features:
- When a relay has failed several reachability tests, be more accurate
at recording when it became unreachable, so we can in turn provide
more accuracy at assigning Stable, Guard, HSDir, etc flags. Bugfix
on 0.2.0.6-alpha. Resolves bug 2716.

View File

@ -1,8 +0,0 @@
o Security fixes:
- Directory authorities now use data collected from rephist when
choosing whether to assign the HSDir flag to relays, instead of
trusting the uptime value the relay reports in its descriptor.
This helps prevent an attack where a small set of nodes with
frequently-changing identity keys can blackhole a hidden service.
(Only authorities need upgrade; others will be fine once they do.)
Bugfix on 0.2.0.10-alpha; fixes bug 2709.