This new option will allow clients to download the newest fresh consensus
much sooner than they normally would do so, even if they previously set
FetchDirInfoEarly. This includes a proper ChangeLog entry and an updated man
page.
* debian-merge: (21 commits)
Bump version to 0.2.1.17-rc
Make "Invalid onion hostname" msg respect SafeLogging.
updated rpm instructions for realtime libevent.
Revise 0.2.1.17-rc changelog.
Make an attempt to fix bug 1024.
Update the year for the copyright statement in two more files
another minor patch to add to 0.2.1.x
and give the bug 969 fixes a changelog
the third piece of bug 969 fixing
the second piece of bug 969 fixing
the first piece of bug 969 fixing
Have eventdns set the "truncated" bit correctly.
stop capping bandwidths we see in the consensus
Added ChangeLog entry for control port fix
Ignore control port commands after a QUIT
Flush long replies over control port on QUIT
add a changelog entry: clients use bw in consensus
Clients now use bandwidth values in the consensus
Serve DirPortFrontPage even if the write bucket is low.
Add warning that the results of --enable-geoip-stats are different from those in master.
...
* commit 'tor-0.2.1.17-rc': (21 commits)
Bump version to 0.2.1.17-rc
Make "Invalid onion hostname" msg respect SafeLogging.
updated rpm instructions for realtime libevent.
Revise 0.2.1.17-rc changelog.
Make an attempt to fix bug 1024.
Update the year for the copyright statement in two more files
another minor patch to add to 0.2.1.x
and give the bug 969 fixes a changelog
the third piece of bug 969 fixing
the second piece of bug 969 fixing
the first piece of bug 969 fixing
Have eventdns set the "truncated" bit correctly.
stop capping bandwidths we see in the consensus
Added ChangeLog entry for control port fix
Ignore control port commands after a QUIT
Flush long replies over control port on QUIT
add a changelog entry: clients use bw in consensus
Clients now use bandwidth values in the consensus
Serve DirPortFrontPage even if the write bucket is low.
Add warning that the results of --enable-geoip-stats are different from those in master.
...
Introduce a threshold of 0.01% of bytes that must be read and written per
port in order to be included in the statistics. Otherwise we cannot include
these statistics in extra-info documents, because they are too big.
Change the labels "-written" and "-read" so that the meanings are as
intended.
The internal error "could not find intro key" occurs when we want to send
an INTRODUCE1 cell over a recently finished introduction circuit and think
we built the introduction circuit with a v2 hidden service descriptor, but
cannot find the introduction key in our descriptor.
My first guess how we can end up in this situation is that we are wrong in
thinking that we built the introduction circuit based on a v2 hidden
service descriptor. This patch checks if we have a v0 descriptor, too, and
uses that instead.
o Minor features:
- If we're a relay and we change our IP address, be more verbose
about the reason that made us change. Should help track down
further bugs for relays on dynamic IP addresses.
when we write out our stability info, detect relays that have slipped
through the cracks. log about them and correct the problem.
if we continue to see a lot of these over time, it means there's another
spot where relays fall out of the routerlist without being marked as
unreachable.
Marks the control port connection for flushing before closing when
the QUIT command is issued. This allows a QUIT to be issued during
a long reply over the control port, flushing the reply and then
closing the connection. Fixes bug 1015.
This just got a little complicated, since old clients use "clipped
advertised bandwith" and new clients now use "consensus bandwidth" but
fall back to "clipped advertised bandwidth".
rather than the bandwidth values in each relay descriptor. This approach
opens the door to more accurate bandwidth estimates once the directory
authorities start doing active measurements. Implements more of proposal
141.
arma's rationale: "I think this is a bug, since people intentionally
set DirPortFrontPage, so they really do want their relay to serve that
page when it's asked for. Having it appear only sometimes (or roughly
never in Sebastian's case) makes it way less useful."
Fixes bug 1013; bugfix on 0.2.1.8-alpha.
