- Dec 05, 2017
-
-
David Goulet authored
First, hs_service_intro_circ_has_closed() is now called in circuit_mark_for close() because the HS subsystem needs to learn when an intro point is actually not established anymore as soon as possible. There is a time window between a close and a free. Second, when we mark for close, we also remove it from the circuitmap because between the close and the free, a service can launch an new circuit to that same intro point and thus register it which only succeeds if the intro point authentication key is not already in the map. However, we still do a remove from the circuitmap in circuit_free() in order to also cleanup the circuit if it wasn't marked for close prior to the free. Fixes #23603 Signed-off-by:
David Goulet <dgoulet@torproject.org>
-
David Goulet authored
The hs_service_intro_circ_has_closed() was removing intro point objects if too many retries. We shouldn't cleanup those objects in that function at all but rather let cleanup_intro_points() do its job and clean it properly. This was causing an issue in #23603. Furthermore, this moves the logic of remembering failing intro points in the cleanup_intro_points() function which should really be the only function to know when to cleanup and thus when an introduction point should be remembered as a failed one. Fixes #23603 Signed-off-by:
David Goulet <dgoulet@torproject.org>
-
- Dec 04, 2017
-
-
David Goulet authored
In the KIST main loop, if the channel happens to be not opened, set its state to IDLE so we can release it properly later on. Prior to this fix, the channel was in PENDING state, removed from the channel pending list and then kept in that state because it is not opened. This bug was introduced in commit dcabf801 for which we made the scheduler loop not consider unopened channel. This has no consequences on tor except for an annoying but harmless BUG() warning. Fixes #24502 Signed-off-by:
David Goulet <dgoulet@torproject.org>
-
Nick Mathewson authored
-
David Goulet authored
Some platforms don't have good monotonic time support so don't warn when the diff between the last run of the scheduler time and now is negative. The scheduler recovers properly from this so no need to be noisy. Fixes #23696 Signed-off-by:
David Goulet <dgoulet@torproject.org>
-
- Dec 01, 2017
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
Fixes bug 24480; bugfix on 0.2.5.16.
-
Nick Mathewson authored
"ours" merge to avoid version bump.
-
Nick Mathewson authored
"ours" merge to avoid version bump.
-
Nick Mathewson authored
"ours" merge to avoid version bump.
-
Nick Mathewson authored
"ours" merge to avoid version bump.
-
Nick Mathewson authored
"ours" merge to avoid version bump.
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
- Nov 30, 2017
-
-
Nick Mathewson authored
-
Nick Mathewson authored
"ours" to avoid version bumps
-
Nick Mathewson authored
-
Nick Mathewson authored
"ours" to avoid version bump.
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
"ours" merge to avoid version bump.
-
Nick Mathewson authored
-
Nick Mathewson authored
"ours" to avoid version bump
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-