Remove from maint-0.2.2 changes files merged in release-0.2.2 and master

changes/1863_bwhist

@@ -1,16 +0,0 @@
-  o Minor features
-    - Servers now save observed maximum bandwidth throughput rates
-      to their state file (along with total usage, which was already
-      saved) so that they can determine their correct estimated
-      bandwidth on restart.  Resolves bug 1863, where Tor servers
-      would reset their estimated bandwidth to 0 after restarting.
-
-  o Minor bugfixes
-    - Fix a bug in banwidth history state parsing that could have been
-      triggered if a future version of Tor ever changed the timing
-      granularity at which bandwidth history is measured.  Bugfix on
-      Tor 0.1.1.11-alpha.
-    - Correctly clear out dir_read/dir_write history when there is an
-      error parsing any bw history value from the state file. Bugfix on
-      Tor 0.2.2.15-alpha.
-

changes/bug1035

@@ -1,13 +0,0 @@
-  o Minor features (authorities)
-    - Take altered router IP addresses and ORPorts into account when
-      determining router stability.  Previously, if a router changed
-      its IP or ORPort, the authorities would not treat it as having
-      any downtime for the purposes of stability calculation, whereas
-      clients would experience downtime since the change could take a
-      while to propagate to them.  Resolves issue 1035.
-  o Minor bugfixes (authorities)
-    - Try to be more robust to hops back in time when calculating
-      router stability.  Previously, if a run of uptime or downtime
-      appeared to be negative, the calculation could give incorrect
-      results.  Bugfix on 0.2.0.6-alpha.
-

changes/bug1090-general

@@ -1,73 +0,0 @@
-  o Major features and bugfixes (node selection)
-
-    - Revise and unify the meaning of the ExitNodes, EntryNodes,
-      ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and
-      StrictNodes options.  Previously, we had been ambiguous in
-      describing what counted as an "exit" node, and what operations
-      exactly "StrictNodes 0" would permit.  This created confusion
-      when people saw nodes built through unexpected circuits, and
-      made it hard to tell real bugs from surprises.  We now stipulate
-      that the intended behavior is:
-
-	. "Exit", in the context of ExitNodes and ExcludeExitNodes,
-	   means a node that delivers user traffic outside the Tor
-	   network.
-	. "Entry", in the context of EntryNodes and ExcludeEntryNodes,
-	  means a node used as the first hop of a multihop circuit:
-	  it doesn't include direct connections to directory servers.
-	. "ExcludeNodes" applies to all nodes.
-	. "StrictNodes" changes the behavior of ExcludeNodes only.
-	  When StrictNodes is set, Tor should avoid all nodes listed
-	  in ExcludeNodes, even when it will make user requests
-	  fail.  When StrictNodes is *not* set, then Tor should
-	  follow ExcludeNodes whenever it can, except when it must
-	  use an excluded node to perform self-tests, connect to a
-	  hidden service, provide a hidden service, fulfill a .exit
-	  request, upload directory information, or fetch directory
-	  information.
-
-      Collectively, the changes to implement the behavior are a fix for
-      bug 1090.
-
-    - ExcludeNodes now takes precedence over EntryNodes and ExitNodes:
-      if a node is listed in both, it's treated as excluded.
-
-    - ExcludeNodes now applies to directory nodes: as a preference if
-      StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
-      (Don't exclude all the directory authorities and set StrictNodes
-      to 1 unless you really want your Tor to break.)
-
-    - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
-
-    - ExcludeExitNodes now overrides .exit requests.
-
-    - We don't use bridges from ExcludeNodes.
-
-    - When StrictNodes is 1:
-       . We now apply ExcludeNodes to hidden service introduction points
-         and to rendezvous points selected by hidden service users.
-         This can make your hidden service less reliable: use it with
-         caution!
-       . If we have used ExcludeNodes on ourself, do not try self-tests.
-       . If we have excluded all the directory authorities, we will
-         not even try to upload our descriptor if we're a server.
-       . Do not honor .exit requests to an excluded node.
-
-    - Remove a misfeature that caused us to ignore the Fast/Stable flags
-      if ExitNodes was set.  Bugfix on 0.2.2.7-alpha.
-
-    - When the set of permitted nodes changes, we now remove any
-      mappings introduced via TrackExitHosts to now-excluded nodes.
-      Bugfix on 0.1.0.1-rc.
-
-    - We never cannibalize a circuit that had excluded nodes on it,
-      even if StrictNodes is 0.  Bugfix on 0.1.0.1-rc.
-
-    - Improve log messages related to excluded nodes.
-
-    - Revert a change where we would be laxer about attaching streams to
-      circuits than when building the circuits.  This was meant to
-      prevent a set of bugs where streams were never attachable, but our
-      improved code here should make this unnecessary.  Bugfix on
-      0.2.2.7-alpha.
-

