#25882: clients not detecting stale onion service introduction points
-------------------------------------------------+-------------------------
Reporter: cypherpunks | Owner: dgoulet
Type: defect | Status:
| assigned
Priority: Medium | Milestone: Tor:
| unspecified
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-hs, 034-deferred-20180602 | Actual Points:
035-removed |
Parent ID: #22455 | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by cypherpunks2):
The file
[https://trac.torproject.org/projects/tor/attachment/ticket/25882/debug.onionservice.2.log.xz
debug.onionservice.2.log.xz] contains a pair of new failures, one for the
v2 service and one for the v3 service, observed at about 21:00 local time.
Notice the absence of the receipt of an {{{INTRODUCE2}}} cell in both
cases.
It seems that our bug affects both v2 and v3 services, and the symptom is
that the onion service does not receive an {{{INTRODUCE2}}} cell, i.e. it
does not hear from the introduction point.
So, two thoughts: what is the mechanism by which the set of introduction
points known to a client is kept synchronised with the set of "live"
introduction points maintained by an onion service? Note that a
descriptor held by a client may become outdated, a descriptor held by the
database may become outdated, and circuits maintained by the onion service
may stop working...
Also, what is to stop a malicious introduction point from sending an ACK
to a client but never reaching out to the onion service?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25882#comment:27>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
