]> git.ipfire.org Git - thirdparty/tor.git/commitdiff
Downgrade "Rejecting RENDEZVOUS1 cell with unrecognized cookie"
authorNick Mathewson <nickm@torproject.org>
Thu, 14 Oct 2021 16:21:30 +0000 (12:21 -0400)
committerNick Mathewson <nickm@torproject.org>
Thu, 14 Oct 2021 16:21:30 +0000 (12:21 -0400)
This is the loudest of our LOG_PROTOCOL_WARN messages, it can occur
naturally, and there doesn't seem to be a great response to it.

Partial fix for 40400; bugfix on 0.1.1.13-alpha.

changes/bug40400_part2 [new file with mode: 0644]
src/feature/rend/rendmid.c

diff --git a/changes/bug40400_part2 b/changes/bug40400_part2
new file mode 100644 (file)
index 0000000..9b834d5
--- /dev/null
@@ -0,0 +1,5 @@
+  o Minor bugfixes (usability):
+    - Do not log "RENDEZVOUS1 cell with unrecognized rendezvous cookie"
+      at LOG_PROTOCOL_WARN; instead log it at DEBUG. This warning can happen
+      naturally if a client gives up on a rendezvous circuit after sending
+      INTRODUCE1. Fixes part of bug 40400; bugfix on 0.1.1.13-alpha.
index df838aa52708674cca6b89ced37383bd4e85e8d9..8f6a45dfef22008ea587cfe7f4ea904c60594a2e 100644 (file)
@@ -131,7 +131,11 @@ rend_mid_rendezvous(or_circuit_t *circ, const uint8_t *request,
 
   rend_circ = hs_circuitmap_get_rend_circ_relay_side(request);
   if (!rend_circ) {
-    log_fn(LOG_PROTOCOL_WARN, LD_PROTOCOL,
+    /* Once this was a LOG_PROTOCOL_WARN, but it can happen naturally if a
+     * client gives up on a rendezvous circuit after sending INTRODUCE1, but
+     * before the onion service sends the RENDEZVOUS1 cell.
+     */
+    log_fn(LOG_DEBUG, LD_PROTOCOL,
          "Rejecting RENDEZVOUS1 cell with unrecognized rendezvous cookie %s.",
          hexid);
     reason = END_CIRC_REASON_TORPROTOCOL;