Mike Perry authored 5 years ago and teor committed 5 years ago

Our monotime mocking forces us to call monotime_init() *before* we set the
mocked time value. monotime_init() thus stores the first ratchet value at
whatever the platform is at, and then we set fake mocked time to some later
value.

If monotime_init() gets a value from the host that is greater than what we
choose to mock time at for our unittests, all subsequent monotime_abosolute()
calls return zero, which breaks all unittests that depend on time moving
forward by updating mocked monotime values.

So, we need to adjust our mocked time to take the weird monotime_init() time
into account, when we set fake time.

Mike Perry authored 6 years ago and teor committed 5 years ago

Hopefully this will stop monotime_absolute_usec() from returning 0 on some
platforms in the tests.

Mike Perry authored 6 years ago and teor committed 5 years ago

Cancel the padding timer by changing order of sent vs recv (sent cancels).

teor authored 5 years ago and Nick Mathewson committed 5 years ago

Fixes bug 29959; bugfix on 0.4.0.2-alpha.

Implements ticket 29897.

juga authored 6 years ago and teor committed 6 years ago

Increment bw file cache lifetime when serving it by HTTP.
And add a constant to define that lifetime.

juga authored 6 years ago and teor committed 6 years ago

Before serving it by HTTP.

juga authored 6 years ago and teor committed 6 years ago

Use flag to do not warn when the bandwidth file is missing trying
to serve it by http.
Also remove double space in the assignement.

juga authored 6 years ago and teor committed 6 years ago

When a directory authority is using a bandwidth file to obtain the
bandwidth values that will be included in the next vote, serve this
bandwidth file at /tor/status-vote/next/bandwidth.z.

rl1987 authored 6 years ago and teor committed 6 years ago

Let's use the same function exit point for BUG() codepath that we're using
for every other exit condition. That way, we're not forgetting to clean up
the memarea.

Part of 29806.

Taylor Yu authored 6 years ago and teor committed 6 years ago

Previously, or_connection_t did not record whether or not the
connection uses a pluggable transport. Instead, it stored the
underlying proxy protocol of the pluggable transport in
proxy_type. This made bootstrap reporting treat pluggable transport
connections as plain proxy connections.

Store a separate bit indicating whether a pluggable transport is in
use, and decode this during bootstrap reporting.

Fixes bug 28925; bugfix on 0.4.0.1-alpha.