Nick Mathewson authored 6 years ago and David Goulet committed 5 years ago

We had this previously, but we did it differently in different
places. This implementation is pulled from test_prob_distr.c

We need to keep the gcno files, because they are created at compile time.

Apply data structure changes between 0.4.0 and 0.4.1.

This reverts commit 387d9448.

This test was disabled in 0.4.0 and later, but the fix in #29298 was only
merged to 0.4.1. So this test will never be re-enabled in 0.4.0.

Part of 29500.

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.

getpid() can be really expensive sometimes, and it can fail to
detect some kind of fork+prng mistakes, so we need to avoid it if
it's safe to do so.

This patch might slow down fast_prng a lot on any old operating
system that lacks a way to prevent ram from being inherited, AND
requires a syscall for any getpid() calls.  But it should make sure
that we either crash or continue safely on incorrect fork+prng usage
elsewhere in the future.

Previously we did this for tests only, but it's valuable for getting
proper fork behavior in rand_fast.

This will cause the child process to construct a new one in a nice
safe way.

Closes ticket 29668; bug not in any released Tor.

Closes ticket 29357, and comes with appropriate notions of caution.

When classifying a client's selection of TLS ciphers, if the client
ciphers are not yet available, do not cache the result. Previously,
we had cached the unavailability of the cipher list and never looked
again, which in turn led us to assume that the client only supported
the ancient V1 link protocol.  This, in turn, was causing Stem
integration tests to stall in some cases.  Fixes bug 30021; bugfix
on 0.2.4.8-alpha.

Merge bug30011 new package timelimit with 0.4.0 new package shellcheck.
Move shellcheck into the correct category.

(Travis terminates the job after 10 minutes of no output.)

Diagnostic for 29437.

Fixes bug 30011; bugfix on 0.3.5.4-alpha.