diff options
| author | David Goulet <dgoulet@torproject.org> | 2018-09-19 10:56:15 -0400 |
|---|---|---|
| committer | David Goulet <dgoulet@torproject.org> | 2018-09-20 11:01:23 -0400 |
| commit | fa6d5dd2686d9fedfbbea9bdf0d7dab1a7afc7c4 (patch) | |
| tree | 053c13355b0dbe67531d2aecf4664d4c92762ba5 /changes | |
| parent | d1a6043bfb0a3869439565d563a93aeb0fa30923 (diff) | |
| download | tor-fa6d5dd2686d9fedfbbea9bdf0d7dab1a7afc7c4.tar.gz tor-fa6d5dd2686d9fedfbbea9bdf0d7dab1a7afc7c4.zip | |
hs-v3: Close all SOCKS request on descriptor failure
Client side, when a descriptor is finally fetched and stored in the cache, we
then go over all pending SOCKS request for that descriptor. If it turns out
that the intro points are unusable, we close the first SOCKS request but not
the others for the same .onion.
This commit makes it that we'll close all SOCKS requests so we don't let
hanging the other ones.
It also fixes another bug which is having a SOCKS connection in RENDDESC_WAIT
state but with a descriptor in the cache. At some point, tor will expire the
intro failure cache which will make that descriptor usable again. When
retrying all SOCKS connection (retry_all_socks_conn_waiting_for_desc()), we
won't end up in the code path where we have already the descriptor for a
pending request causing a BUG().
Bottom line is that we should never have pending requests (waiting for a
descriptor) with that descriptor in the cache (even if unusable).
Fixees #27410.
Signed-off-by: David Goulet <dgoulet@torproject.org>
Diffstat (limited to 'changes')
| -rw-r--r-- | changes/ticket27410 | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/changes/ticket27410 b/changes/ticket27410 new file mode 100644 index 0000000000..a21fdde58e --- /dev/null +++ b/changes/ticket27410 @@ -0,0 +1,5 @@ + o Minor bugfixes (hidden service v3): + - Close all SOCKS request (for the same .onion) if the newly fetched + descriptor is unusable. Before that, we would close only the first one + leaving the other hanging and let to time out by themselves. Fixes bug + 27410; bugfix on 0.3.2.1-alpha. |