changes/bug1090-launch-warning

@@ -1,5 +0,0 @@
-  o Minor features:
-    - Keep track of how many times we launch a new circuit to handle
-      a given stream. Too many launches could indicate an inconsistency
-      between our "launch a circuit to handle this stream" logic and our
-      "attach our stream to one of the available circuits" logic.

changes/bug2004

@@ -1,4 +0,0 @@
-  o Minor features
-    - Log less aggressively about circuit timeout changes, and improve some
-      other circuit timeout messages.  Resolves bug 2004.
-

changes/bug2060

@@ -1,4 +0,0 @@
-  o Minor features
-    - Make sure to disable DirPort if running as a bridge.  DirPorts aren't
-      used on bridges, and it makes bridge scanning way too easy.
-

changes/bug2081_followup

@@ -1,9 +0,0 @@
-  o Minor features (authorities)
-    - Directory authorities now reject relays running any versions of
-      Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
-      known bugs that keep RELAY_EARLY cells from working on rendezvous
-      circuits.  Followup to fix for bug 2081.
-    - Directory authorities now reject relays running any version of Tor
-      older than 0.2.0.26-rc.  That is the earliest version that fetches
-      current directory information correctly.  Fix for bug 2156.
-

changes/bug2097-more

@@ -1,6 +0,0 @@
-  o Minor bugfixes:
-    - Fix a logic error in directory_fetches_from_authorities that
-      would cause all _non_-exits refusing single-hop-like circuits to
-      fetch from authorities, when we wanted to have _exits_ fetch
-      from authorities.  Fix by boboper; fixes more of 2097; bugfix on
-      0.2.2.16-alpha.

changes/bug2146.1

@@ -1,4 +0,0 @@
-  - Major bugfixes:
-    o Fix a bug that could break accounting on 64-bit systems with large
-      time_t values, making them hibernate for impossibly long intervals.
-      Bugfix on 0.0.9pre6; fix for bug 2146; fix by boboper.

changes/bug2181

@@ -1,4 +0,0 @@
-  o Minor features
-    - Log a little more clearly about the times at which we're no longer
-      accepting new connections.  Resolves bug 2181.
-

changes/bug2203

@@ -1,6 +0,0 @@
-  o Minor bugfixes:
-    - Clients should not weight BadExit nodes as Exits in their node
-      selection. Similarly, directory authorities should not count
-      BadExit bandwidth as Exit bandwidth when computing bandwidth-weights.
-      Bugfix on 0.2.2.10-alpha; fixes bug 2203.
-

changes/bug2210

@@ -1,5 +0,0 @@
-  o ?? bugfixes:
-    - Fix a bug that would cause newer streams on a given circuit to
-      get preference when reading bytes from the network.  Fixes bug
-      2210.  Fix by Mashael AlSabah.  This bug was introduced before
-      the first Tor release, in svn revision r152.

changes/bug2230_clean_1

@@ -1,4 +0,0 @@
-  o Minor features
-    - Backport code from 0.2.3.x to allow directory authorities to clean
-      their microdescriptor caches.
-

changes/bug2230_part1

@@ -1,7 +0,0 @@
-  o Minor bugfixes
-    - When loading the microdesc journal, remember its current size.
-      In 0.2.2, this helps prevent the microdesc journal from growing
-      without limit on authorities (who are the only ones to use it in
-      0.2.2).  Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
-      Fix posted by "cypherpunks."
-      

changes/bug2230_part2

@@ -1,5 +0,0 @@
-  o Minor bugfixes
-    - The microdesc journal is supposed to get rebuilt only if it is
-      at least _half_ the length of the store, not _twice_ the length
-      of the store.   Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
-

