[tor-bugs] #21621 [Core Tor/Tor]: Intro points can get stuck in CIRCUIT_PURPOSE_S_ESTABLISH_INTRO

Tor Bug Tracker & Wiki blackhole at torproject.org
Tue May 9 19:23:21 UTC 2017


#21621: Intro points can get stuck in CIRCUIT_PURPOSE_S_ESTABLISH_INTRO
--------------------------+------------------------------------
 Reporter:  teor          |          Owner:  dgoulet
     Type:  defect        |         Status:  needs_information
 Priority:  Medium        |      Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |        Version:  Tor: 0.2.7.2-alpha
 Severity:  Normal        |     Resolution:
 Keywords:  tor-hs        |  Actual Points:
Parent ID:  #21446        |         Points:  1
 Reviewer:                |        Sponsor:  SponsorR-can
--------------------------+------------------------------------
Changes (by dgoulet):

 * status:  accepted => needs_information


Comment:

 So I was studying carefully this ticket for the service implementation of
 prop224 (#20657) in order to implement this feature. However, I *think*
 the service intro circuit do expire normally and don't have a super long
 expiration like a rendezvous circuit has.

 Looking at `circuit_expire_building()` (which actually looks at open
 circuits contrary to its comment), the timeout cutoff is "normal" that is
 not super long:

 `SET_CUTOFF(s_intro_cutoff, get_circuit_build_timeout_ms() * (9/6.0) +
 1000);`

 And then later, there is the `if (victim->state == CIRCUIT_STATE_OPEN) {`
 condition that just breaks if we have a
 `CIRCUIT_PURPOSE_S_ESTABLISH_INTRO` and ultimately close it with timeout
 reason.

 So, I believe tor "naturally" closes too old intro circuit that *are*
 established but then nothing happens on them. By design, they are suppose
 to be short live so this seems already integrated?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21621#comment:14>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list