aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2017-11-08small edits to changelogNick Mathewson
2017-11-08start on 0.3.2.4-alpha changelogNick Mathewson
2017-11-08Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
2017-11-08Merge branch 'bug23816_029_squashed' into maint-0.3.2Nick Mathewson
2017-11-08Replace our random-exponential-delay algorithm.Nick Mathewson
This patch has implementations of the "decorrelated" and "full" algorithms from https://www.awsarchitectureblog.com/2015/03/backoff.html
2017-11-07Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
2017-11-07Revert "Remove an erroneous 0.5 in compute_weighted_bandwidths()"Nick Mathewson
This reverts commit 01e984870a7e1db2722e85fe43af7bcb4755c2d4.
2017-11-07Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
2017-11-07Merge remote-tracking branch 'dgoulet/bug24161_032_01' into maint-0.3.2Nick Mathewson
2017-11-07Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
2017-11-07Bump to 0.3.2.4-alphaNick Mathewson
2017-11-07Add a safe guard to avoid using a zeroed voting scheduleDavid Goulet
dirvote_get_next_valid_after_time() is the only public function that uses the voting schedule outside of the dirvote subsystem so if it is zeroed, recalculate its timing if we can that is if a consensus exists. Part of #24161 Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-11-07Recalculate voting schedule first when getting a new consensusDavid Goulet
Because the HS and SR subsystems can use the voting schedule early (with the changes in #23623 making the SR subsystem using the static voting schedule object), we need to recalculate the schedule very early when setting the new consensus. Fixes #24161 Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-11-07Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
2017-11-07Merge remote-tracking branch 'asn/ticket23623_032_01' into maint-0.3.2Nick Mathewson
2017-11-07Add changes file for #23623.George Kadianakis
2017-11-06Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
2017-11-06Merge branch 'bug24150_032_squashed' into maint-0.3.2Nick Mathewson
2017-11-06Fix a memory leak on decryption non-failure of v3 hsdescNick Mathewson
If it decrypts something that turns out to start with a NUL byte, then decrypt_desc_layer() will return 0 to indicate the length of its result. But 0 also indicates an error, which causes the result not to be freed by decrypt_desc_layer()'s callers. Since we're trying to stabilize 0.3.2.x, I've opted for the simpler possible fix here and made it so that an empty decrypted string will also count as an error. Fixes bug 24150 and OSS-Fuzz issue 3994. The original bug was present but unreachable in 0.3.1.1-alpha. I'm calling this a bugfix on 0.3.2.1-alpha since that's the first version where you could actually try to decrypt these descriptors.
2017-11-06Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
2017-11-06Fix a 32-bit formatting warningNick Mathewson
2017-11-06Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
2017-11-06Merge remote-tracking branch 'public/bug23318_029' into maint-0.3.2Nick Mathewson
2017-11-05Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
2017-11-05lintchanges: Allow 'fixes bugs a, b, and c'Nick Mathewson
2017-11-05Merge branch 'bug21394_029' into maint-0.3.2Nick Mathewson
2017-11-05Fix DNS resolution on busy exit relaysSebastian Hahn
Thanks to Dhalgren who analyzed this issue two years ago and found a solution!
2017-11-05Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
2017-11-05ticket21031 changes file revised.Nick Mathewson
2017-11-04ClientDNSRejectInternalAddresses in non-default networksSebastian Hahn
Once again allow the flag to be set, unless the default network is used. Thanks to nickm for a suggestion for the workaround to a test failure.
2017-11-04Undo deprecation of ClientDNSRejectInternalAddressesSebastian Hahn
2017-11-04Revert "Make ClientDNSRejectInternalAddresses testing-only."Sebastian Hahn
This reverts commit 27fa4a98d23972213122fa99499efa4baebe49e3.
2017-11-02Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
2017-11-02nodelist: Downgrade warning to protocol warningDavid Goulet
The node_get_ed25519_id() warning can actually be triggered by a relay flagged with NoEdConsensus so instead of triggering a warning on all relays of the network, downgrade it to protocol warning. Fixes #24025 Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-11-02Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
2017-11-02Merge branch 'dgoulet_ticket23753_032_02_squashed' into maint-0.3.2Nick Mathewson
2017-11-02sched: Rate limit scheduler_bug_occurred()David Goulet
Just in case we end up hitting a SCHED_BUG() multiple times, rate limit the log warning. Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-11-02sched: Add another SCHED_BUG() callsiteMatt Traudt
2017-11-02sched: Use SCHED_BUG() macro in schedulerDavid Goulet
When a BUG() occurs, this macro will print extra information about the state of the scheduler and the given channel if any. This will help us greatly to fix future bugs in the scheduler especially when they occur rarely. Fixes #23753 Signed-off-by: David Goulet <dgoulet@torproject.org>
2017-11-02Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
2017-11-02Test that IPv6-only clients can use microdescriptorsteor
When running "make test-network-all", test that IPv6-only clients can use microdescriptors. IPv6-only microdescriptor client support was fixed in tor 0.3.0.1-alpha. Requires chutney master 61c28b9 or later. Closes ticket 24109.
2017-11-02Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
2017-11-02Tweak a comment for a minor but important distinctionNick Mathewson
2017-11-02Merge branch 'ticket23820_032_01_squashed' into maint-0.3.2Nick Mathewson
2017-11-02Changes file for 23820teor
2017-11-02Don't run IPv6-only v3 single onion service tests using chutneyteor
Part of #23820.
2017-11-02Stop users configuring IPv6-only v3 single onion servicesteor
They are not yet implemented: they will upload descriptors, but won't be able to rendezvous, because IPv6 addresses in link specifiers are ignored. Part of #23820.
2017-11-02Improve v3 onion service logging for intro and rend pointsteor
Diagnostics for #23820.
2017-11-02Remove buggy IPv6 and ed25519 handling from get_lspecs_from_extend_info()teor
The previous version of this function had the following issues: * it didn't check if the extend_info contained an IPv6 address, * it didn't check if the ed25519 identity key was valid. But we can't add IPv6 support in a bugfix release. Instead, BUG() if the address is an IPv6 address, so we always put IPv4 addresses in link specifiers. And ignore missing ed25519 identifiers, rather than generating an all-zero link specifier. This supports v3 hidden services on IPv4, dual-stack, and IPv6, and v3 single onion services on IPv4 only. Part of 23820, bugfix on 0.3.2.1-alpha.
2017-11-01Merge branch 'maint-0.3.2' into release-0.3.2Nick Mathewson
7apu2bq3rhoylwmucxizk54afw5jyda7pho4j5zdcqpwkufke7zdzwad.onion