[tor-bugs] #22136 [Core Tor/Tor]: Make entry relays expire idle client and bridge connections (was: Make guards expire client connections)

Tor Bug Tracker & Wiki blackhole at torproject.org
Mon Jul 31 23:54:32 UTC 2017


#22136: Make entry relays expire idle client and bridge connections
--------------------------+------------------------------------
 Reporter:  teor          |          Owner:
     Type:  defect        |         Status:  new
 Priority:  Medium        |      Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:  #22805        |         Points:  0.3
 Reviewer:                |        Sponsor:  Sponsor4-can
--------------------------+------------------------------------
Changes (by teor):

 * milestone:  Tor: 0.3.1.x-final => Tor: 0.3.2.x-final
 * sponsor:   => Sponsor4-can


Comment:

 Replying to [comment:2 mikeperry]:
 > Well, the padding code tries to set connection lifetimes on the order of
 an hour by controlling idle circuit lifetime. It tries to ensure that you
 always have some kind of circuit open for around 30-60 minutes, even if
 the client is idle. After that point, it stops holding circuits open or
 building new ones, and then a few minutes after that, the client should
 close the orconn itself.
 >
 > So this bug should only affect padding overhead if there are buggy
 clients (or alternate client implementations) that do not close their own
 idle circuits and orconns.

 So this bug would mainly affect bridges, which delay closing their own
 idle orconns (because they think they are relays connected to another
 relay). This is probably ok.

 But there are a lot of idle bridges, so fixing this bug might help reduce
 network load.

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


More information about the tor-bugs mailing list