changes/bug2230_part4

@@ -1,6 +0,0 @@
-  o Minor bugfixes:
-    - Authorities now clean their microdesc cache periodically and when
-      reading from disk initially, not only when adding new descriptors.
-      This prevents a bug where we could lose microdescriptors.  Bugfix
-      on 0.2.2.6-alpha.
-

changes/bug2235

@@ -1,3 +0,0 @@
-  o Minor bugfixes
-    - Avoid crashes when AccountingMax is set on clients.  Fixes bug 2235;
-      Bugfix on 0.2.2.18-alpha.  Diagnosed by boboper.

changes/bug2250

@@ -1,5 +0,0 @@
-  o Minor bugfixes:
-    - Fix an assert that got triggered when using the TestingTorNetwork
-      configuration option and then issuing a GETINFO config-text control
-      command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
-

changes/bug2279

@@ -1,15 +0,0 @@
-  o Minor bugfixes
-    - Avoid a double mark-for-free warning when failing to attach a
-      transparent proxy connection.  Fixes bug 2279.  Bugfix on
-      Tor 0.1.2.1 alpha.
-
-  o Minor features
-    - Detect attempts at the client side to open connections to private
-      IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with a randomly
-      chosen exit node.  Attempts to do so are always ill-defined, generally
-      prevented by exit policies, and usually in error.  This will also
-      help to detect loops in transparent proxy configurations.  You can
-      disable this feature by setting "ClientRejectInternalAddresses 0"
-      in your torrc.
-
-

changes/bug2314

@@ -1,4 +0,0 @@
-  o Minor bugfixes:
-    - Fix a bunch of compile warnings revealed by mingw with gcc 4.5. Fixes
-      bug 2314.
-

changes/bug2317

@@ -1,9 +0,0 @@
-  o Major features:
-    - Introduce minimum/maximum values that a client is going to believe
-      in a consensus. This helps to avoid crashes or worse when a param
-      has a weird value.
-
-  o Major bugfixes:
-    - Prevent crash/heap corruption when cbtnumnodes consensus parameter is
-      set to 0 or large values. Fixes bug 2317.
-

changes/bug2330

@@ -1,7 +0,0 @@
-  o Minor bugfixes
-    - Handle SOCKS messages longer than 128 bytes long correctly, rather
-      than waiting forever for them to finish.  Fixes bug 2330.  Bugfix on
-      0.2.0.16-alpha.  Found by doorss.
-
-
-

changes/bug2331

@@ -1,7 +0,0 @@
-  o Minor bugfixes:
-    - Add assertions to check for overflow in arguments to
-      base32_encode and base32_decode; fix a signed-unsigned
-      comparison there too.  These bugs are not actually reachable in
-      Tor, but it's good to prevent future errors too.  Found by
-      doorss.
-

changes/bug2337

@@ -1,3 +0,0 @@
-  o Minor bugfixes
-    - Detect broken platforms with a signed size_t, and refuse to
-      build there.  Found and analyzed by doorss and rransom.

changes/bug2346

@@ -1,6 +0,0 @@
-  o Minor features
-    - If writing the state file to disk fails, wait up to an hour
-      before retrying again.  (Our old code would retry the write
-      immediately.)  Fixes bug 2346.  Bugfix on Tor 0.1.1.3-alpha.
-
-

changes/bug2358

@@ -1,5 +0,0 @@
-  o Minor features
-    - Enable Address Space Layout Randomization (ASLR) and Data Execution
-      Prevention (DEP) by default on Windows to make it harder for
-      attackers to exploit vulnerabilities.  Patch from John Brooks.
- 

changes/bug2363

@@ -1,6 +0,0 @@
-  o Minor bugfixes
-    - Correctly detect failures to create DNS requests when using Libevent
-      versions before v2.  (Before Libevent 2, we used our own evdns
-      implementation.  Its return values for Libevent's evdns_resolve_*()
-      functions are not consistent with those from Libevent.) Found by
-      Lodger; fixes bug 2363; bugfix on 0.2.2.6-alpha.

changes/bug2364

@@ -1,4 +0,0 @@
-  o Documentation
-    - Document the default socks host and port (127.0.0.1:9050) for
-      tor-resolve.
-

