- 23 Jan, 2019 3 commits
-
-
Nick Mathewson authored
-
Nick Mathewson authored
"ours" merge to avoid dropping non-broken changes files after removal of merged 0.2.9 changes files.
-
Nick Mathewson authored
Many of these files cause check-changes to fail, which will be a long-term problem as we continue to support 0.2.9.
-
- 18 Jan, 2019 2 commits
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
- 09 Jan, 2019 1 commit
-
-
teor authored
Stop logging "Tried to establish rendezvous on non-OR circuit..." as a warning. Instead, log it as a protocol warning, because there is nothing that relay operators can do to fix it. Fixes bug 29029; bugfix on 0.2.5.7-rc.
-
- 08 Jan, 2019 3 commits
-
-
Nick Mathewson authored
-
Nick Mathewson authored
"Ours" to avoid version bump.
-
Nick Mathewson authored
-
- 07 Jan, 2019 6 commits
-
-
Nick Mathewson authored
-
Nick Mathewson authored
"ours" merge to avoid version bump.
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Karsten Loesing authored
-
- 04 Jan, 2019 6 commits
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
- 03 Jan, 2019 3 commits
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
In theory it would be better to detect this bug in advance, but this approach is much simpler, and therefore safer to backport. This closes tor issue 28973.
-
- 21 Dec, 2018 1 commit
-
-
David Goulet authored
Linked connections aren't woken up by libevent due to I/O but rather artificially so we can, by chunks, empty the spooled object(s). Commit 5719dfb4 (in 0.3.4.1-alpha) made it that the schedule_active_linked_connections_event would be only called once at startup but this is wrong because then we would never go through again the active linked connections. Fortunately, everytime a new linked connection is created, the event is activated and thus we would go through the active list again. On a busy relay, this issue is mitigated by that but on a slower relays or bridge, a connection could get stuck for a while until a new directory information request would show up. Fixes #28717, #28912
-
- 11 Dec, 2018 5 commits
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
- 10 Dec, 2018 1 commit
-
-
teor authored
Merge Phoul's two lists into teor's list. Replace the 150 fallbacks originally introduced in Tor 0.3.3.1-alpha in January 2018 (of which ~115 were still functional), with a list of 157 fallbacks (92 new, 65 existing, 85 removed) generated in December 2018. Closes ticket 24803.
-
- 07 Dec, 2018 1 commit
-
-
teor authored
Replace the 150 fallbacks originally introduced in Tor 0.3.3.1-alpha in January 2018 (of which ~115 were still functional), with a list of 148 fallbacks (89 new, 59 existing, 91 removed) generated in December 2018. Closes ticket 24803.
-
- 06 Dec, 2018 2 commits
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
- 05 Dec, 2018 1 commit
-
-
Karsten Loesing authored
-
- 01 Dec, 2018 1 commit
-
-
Nick Mathewson authored
-
- 27 Nov, 2018 1 commit
-
-
Alexander Færøy authored
This patch explicitly specifies the path to our OpenSSL dependency and disables the installation of an external OpenSSL version and instead uses the OpenSSL version available from the MinGW environments. See: https://bugs.torproject.org/28574
-
- 26 Nov, 2018 1 commit
-
-
David Goulet authored
Bug reported on tor-dev@ and here is the detail explanation of the issue: https://lists.torproject.org/pipermail/tor-dev/2018-November/013558.html Fixes bug #28619 Signed-off-by:
David Goulet <dgoulet@torproject.org>
-
- 22 Nov, 2018 1 commit
-
-
teor authored
test_entry_guard_outdated_dirserver_exclusion leaks memory, and is missing some unmocks. Fixes 28554; bugfix on 0.3.0.1-alpha.
-
- 20 Nov, 2018 1 commit
-
-
Nick Mathewson authored
-