mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-23 20:03:31 +01:00
fold the changes files into a changelog
This commit is contained in:
parent
70411a50b1
commit
6b4db953c9
48
ChangeLog
48
ChangeLog
@ -1,3 +1,51 @@
|
||||
Changes in version 0.2.2.18-rc - 2010-11-1?
|
||||
o Major bugfixes:
|
||||
- Avoid a crash bug triggered by looking at a dangling pointer while
|
||||
setting the network status consensus. Found by Robert Ransom.
|
||||
Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
|
||||
|
||||
o Minor bugfixes (on Tor 0.2.1.x and earlier):
|
||||
- When we're trying to guess whether we know our IP address as
|
||||
a relay, we would log various ways that we failed to guess
|
||||
our address, but never log that we ended up guessing it
|
||||
successfully. Now add a log line to help confused and anxious
|
||||
relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
|
||||
- Bring the logic that gathers routerinfos and assesses the
|
||||
acceptability of circuits into line. This prevents a Tor OP from
|
||||
getting locked in a cycle of choosing its local OR as an exit for a
|
||||
path (due to a .exit request) and then rejecting the circuit because
|
||||
its OR is not listed yet. Also prevent Tor clients from using an OR
|
||||
running in the same instance as an exit (due to a .exit request)
|
||||
if the OR does not meet the same requirements expected of an OR
|
||||
running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
|
||||
- Correctly describe errors that occur when generating a TLS object
|
||||
when logging them. Previously we would attribute them to a failure
|
||||
while generating a TLS context. Patch by Robert Ransom. Bugfix on
|
||||
0.1.0.4-rc; fixes bug 1994.
|
||||
- Fix warnings that newer versions of autoconf produced during
|
||||
./autogen.sh. These warnings appear to be harmless in our case,
|
||||
but they were extremely verbose. Fixes bug 2020.
|
||||
|
||||
o Minor bugfixes (on Tor 0.2.2.x):
|
||||
- Enable protection of small arrays whenever we build with gcc
|
||||
hardening features, not only when also building with warnings
|
||||
enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
|
||||
- Fix a logic error where servers that _didn't_ act as exits would
|
||||
try to keep their server lists more aggressively up to date than
|
||||
exits, when it was supposed to be the other way around. Bugfix
|
||||
on 0.2.2.17-alpha.
|
||||
|
||||
o Minor features:
|
||||
- Update to the November 1 2010 Maxmind GeoLite Country database.
|
||||
|
||||
o Code simplifications and refactoring:
|
||||
- When we fixed bug 1038 we had to put in a restriction not to send
|
||||
RELAY_EARLY cells for relay cells on rend circuits. This was
|
||||
necessary as long as relays using Tor 0.2.1.3-alpha through
|
||||
0.2.1.18-alpha were active. Since this isn't the case anymore,
|
||||
we unify our behaviour here. Resolves bug 2081.
|
||||
|
||||
|
||||
Changes in version 0.2.2.17-alpha - 2010-09-30
|
||||
Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
|
||||
to use one-hop circuits (which can put the exit relays at higher risk,
|
||||
|
@ -1,6 +0,0 @@
|
||||
o Minor bugfixes:
|
||||
- When we're trying to guess whether we know our IP address as
|
||||
a relay, we would log various ways that we failed to guess
|
||||
our address, but never log that we ended up guessing it
|
||||
successfully. Now add a log line to help confused and anxious
|
||||
relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
|
@ -1,9 +0,0 @@
|
||||
o Minor bugfixes:
|
||||
- Bring the logic that gathers routerinfos and assesses the
|
||||
acceptability of circuits into line. This prevents a Tor OP from getting
|
||||
locked in a cycle of choosing its local OR as an exit for a path (due to
|
||||
a .exit request) and then rejecting the circuit because its OR is not
|
||||
listed yet. Also prevent Tor clients from using an OR running in the same
|
||||
instance as an exit (due to a .exit request) if the OR does not meet the
|
||||
same requirements expected of an OR running elsewhere.
|
||||
Fixes bug 1859; bugfix on 0.2.0-alpha.
|
@ -1,6 +0,0 @@
|
||||
o Minor bugfixes:
|
||||
- Correctly describe errors that occur when generating a TLS object
|
||||
when logging them. Previously we would attribtue them to a failure
|
||||
while generating a TLS context. Bugfix by Robert Ransom. Bugfix
|
||||
on 0.1.0.4-rc.
|
||||
|
@ -1,5 +0,0 @@
|
||||
o Minor bugfixes:
|
||||
- Fix warnings that newer versions of autoconf produced during
|
||||
./autogen.sh. From what I can tell these were harmless in our case,
|
||||
but they were extremely verbose. Fixes bug 2020.
|
||||
|
@ -1,5 +0,0 @@
|
||||
o Minor bugfixes:
|
||||
- Enable protection of small arrays whenever we build with gcc hardening
|
||||
features, not only when also building with warnings enabled. Fixes bug
|
||||
2031; bugfix on 0.2.2.14-alpha. Reported by keb.
|
||||
|
@ -1,5 +0,0 @@
|
||||
o Minor bugfixes:
|
||||
- Fix a logic error where servers that _didn't_ act as exits would
|
||||
try to keep their server lists more aggressively up to date than
|
||||
exits, when it was supposed to be the other way around. Bugfix
|
||||
on 0.2.2.17-alpha.
|
@ -1,3 +0,0 @@
|
||||
o Minor features:
|
||||
- Update to the November 1 2010 Maxmind GeoLite Country database.
|
||||
|
@ -1,6 +0,0 @@
|
||||
o Code simplifications and refactorting:
|
||||
- When we fixed bug 1038 we had to put in a restriction not to send
|
||||
RELAY_EARLY cells for relay cells on rend circuits. This was necessary
|
||||
as long as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
|
||||
active. Since this isn't the case anymore, we unify our behaviour here.
|
||||
Implements bug 2081.
|
@ -1,4 +0,0 @@
|
||||
o Major bugfixes:
|
||||
- Avoid a crash bug triggered by looking at a dangling pointer while
|
||||
setting the network status consensus. Found by Robert Ransom.
|
||||
Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
|
Loading…
Reference in New Issue
Block a user