mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-27 13:53:31 +01:00
start an 0.2.2.14-alpha changelog
This commit is contained in:
parent
1def582217
commit
1d5b2da3a8
66
ChangeLog
66
ChangeLog
@ -1,3 +1,69 @@
|
||||
Changes in version 0.2.2.14-alpha - 2010-06-30
|
||||
o Major bugfixes:
|
||||
- Tor directory authorities no longer crash when started with a
|
||||
cached-microdesc-consensus file in their data directory. Bugfix on
|
||||
0.2.2.6-alpha, fixes bug 1532.
|
||||
- Treat an unset $HOME like an empty $HOME rather than triggering an
|
||||
assert. Fixes bug 1522; bugfix on tor-0.0.8pre1.
|
||||
|
||||
o Major features:
|
||||
- Move to the June 2010 Maxmind GeoLite country db (rather than the
|
||||
June 2009 ip-to-country GeoIP db) for our statistics that count
|
||||
how many users relays are seeing from each country. Now we have
|
||||
more accurate data for many African countries.
|
||||
- Port Tor to build and run correctly on Windows CE systems, using
|
||||
the wcecompat library. Contributed by Valerio Lupi.
|
||||
- New "--enable-gcc-hardening" ./configure flag to turn on gcc
|
||||
compile time hardening options. It ensures that signed ints have
|
||||
defined behavior (-fwrapv), -D_FORTIFY_SOURCE=2 is enabled
|
||||
(requiring -O2), stack smashing protection with canaries
|
||||
(-fstack-protector-all), ASLR protection if supported by the
|
||||
kernel (-fPIE, -pie). Additional security related warnings are
|
||||
enabled. Verified to work on Mac OS X and Debian Lenny.
|
||||
- New "--enable-linker-hardening" ./configure flag to turn on ELF
|
||||
specific hardening features (relro, now). This does not work with
|
||||
Mac OS X or any other non-ELF binary format.
|
||||
|
||||
o New directory authorities:
|
||||
- Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
|
||||
authority.
|
||||
|
||||
o Minor features:
|
||||
- New config option "WarnUnsafeSocks 0" disables the warning that
|
||||
occurs whenever Tor receives only an IP address instead of a
|
||||
hostname. Setups that do DNS locally over Tor are fine, and we
|
||||
shouldn't spam the logs in that case.
|
||||
- Convert the HACKING file to asciidoc, and add a few new sections
|
||||
to it, explaining how we use Git, how we make changelogs, and
|
||||
what should go in a patch.
|
||||
|
||||
o Minor bugfixes:
|
||||
- Build correctly on OSX with zlib 1.2.4 and higher with all warnings
|
||||
enabled.
|
||||
- When a2x fails, mention that the user could disable manpages instead
|
||||
of trying to fix their asciidoc installation.
|
||||
- Where available, use Libevent 2.0's periodic timers so that our
|
||||
once-per-second cleanup code gets called even more closely to
|
||||
once per second than it would otherwise. Fixes bug 943.
|
||||
- If you run a bridge that listens on multiple IP addresses, and
|
||||
some user configures a bridge address that uses a different IP
|
||||
address than your bridge writes in its router descriptor, and the
|
||||
user doesn't specify an identity key, their Tor would discard the
|
||||
descriptor because "it isn't one of our configured bridges", and
|
||||
fail to bootstrap. Now believe the descriptor and bootstrap anyway.
|
||||
Bugfix on 0.2.0.3-alpha.
|
||||
- If OpenSSL fails to make a duplicate of a private or public key, log
|
||||
an error message and try to exit cleanly. May help with debugging
|
||||
if bug 1209 ever remanifests.
|
||||
- Save a couple bytes in memory allocation every time we escape
|
||||
certain characters in a string. Patch from Florian Zumbiehl.
|
||||
- Make it explicit that we don't cannibalize one-hop circuits. This
|
||||
happens in the wild, but doesn't turn out to be a problem because
|
||||
we fortunately don't use those circuits. Many thanks to outofwords
|
||||
for the initial analysis and to swissknife who confirmed that
|
||||
two-hop circuits are actually created.
|
||||
|
||||
|
||||
Changes in version 0.2.1.26 - 2010-05-02
|
||||
Tor 0.2.1.26 addresses the recent connection and memory overload
|
||||
problems we've been seeing on relays, especially relays with their
|
||||
|
@ -1,8 +0,0 @@
|
||||
o Minor bugfixes:
|
||||
- If you run a bridge that listens on multiple IP addresses, and
|
||||
some user configures a bridge address that uses a different IP
|
||||
address than your bridge writes in its router descriptor, and the
|
||||
user doesn't specify an identity key, their Tor would discard the
|
||||
descriptor because "it isn't one of our configured bridges", and
|
||||
fail to bootstrap. Now believe the descriptor and bootstrap anyway.
|
||||
Bugfix on 0.2.0.3-alpha.
|
@ -1,3 +0,0 @@
|
||||
o Minor bugfixes
|
||||
- Treat an unset $HOME like an empty $HOME. Fixes bug 1522; bugfix on
|
||||
tor-0.0.8pre1.
|
@ -1,3 +0,0 @@
|
||||
o Minor documentation fixes
|
||||
- When a2x fails, mention that the user could disable manpages instead
|
||||
of trying to fix their asciidoc installation.
|
@ -1,3 +0,0 @@
|
||||
o Minor bugfixes:
|
||||
- Build correctly on OSX with zlib 1.2.4 and higher with all warnings
|
||||
enabled.
|
@ -1,4 +0,0 @@
|
||||
o Major bugfixes
|
||||
- Tor directory authorities no longer crash when started with a
|
||||
cached-microdesc-consensus file in their data directory. Bugfix on
|
||||
0.2.2.6-alpha, fixes bug 1532.
|
@ -1,12 +0,0 @@
|
||||
Add two new configure flags:
|
||||
--enable-gcc-hardening
|
||||
This turns on gcc compile time hardening options. It ensures that
|
||||
signed ints have defined behavior (-fwrapv), -D_FORTIFY_SOURCE=2 is
|
||||
enabled (requiring -O2), stack smashing protection with canaries
|
||||
(-fstack-protector-all), ASLR protection if supported by the kernel
|
||||
(-fPIE, -pie). Additional security related warnings are enabled.
|
||||
Verified as working on Mac OS X and Debian Lenny.
|
||||
|
||||
--enable-linker-hardening
|
||||
This turns on ELF specific hardening features (relro, now). This does
|
||||
not work with Mac OS X or any other non-ELF binary format.
|
@ -1,4 +0,0 @@
|
||||
o Minor bugfixes
|
||||
- If OpenSSL fails to make a duplicate of a private or public key, log
|
||||
an error message and try to exit cleanly. May help with debugging
|
||||
if bug 1209 ever remanifests.
|
@ -1,6 +0,0 @@
|
||||
o Refactorings:
|
||||
- Make it explicit that we don't cannibalize one-hop circuits. This happens
|
||||
in the wild, but doesn't turn out to be a problem because we fortunately
|
||||
don't use those circuits. Many thanks to outofwords for the initial
|
||||
analysis and to swissknife who confirmed that two-hop circuits are
|
||||
actually created.
|
@ -1,2 +0,0 @@
|
||||
o Minor features
|
||||
- Update to the June 1 2010 Maxmind GeoLite Country database.
|
@ -1,3 +0,0 @@
|
||||
o Minor bugfixes
|
||||
- Save a couple bytes in memory allocation every time we escape
|
||||
certain characters in a string. Patch from Florian Zumbiehl.
|
@ -1,3 +0,0 @@
|
||||
o New directory authorities:
|
||||
- Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
|
||||
authority.
|
@ -1,5 +0,0 @@
|
||||
o Major features:
|
||||
- Move to the Maxmind GeoIP db (rather than the June 2009
|
||||
ip-to-country GeoIP db) for our statistics that count how many
|
||||
users relays are seeing from each country. Now we have more accurate
|
||||
data for many African countries.
|
@ -1,5 +0,0 @@
|
||||
o Minor features:
|
||||
- Allow disabling the warning that occurs whenever Tor receives only
|
||||
an IP address instead of a hostname. Setups that do DNS locally over
|
||||
Tor are fine, and we shouldn't spam the logs in that case.
|
||||
|
@ -1,4 +0,0 @@
|
||||
o Minor features
|
||||
- Where available, use Libevent 2.0's periodic timers so that our
|
||||
once-per-second cleanup code gets called even more closely to
|
||||
once per second than it would otherwise. Fix for bug 943.
|
@ -1,4 +0,0 @@
|
||||
o Major features:
|
||||
- Tor has now been ported to build and run correctly on Windows CE
|
||||
systems, using the wcecompat library. (Valerio Lupi)
|
||||
|
@ -1,4 +0,0 @@
|
||||
o Documentation:
|
||||
- Convert the HACKING file to asciidoc, and add a few new sections
|
||||
to it, explaining how we use Git, how we make changelogs, and
|
||||
what should go in a patch.
|
Loading…
Reference in New Issue
Block a user