changes/bug2366

@@ -1,8 +0,0 @@
-  o Minor bugfixes
-    - When a relay decides that its DNS is too broken for it to serve
-      as an exit server, it advertised itself as a non-exit, but
-      continued to act as an exit.  This could create accidental
-      partitioning opportunities for users.  Instead, if a relay is
-      going to advertise reject *:* as its exit policy, it should
-      really act with exit policy "reject *:*". Fixes bug 2366.
-      Bugfix on Tor 0.1.2.5-alpha.  Bugfix by user "postman" on trac.

changes/bug2378

@@ -1,8 +0,0 @@
-  o Minor bugfixes
-    - Correctly detect failure to allocate an OpenSSL BIO.  Fixes bug 2378;
-      found by "cypherpunks".   This bug was introduced before the
-      first Tor release, in svn commit r110.
-
-  o Minor code simplifications and refactorings
-    - Always treat failure to allocate an RSA key as an unrecoverable
-      allocation error.

changes/bug2379

@@ -1,5 +0,0 @@
-  o Documentation:
-    - Add missing documentation for the authority-related torrc options
-      RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey.  Resolves
-      issue 2379.
-      

changes/bug2403

@@ -1,6 +0,0 @@
-  o Minor bugfixes:
-    - In the special case where you configure a public exit relay as your
-      bridge, Tor would be willing to use that exit relay as the last
-      hop in your circuit as well. Now we fail that circuit instead.
-      Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
-

changes/bug2409

@@ -1,4 +0,0 @@
-  o Minor bugfixes
-    - Resolve a bug in verifying signatures of directory objects
-      with digests longer than SHA1.  Bugfix on 0.2.2.20-alpha;
-      fixes bug 2409; found by "piebeer".

changes/bug2432

@@ -1,5 +0,0 @@
-  o Minor features:
-    - Provide a log message stating which geoip file we're parsing
-      instead of just stating that we're parsing the geoip file.
-      Implements ticket 2432.
-

changes/bug2433

@@ -1,5 +0,0 @@
-  o Major bugfixes:
-    - Don't assert when changing from bridge to relay or vice versa with a controller.
-      The assert happened because we didn't properly initialize our keys in this case.
-      Bugfix on 0.2.2.18, fixes bug 2433. Issue first discovered by bastik.
-

changes/bug2450

@@ -1,5 +0,0 @@
-  o Minor bugfixes:
-    - Country codes aren't supported in EntryNodes until 0.2.3.x.
-      Don't mention them in the manpage. Fixes bug 2450, issue
-      spotted by keb and G-Lo.
-

changes/bug2504

@@ -1,5 +0,0 @@
-  o Minor bugfixes:
-    - Fix a bug with our locking implementation on windows that couldn't
-      correctly detect when a file was already locked. Fixes bug 2504,
-      bugfix on 0.2.1.6-alpha.
-

changes/bug2510

@@ -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.
-

changes/bug2511

@@ -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.

changes/bug2572

@@ -1,5 +0,0 @@
-  o Minor bugfixes:
-    - Don't crash a bridge authority on SIGHUP if it can't force itself
-      into its routerlist.  Fixes bug 2572.
-
-

changes/bug2573

@@ -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.

changes/bug2660

@@ -1,7 +0,0 @@
-  o Minor bugfixes:
-    - Fix connect() failures on some platforms (BSD, OS X). Bugfix on
-      0.2.0.3-alpha; fixes first part of bug 2660. Patch by piebeer.
-    - Set target port in get_interface_address6() correctly. Bugfix
-      on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug
-      2660.
-

changes/bug2683a

@@ -1,3 +0,0 @@
-  o Minor features
-    - Log the source of a rejected POSTed v3 networkstatus vote.
-

changes/bug2696

@@ -1,5 +0,0 @@
-  o Minor features:
-    - Make compilation with clang possible when using
-      --enable-gcc-warnings by removing two warnings that clang hasn't
-      implemented yet and by fixing a few warnings. Implements ticket
-      2696.

changes/bug2698

@@ -1,6 +0,0 @@
-  o Minor bugfixes:
-    - Fix an issue that prevented static linking of libevent on
-      some platforms (notably Linux). Fixes bug 2698, bugfix on
-      versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
-      the --with-static-libevent configure option).
-

