- 01 Mar, 2019 1 commit
-
-
When "auto" was used for the port number for a listening socket, the message logged after opening the socket would incorrectly say port 0 instead of the actual port used. Fixes bug 29144; bugfix on 0.3.5.1-alpha Signed-off-by:
Kris Katterjohn <katterjohn@gmail.com>
-
- 28 Feb, 2019 6 commits
- 27 Feb, 2019 3 commits
- 26 Feb, 2019 4 commits
-
-
teor authored
-
teor authored
-
teor authored
-
David Goulet authored
-
- 21 Feb, 2019 13 commits
-
-
Nick Mathewson authored
-
Nick Mathewson authored
"ours" to avoid version bump.
-
Nick Mathewson authored
-
Nick Mathewson authored
"ours" to avoid version bump
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
KIST works by computing how much should be allowed to write to the kernel for a given socket, and then it writes that amount to the outbuf. The problem is that it could be possible that the outbuf already has lots of data in it from a previous scheduling round (because the kernel is full/busy and Tor was not able to flush the outbuf yet). KIST ignores that the outbuf has been filling (is above its "highwater") and writes more anyway. The end result is that the outbuf length would exceed INT_MAX, hence causing an assertion error and a corresponding "Bug()" message to get printed to the logs. This commit makes it for KIST to take into account the outbuf length when computing the available space. Bug found and patch by Rob Jansen. Closes #29168. TROVE-2019-001. Signed-off-by:
David Goulet <dgoulet@torproject.org>
-
Nick Mathewson authored
-
Nick Mathewson authored
"ours" to avoid version bump.
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
- 19 Feb, 2019 1 commit
-
-
malloc_options needs to be declared extern (and declaring it extern means we need to initialize it separately) Fixes bug 29145; bugfix on 0.2.9.3-alpha Signed-off-by:
Kris Katterjohn <katterjohn@gmail.com>
-
- 14 Feb, 2019 2 commits
-
-
George Kadianakis authored
-
George Kadianakis authored
-
- 13 Feb, 2019 1 commit
-
-
David Goulet authored
-
- 12 Feb, 2019 5 commits
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
David Goulet authored
Because the test is adding entries to the "rend_cache" directly, the rend_cache_increment_allocation() was never called which made the rend_cache_clean() call trigger that underflow warning: rend_cache/clean: [forking] Nov 29 09:55:04.024 [warn] rend_cache_decrement_allocation(): Bug: Underflow in rend_cache_decrement_allocation (on Tor 0.4.0.0-alpha-dev 2240fe63feb9a8cf) The test is still good and valid. Fixes #28660 Signed-off-by:
David Goulet <dgoulet@torproject.org>
-
Karsten Loesing authored
-
- 08 Feb, 2019 4 commits
-
-
Nick Mathewson authored
It was looking for object files made with the old automake directorations, but those changed when we split up our libraries. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
-
Nick Mathewson authored
-
Nick Mathewson authored
Closes ticket 29026; patch from Mangix.
-
Nick Mathewson authored
Patch from Mangix. Closes part of ticket 29026.
-