aboutsummaryrefslogtreecommitdiff
path: root/changes/ticket28669
diff options
context:
space:
mode:
authorDavid Goulet <dgoulet@torproject.org>2018-12-04 14:27:46 -0500
committerDavid Goulet <dgoulet@torproject.org>2018-12-04 14:34:04 -0500
commitcec616a0c8ff060cb722e54342fd30aeab3ad285 (patch)
treee614a2b86fc7bb0ca17f3d224532a46d8b7df7cd /changes/ticket28669
parent43bd4d7509ceab2d82a85483f08132e90b1ab10d (diff)
downloadtor-cec616a0c8ff060cb722e54342fd30aeab3ad285.tar.gz
tor-cec616a0c8ff060cb722e54342fd30aeab3ad285.zip
hs-v3: Don't BUG() if descriptor is found on SOCKS connection retry
When retrying all SOCKS connection because new directory information just arrived, do not BUG() if a connection in state AP_CONN_STATE_RENDDESC_WAIT is found to have a usable descriptor. There is a rare case when this can happen as detailed in #28669 so the right thing to do is put that connection back in circuit wait state so the descriptor can be retried. Fixes #28669 Signed-off-by: David Goulet <dgoulet@torproject.org>
Diffstat (limited to 'changes/ticket28669')
-rw-r--r--changes/ticket286696
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/ticket28669 b/changes/ticket28669
new file mode 100644
index 0000000000..32c6114ffc
--- /dev/null
+++ b/changes/ticket28669
@@ -0,0 +1,6 @@
+ o Minor bugfix (hidden service v3, client):
+ - Avoid a BUG() stacktrace in case a SOCKS connection is found waiting for
+ the descriptor while we do have it in the cache. There is a rare case
+ when this can happen. Now, tor will recover and retry the descriptor.
+ Fixes bug 28669; bugfix on 0.3.2.4-alpha.
+