changes/bug2704

@@ -1,5 +0,0 @@
-  o Major bugfixes:
-    - When writing our maximum bw for the current interval to the state
-      file, don't wrongly inflate that value by a factor of 10 anymore.
-      Fixes more of bug 2704.
-

changes/bug2704_part1

@@ -1,5 +0,0 @@
-  o Minor bugfixes:
-    - Fix an issue causing calculation of Tor's average bandwidth as saved
-      in the state file to be 10 times smaller than it should be. Fixes the
-      first part of bug 2704, bugfix on tor-0.2.2.23-alpha.
-

changes/bug2704_part2

@@ -1,5 +0,0 @@
-  o Major bugfixes:
-    - Prevent relays that read their bandwidth history from their state file
-      from arbitrarily inflating that value. Fixes the second half of bug
-      2704, bugfix on tor-0.2.2.23-alpha.
-

changes/bug2716

@@ -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.

changes/bug2722

@@ -1,11 +0,0 @@
-  o Minor bugfixes
-    - Ignore the TunnelDirConns option when determining which HSDir
-      relays are responsible for a hidden service descriptor ID.
-      Currently, clients and hidden services with TunnelDirConns off
-      will skip over HSDir relays which do not advertise a DirPort
-      when making a list of HSDirs responsible for a descriptor ID,
-      even though they would never try to use a HSDir's DirPort to
-      upload or fetch a hidden service descriptor.  Fixes bug 2722;
-      bugfix on 0.2.1.6-alpha.
-
-

changes/bug2756

@@ -1,11 +0,0 @@
-  o Minor bugfixes (spec conformance, performance):
-    - We now ask the other side of a stream (the client or the exit)
-      for more data on that stream when the amount of queued data on
-      that stream dips low enough.  Previously, we wouldn't ask the
-      other side for more data until either it sent us more data
-      (which it wasn't supposed to do if it had exhausted its
-      window!) or until we had completely flushed all our queued
-      data.  Fixing this should improve throughput.  Fixes bug 2756;
-      bugfix on the earliest released versions of Tor (svn commit
-      r152).
-

changes/bug2757

@@ -1,6 +0,0 @@
-  - Minor bugfixes
-    o Avoid a double-mark-for-free warning when failing to attach a
-      transparent proxy connection.  (We thought we had fixed this in
-      0.2.2.23-alpha, but it turns out our fix was checking the wrong
-      connection.)  Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
-      bug) and 0.2.2.23-alpha (the incorrect fix).

changes/bug2899

@@ -1,4 +0,0 @@
-  - Minor bugfixes:
-    o Downgrade "no current certificates known for authority" message from
-      Notice to Info.  Bugfix on 0.2.0.10-alpha; fixes bug 2899.
-

changes/bug2917

@@ -1,4 +0,0 @@
-  o Minor bugfixes
-    - Make the SIGNAL DUMP control-port command work on FreeBSD.  Fixes
-      bug 2917.  Bugfix on 0.1.1.1-alpha.
-

changes/bug2948

@@ -1,7 +0,0 @@
-  o Minor bugfixes
-    - Only limit the lengths of single HS descriptors, even when
-      multiple HS descriptors are published to an HSDir relay in a
-      single POST operation.  Fixes bug 2948; bugfix on 0.2.1.5-alpha.
-      Found by hsdir.
-
-

changes/bug2971

@@ -1,6 +0,0 @@
-  o Minor bugfixes:
-    - Be more consistent in our treatment of file system paths. ~ should
-      get expanded to the user's home directory in the Log config option.
-      Bugfix on 0.2.0.1-alpha, which introduced the feature for the -f and
-      --DataDirectory options.
-

changes/bug2979

@@ -1,9 +0,0 @@
-  o Minor bugfixes:
-    - If the Nickname configuration option wasn't given, Tor used to pick
-      a nickname based on the local hostname as the nickname for a relay.
-      Because nicknames are not very important in today's Tor and the
-      "Unnamed" nickname has been implemented, this is now problematic
-      behaviour: It leaks information about the hostname without being
-      useful at all. Bugfix on tor-0.1.2.2-alpha, which introduced the
-      Unnamed nickname. Fixes bug 2979, reported by tagnaq.
-

