mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-12-06 19:41:15 +01:00
Initial draft changelog for 0.2.3.1-alpha
This commit is contained in:
@@ -1,6 +0,0 @@
|
||||
o Build changes
|
||||
- Our build system requires automake 1.6 or later to create the
|
||||
Makefile.in files. Previously, you could have used 1.4.
|
||||
This only affects developers and people building Tor from git;
|
||||
people who build Tor from the source distribution without changing
|
||||
the Makefile.am files should be fine.
|
||||
@@ -1,5 +0,0 @@
|
||||
o Minor build changes:
|
||||
- Use autoreconf to launch autoconf, automake, etc from autogen.sh.
|
||||
This is more robust against some of the failure modes associated
|
||||
with running the autotools chain on its own.
|
||||
|
||||
@@ -1,12 +0,0 @@
|
||||
o Major features
|
||||
- Tor can now optionally build with the "bufferevents" buffered IO
|
||||
backend provided by Libevent, when building with Libevent 2.0.7-rc
|
||||
or later. To use this feature, make sure you have the latest possible
|
||||
version of Libevent, and run autoconf with the --enable-bufferevents
|
||||
flag. Using this feature will make our networking code more flexible,
|
||||
lets us stack layers on each other, and let us use more efficient
|
||||
zero-copy transports where available.
|
||||
- As an experimental feature, when using the "bufferevents" buffered
|
||||
IO backend, Tor can try to use Windows's IOCP networking API. This
|
||||
is off by default. To turn it on, add "DisableIOCP 0" to your torrc.
|
||||
|
||||
@@ -1,5 +0,0 @@
|
||||
o Major features:
|
||||
- Allow EntryNodes to include country codes like {de} or IP addresses
|
||||
or network masks. Previously we had disallowed these options
|
||||
because we didn't have an efficient way to keep the list up to
|
||||
date. Resolves bug 1982.
|
||||
@@ -1,4 +0,0 @@
|
||||
o Minor features:
|
||||
- If we did find a configuration file, log a message saying where we found
|
||||
it during startup. Implements ticket 2444.
|
||||
|
||||
@@ -1,6 +0,0 @@
|
||||
o Minor features:
|
||||
- Ordinarily, Tor does not count traffic from private addresses
|
||||
(like 127.0.0.1 or 10.0.0.1) when calculating rate limits or
|
||||
accounting. There is now a new option, CountPrivateBandwidth, to
|
||||
disable this behavior. Patch from Daniel Cagara.
|
||||
|
||||
@@ -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.
|
||||
@@ -1,5 +0,0 @@
|
||||
o Minor features:
|
||||
- Implements --enable-static-tor for configure time. Implements ticket
|
||||
2702. Idea, general hackery and thoughts from Alexei Czeskis, John
|
||||
Gilmore, Jacob Appelbaum.
|
||||
|
||||
@@ -1,4 +0,0 @@
|
||||
o Code simplifications
|
||||
- We no longer need link tor-gencert, tor-resolve, or tor-checkkey
|
||||
against libevent; they don't use them, and our code was already
|
||||
refactored not to force them to use them.
|
||||
@@ -1,3 +0,0 @@
|
||||
o Minor features
|
||||
- If you set the NumCPUs option to 0, Tor will try to detect how many
|
||||
CPUs you have. This is the new default behavior.
|
||||
@@ -1,4 +0,0 @@
|
||||
o Minor features:
|
||||
- Turn on directory request statistics by default and include them in
|
||||
extra-info descriptors. Don't break if we have no GeoIP database.
|
||||
|
||||
@@ -1,4 +0,0 @@
|
||||
o Minor features:
|
||||
- Make logging resolution configurable and change default from 1
|
||||
millisecond to 1 second. Implements enhancement 1668.
|
||||
|
||||
@@ -1,4 +0,0 @@
|
||||
o Minor features:
|
||||
- Relays that set "ConnDirectionStatistics 1" write statistics on the
|
||||
birectional use of connections to disk every 24 hours.
|
||||
|
||||
@@ -1,4 +0,0 @@
|
||||
o Minor features:
|
||||
- Add GeoIP file digest to extra-info descriptor. Implements
|
||||
enhancement 1883.
|
||||
|
||||
@@ -1,4 +0,0 @@
|
||||
o Minor feature removals
|
||||
- Removed old code to work around versions of Tor so old that they
|
||||
used multiple forked processes to handle DNS requests. Such
|
||||
versions of Tor are no longer in use as servers.
|
||||
@@ -1,4 +0,0 @@
|
||||
o Minor features (controller)
|
||||
- Add a new SIGNAL event to the controller interface so that
|
||||
controllers can be notified when Tor handles a signal. Resolves
|
||||
issue 1955. Patch by John Brooks.
|
||||
@@ -1,4 +0,0 @@
|
||||
o Minor features (controller)
|
||||
- Add GETINFO options to get total bytes read and written. Patch
|
||||
from pipe, revised by atagar. Resolves ticket 2345.
|
||||
|
||||
@@ -1,3 +0,0 @@
|
||||
o Minor features
|
||||
- Implement some GETINFO controller fields to provide information about
|
||||
the Tor process's pid, euid, username, and resource limits.
|
||||
@@ -1,7 +0,0 @@
|
||||
o Minor features
|
||||
- Add a new 'Heartbeat' log message type to periodically log a
|
||||
message describing Tor's status at level Notice. This feature
|
||||
is meant for operators who log at notice, adn want to make sure
|
||||
that their Tor server is still working. Implementation by
|
||||
George Kadianakis.
|
||||
|
||||
@@ -1,3 +0,0 @@
|
||||
o Minor bugfixes:
|
||||
- Correct a broken faq link in the INSTALL file. Fixes bug 2307.
|
||||
|
||||
@@ -1,4 +0,0 @@
|
||||
o Major features:
|
||||
- Caches now download and cache all the consensus flavors that
|
||||
they know about. This allows them to assess which microdescriptors
|
||||
they need to fetch.
|
||||
@@ -1,10 +0,0 @@
|
||||
o Code refactorings
|
||||
- Unified our node-listing and selecting logic. We had at least
|
||||
two major ways to look at the question of "which Tor servers do
|
||||
we know about": our list of router descriptors, and the current
|
||||
consensus. We're adding a third in microdescriptors. Having
|
||||
so many systems without an abstraction layer over them was
|
||||
hurting the codebase. Now, we have a new "node_t" abstraction
|
||||
that presents a consistent interface to a client's view of
|
||||
a Tor node, and holds (nearly) all of the mutable state
|
||||
formerly in routerinfo_t and routerstatus_t.
|
||||
@@ -1,6 +0,0 @@
|
||||
o Features:
|
||||
- Servers now accept and queue data on not-yet-connected
|
||||
streams. Previously, such data wasn't allowed. This forced
|
||||
clients to wait for a CONNECTED cell before sending their
|
||||
data, thus adding a round trip to stream setup. (Patch from
|
||||
Ian Goldberg; implements the server side of Proposal 174.)
|
||||
@@ -1,5 +0,0 @@
|
||||
o Code simplifications and refactoring:
|
||||
- Use SSL_get_ex_data to map SSL objects to tor_tls_t objects: there's
|
||||
no need for a hash table.
|
||||
|
||||
|
||||
@@ -1,14 +0,0 @@
|
||||
o Major features:
|
||||
- Tor now has the ability to wrangle NAT devices like a good network cowbot
|
||||
with the tor-fw-helper tool. The tor-fw-helper tool supports Apple's
|
||||
NAT-PMP protocol and the UPnP standard for TCP port mapping. This
|
||||
optional tool may be enabled at compile time by configuring with
|
||||
'--enable-upnp' or '--enable-natpmp' or with both. This tool may be
|
||||
called by hand or by Tor. By configuring the PortForwarding option, Tor
|
||||
will launch the helper on a regular basis to ensure that the NAT mapping
|
||||
is regularly updated. Additionally, a user may also specify an
|
||||
alternative helper by using the PortForwardingHelper option. The helper
|
||||
may be specified by name or with the full path to the helper. The default
|
||||
helper is named 'tor-fw-helper' and any alternative helper must take the
|
||||
tor-fw-helper-spec.txt into account.
|
||||
|
||||
Reference in New Issue
Block a user