- Nov 08, 2016
-
-
Nick Mathewson authored
-
teor authored
Lower exponents mean that delays do not vary as much. This helps test networks bootstrap consistently. Bugfix on 20499.
-
- Nov 07, 2016
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
teor authored
-
Nick Mathewson authored
-
Nick Mathewson authored
(Three _is_ a good number for anonymity!)
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
Because as Teor puts it: "[Resetting on 503] is exactly what we don't want when relays are busy - imagine clients doing an automatic reset every time they DoS a relay..." Fixes bug 20593.
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
Merge branch '20499_part1_029_squashed', remote-tracking branches 'teor/bug20591_029' and 'teor/bug20533_029' into maint-0.2.9
-
Nick Mathewson authored
It's only safe to remove the failure limit (per 20536) if we are in fact waiting a bit longer each time we try to download. Fixes bug 20534; bugfix on 0.2.9.1-alpha.
-
Nick Mathewson authored
-
Karsten Loesing authored
-
teor authored
If a consensus expires while we are waiting for certificates to download, stop waiting for certificates. If we stop waiting for certificates less than a minute after we started downloading them, do not consider the certificate download failure a separate failure. Fixes bug 20533; bugfix on commit e0204f21 in 0.2.0.9-alpha.
-
teor authored
Relays do not deliberately launch multiple attempts, so the impact of this bug should be minimal. This fix also defends against bugs like #20499. Bugfix on 0.2.8.1-alpha.
-
Nick Mathewson authored
(OpenSSL 1.1 makes EVP_CIPHER_CTX opaque, _and_ adds acceleration for counter mode on more architectures. So it won't work if we try the older approach, and it might help if we try the newer one.) Fixes bug 20588.
-
Nick Mathewson authored
-
Nick Mathewson authored
(We weren't actually using these ciphers; we were just requing that ciphers of that name existed.) Patch from rubiate. Fixes 20460
-
Nick Mathewson authored
Fixes bug 20536; bugfix on 0.2.9.1-alpha.
-
Nick Mathewson authored
-
Nick Mathewson authored
Fixes bug 20587; bugfix on 35bbf2e4 in 0.2.8.1-alpha.
-
- Nov 06, 2016
-
-
Nick Mathewson authored
-
- Nov 03, 2016
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
In our code to write public keys to a string, for some unfathomable reason since 253f0f16, we would allocate a memory BIO, then set the NOCLOSE flag on it, extract its memory buffer, and free it. Then a little while later we'd free the memory buffer with BUF_MEM_free(). As of openssl 1.1 this doesn't work any more, since there is now a BIO_BUF_MEM structure that wraps the BUF_MEM structure. This BIO_BUF_MEM doesn't get freed in our code. So, we had a memory leak! Is this an openssl bug? Maybe. But our code was already pretty silly. Why mess around with the NOCLOSE flag here when we can just keep the BIO object around until we don't need the buffer any more? Fixes bug 20553; bugfix on 0.0.2pre8
-
Nick Mathewson authored
fixes bug 20551; bugfix on 0.2.1.1-alpha
-
- Nov 02, 2016
-
-
teor authored
Fixup on both: * Refactor, adding a create argument... and * Check every hidden service directory's permissions...
-