changes/bug3012

@@ -1,5 +0,0 @@
-  o Minor features:
-    - Relays can go for weeks without writing out their state file. A
-      relay that crashes would lose its bandwidth history (including
-      capacity estimate), client country statistics, and so on. Now relays
-      checkpoint the file at least every 12 hours. Addresses bug 3012.

changes/bug3020

@@ -1,7 +0,0 @@
-  o Minor bugfixes:
-    - When checking whether a hibernation period has fully elapsed, use
-      the amount of seconds we expect for that period instead of using
-      the new period that just started. This would cause an issue because
-      February is a really short month. Bugfix on 0.2.2.17-alpha;
-      fixes bug 3020.
-

changes/bug3039

@@ -1,5 +0,0 @@
-  o Minor bugfixes:
-    - Write the current time into the LastWritten line in our state file,
-      rather than the time from the previous write attempt. Also, stop
-      trying to use a time of -1 in our log statements. Fixes bug 3039;
-      bugfix on 0.2.2.14-alpha.

changes/bug539_removal

@@ -1,6 +0,0 @@
-  o Removed code
-    - Removed workaround code to handle directory responses from
-      servers that had bug 539 (they would send HTTP status 503
-      responses _and_ send a body too).  Since only server versions
-      before 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer
-      reason to keep the workaround in place.

changes/bytecount

@@ -1,5 +0,0 @@
-  o Minor bugfixes
-    - Fix a off-by-one error in calculating some controller command argument
-      lengths.  Fortunately, this is harmless, the controller code does
-      redundant NUL termination too.  Found by boboper.  Bugfix on
-      0.1.1.1-alpha.

changes/cbt_hi_res

@@ -1,7 +0,0 @@
-  o Minor features
-    - When expiring circuits, use microsecond timers rather than one-second
-      timers.  This can avoid an unpleasant situation where a circuit is
-      launched near the end of one second and expired right near the
-      beginning of the next, and prevent fluctuations in circuit timeout
-      values.
-

changes/cbt_parallel_intro

@@ -1,4 +0,0 @@
-  o Minor features
-    - Use computed circuit-build timeouts to decide when to launch
-      parallel introdution circuits.  (Previously, we would retry
-      after 15 seconds.)

changes/clear_trackexithost

@@ -1,5 +0,0 @@
-  o Minor bugfixes:
-    - Fix a bug in the code where we could keep trying to use a
-      TrackHostExits-based mapping after we failed to reach the intended
-      destination node. Fixes bug 2999. Bugfix on 0.2.0.20-rc.
-

changes/connect_err_reporting

@@ -1,6 +0,0 @@
-  o Minor bugfixes:
-    - Be more careful about reporting the correct error from a failed
-      connect() operation.  Under some circumstances, it was possible to
-      look at an incorrect value for errno when sending the end reason.
-      Bugfix on Tor-0.1.0.1-rc.
-

changes/count_overflow

@@ -1,5 +0,0 @@
-  o Minor bugfixes:
-    - Correctly handle an "impossible" overflow cases in connection
-      byte counting, where we write or read more than 4GB on an edge
-      connection in single second.  Bugfix on 0.1.2.8-beta.
-

changes/doxygen

@@ -1,6 +0,0 @@
-  o Documentation changes
-    - Modernize the doxygen configuration file slightly.  Fixes bug 2707.
-    - Resolve all doxygen warnings except those for missing documentation.
-      Fixes bug 2705.
-    - Add doxygen documentation for more functions, fields, and types.
-

changes/exitnodes_reliable

