[tor-dev] Upcoming Tor change with application impact: "Dormant Mode"

Nick Mathewson nickm at torproject.org
Wed Jan 2 21:00:28 UTC 2019

On Fri, Dec 21, 2018 at 6:34 AM Michael Rogers <michael at briarproject.org> wrote:
> Hi Nick,
> Is the guard connection closed when becoming dormant?

No; it times out independently.

> On 13/12/2018 20:56, Nick Mathewson wrote:
> >        DormantTimeoutDisabledByIdleStreams 0|1
> >            If true, then any open client stream (even one not reading or
> >            writing) counts as client activity for the purpose of
> >            DormantClientTimeout. If false, then only network activity counts.
> >            (Default: 1)
> When this option's set to 0 and Tor becomes dormant, will it close any
> idle client connections that are still open?

No.  By default, it won't go dormant if there are any idle client
connections. See DormantTimeoutDisabledByIdleStreams for the option
that overrides that behavior.

> Will it close client connections on receiving SIGNAL DORMANT?


> If Tor doesn't close client connections when becoming dormant, will it
> become active again (or send an event that the controller can use to
> trigger SIGNAL ACTIVE) if there's activity on an open client stream?

No, but that might be a good idea if
DormantTimeoutDisabledByIdleStreams is set to 0.


More information about the tor-dev mailing list