@@ -1,7 +0,0 @@
-  o Minor features:
-    - If ExitNodes is set, still pay attention to the Fast/Stable
-      status of exits when picking exit nodes.  (We used to ignore
-      these flags when ExitNodes was set, on the grounds that people
-      who set exitnodes wanted all of those nodes to get used, but
-      with the ability to pick exits by country and IP range, this
-      doesn't necessarily make sense any more.)

changes/feature2711

@@ -1,4 +0,0 @@
-  o Minor features
-    - Export GeoIP information on usage to bridge controller even if we have
-      not yet been running for 24 hours.
-

changes/fix2195-fix

@@ -1,6 +0,0 @@
-  o Minor bugfixes:
-    - Do not dereference NULL if a bridge fails to build its
-      extra-info descriptor. Previously, we would have dereferenced
-      NULL. Found by an anonymous commenter on Trac. Bugfix on
-      0.2.2.19-alpha.
-

changes/full_ap_circuits

@@ -1,6 +0,0 @@
-  o Minor bugfixes
-    - When a client finds that an origin circuit has run out of 16-bit
-      stream IDs, we now mark it as unusable for new streams.
-      Previously, we would try to close the entire circuit.  Bugfix on
-      Tor version 0.0.6.
-

changes/gmtime_null

@@ -1,6 +0,0 @@
-  o Minor bugfixes
-    - On some platforms, gmtime and localtime can return NULL under
-      certain circumstances even for well-defined values of time_t.
-      Try to detect and make up for this deficiency.  Possible fix for
-      bug 2077.  Bugfix on all versions of Tor.  Found by boboper.
-

changes/hsdir_assignment

@@ -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.

changes/kill_ftime

@@ -1,7 +0,0 @@
-  o Code simplification and refactoring
-    - Remove the old 'fuzzy time' logic.  It was supposed to be used
-      for handling calculations where we have a known amount of clock
-      skew and an allowed amount of unknown skew.  But we only used it
-      in three places, and we never adjusted the known/unknown skew
-      values.  This is still something we might want to do someday,
-      but if we do, we'll want to do it differently.

changes/log-typo-2011-03-15-01

@@ -1,3 +0,0 @@
-  o Minor bugfixes
-    - Fix a minor typo in a log message.  Bugfix on 0.2.2.6-alpha.
-

changes/log_domains

@@ -1,12 +0,0 @@
-  o Minor features
-    - Make it simpler to specify "All log domains except for A and B".
-      Previously you needed to say "[*,~A,~B]".  Now you can just say
-      "[~A,~B]".
-    - Add a LogMessageDomains option to include the domains of log messages
-      along with the messages.  Without this, there's no way to use
-      log domains without reading the source or doing a lot of guessing
-
-  o Documentation
-    - Add documentation for configuring logging at different severities in
-      different log domains.  We've had this feature since 0.2.1.1-alpha, but
-      for some reason it never made it into the manpage.  Fixes bug 2215.

changes/microdesc-double-free

@@ -1,7 +0,0 @@
-  o Security fixes:
-    - Don't double-free a parsable, but invalid, microdescriptor, even
-      if it is followed in the blob we're parsing by an unparsable
-      microdescriptor.  Fixes an issue reported in a comment on bug 2954.
-      Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
-
-

changes/noroute

@@ -1,5 +0,0 @@
-  - Minor features
-    - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
-      Clients before 0.2.1.27 didn't handle NOROUTE correctly, but
-      such clients are already deprecated because of security bugs.
-

changes/osx_forgotten_compilefix

@@ -1,4 +0,0 @@
-  o Minor bugfixes:
-    - Added a forgotten cast that caused a compile warning on OS X 10.6. Bugfix
-      on 0.2.2.24-alpha.
-

changes/task2196

@@ -1,5 +0,0 @@
-  o Minor features:
-    - Report only the top 10 ports in exit-port stats in order not to
-      exceed the maximum extra-info descriptor length of 50 KB. Implements
-      task 2196.
-

changes/ticket2497

@@ -1,4 +0,0 @@
-  o Minor features:
-    - Ensure that no empty [dirreq-](read|write)-history lines are added
-      to an extrainfo document. Implements ticket 2497.
-

changes/warn-if-get_digest-fails

@@ -1,6 +0,0 @@
-  o Minor bugfixes:
-    - If we fail to compute the identity digest of a v3 legacy
-      keypair, warn, and don't use a buffer-full of junk instead.
-      Bugfix on 0.2.1.1-alpha; fixes bug 3106.
-
-

changes/win_tmp_dir

@@ -1,4 +0,0 @@
-  o Unit tests:
-    - Use GetTempDir to find the proper temporary directory location on
-      Windows when generating temporary files for the unit tests.  Patch
-      by Gisle Vanem.