[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-dev] Upcoming Tor change with application impact: "Dormant Mode"
- To: tor-dev@xxxxxxxxxxxxxxxxxxxx, Nick Mathewson <nickm@xxxxxxxxxxxxxx>
- Subject: Re: [tor-dev] Upcoming Tor change with application impact: "Dormant Mode"
- From: Michael Rogers <michael@xxxxxxxxxxxxxxxx>
- Date: Fri, 4 Jan 2019 12:43:08 +0000
- Autocrypt: addr=michael@xxxxxxxxxxxxxxxx; prefer-encrypt=mutual; keydata= mQENBE+DF5gBCADGR+FvMLv2vtjznaZbfqRVLNnxfFzXwO8LPu8MdwDMYFEubTx9pCz5Z/jI +BEI+rkhbJbJYRw13rj7zEJWN2+QUb4YtaHCcR1ClA5pcZUurPqbMsFlIruEufydoCcEiTUN FtP/8MrYy70BqDzIgLzpS9tk7CwY2CELm8z0aLIa4th6rjUTIZb+2DbIrVUIwLbub/W014aJ hH942bGO/pbMz8QCdLjtT0YKTiLTDvU0gPA50YxBZHWKqHjJS+35cJUvVxILgSiqqeAkHPks 0IerMGTXBt5QaPamBEo9cGNr0hnRizwvRBPMcG2YDl5CJazUWwCe3FNRUzFfbMq9l3+PABEB AAG0KU1pY2hhZWwgUm9nZXJzIDxtaWNoYWVsQGJyaWFycHJvamVjdC5vcmc+iQE+BBMBAgAo AhsjBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAUCWznfSAUJDZf7MAAKCRARBE/Rn8UnzOPx B/4zVF0oduFMqtXfI+9eVTfilvWW9BQKk4AO78ECWVDfflKYhBKtmW+bZTfJ8OM0iQFS/i2Z E/++0K68dhpRE/FT24jTYosnknFJvov5uAlNiERkXlVhuIGMfJ94XpncEIj5Ji+IHX7PD+RG eVhgQAWhvzYFXUJ8aGXCVWymz/1NOFKRvaSBfjmjMpZnTcbCDVtPFIS+Ha3yS4ql148r0wQc /MOR72vhM8R0obHfKExAeAUc1SlvAeBMvyrb3gRnTrMrNh1ap/gNrrSXChiT+zaIMatQlQS8 o4gNn3AptTxvGW1vhzZPm4nHaVBe1TpFKRkCSKBhClIJVZj+DUqb85zNuQENBE+DF5gBCADV J1q9uGuCePE8wqybJMtjXxAbx+luDeIHrLCPT4E8H2J+v+X/74iRjBoMlZ3JVpaQPVR05nM4 7Vyj0KRhPucv6TH0S9A2cSPiAnWyMIoYOCcYjL8LrPRYdoeLd8b1m7n/KUyi+pOkN/pxJUH5 63gvs4xl+agyhNXkVxxDf2wipZmrr851qSUZJoo/NFfuIW13MU0HyslQaI5fZ4kSV3jgU+QJ eSiScgHRGthDRIFXNzhi8TG8KFi/SXVxGAD5ZYNVV76TzYjXOunCnPsXjj3sV8NqgqhCPpGl DtI5be09FjBKqPzNBVzJFXuPYUv30uLyS7EzKZ089zvn/pN/xDWtABEBAAGJASUEGAECAA8C GwwFAls5304FCQ2X+zYACgkQEQRP0Z/FJ8w68Af/W0XMekchtEvmubiOLXLGnIq7kGuQLp8s aF9696cEWc0vpL6B4zJWeS4Kr4zPMu2Y0XuKsv+XCrKy+rJnUdYgoLiHNEW4629+OibYqV3m XAv3Xkx7YGMi/2rke9dOa6ieyntXgy/3KKgbv12RGVvY5LxFjXy8wV+MIPw5ErAci/1baLNM LcSeMGOpdFtygPTXC/WOTG4gBngAWpBcxR8PeUlo+BDWq9Rpv8bmGSMROqxWIMOFN2IERoy/ szQQTSJvvw6UXnPocKgJSQpljyVEkyU0fK56d+abbZ3QPAsplDEjH8uqnlfdtGGmI7tSQKXJ yXIisGSYk+M4Bq7HrnYO0A==
- Delivered-to: archiver@xxxxxxxx
- Delivery-date: Fri, 04 Jan 2019 07:43:30 -0500
- In-reply-to: <CAKDKvuzD0SAeFkhmmzGQZie9xUfjC7pJzOxM397Gi78_=e4HKw@mail.gmail.com>
- List-archive: <http://lists.torproject.org/pipermail/tor-dev/>
- List-help: <mailto:tor-dev-request@lists.torproject.org?subject=help>
- List-id: discussion regarding Tor development <tor-dev.lists.torproject.org>
- List-post: <mailto:tor-dev@lists.torproject.org>
- List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev>, <mailto:tor-dev-request@lists.torproject.org?subject=subscribe>
- List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-dev>, <mailto:tor-dev-request@lists.torproject.org?subject=unsubscribe>
- Openpgp: preference=signencrypt
- References: <CAKDKvuyqjXN75NLR0Dxn3FpzmwKtY5JdvE5jwy_PfRiJJCqKmQ@mail.gmail.com> <d3ef92f3-ab22-66b4-0514-48f7548b122d@briarproject.org> <CAKDKvuzD0SAeFkhmmzGQZie9xUfjC7pJzOxM397Gi78_=e4HKw@mail.gmail.com>
- Reply-to: tor-dev@xxxxxxxxxxxxxxxxxxxx
- Sender: "tor-dev" <tor-dev-bounces@xxxxxxxxxxxxxxxxxxxx>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3
Hi Nick,
Thanks very much for the reply. Follow-ups inline below.
On 02/01/2019 21:00, Nick Mathewson wrote:
> On Fri, Dec 21, 2018 at 6:34 AM Michael Rogers <michael@xxxxxxxxxxxxxxxx> wrote:
>>
>> Hi Nick,
>>
>> Is the guard connection closed when becoming dormant?
>
> No; it times out independently.
That's good news from my point of view, but in that case I think the
idea of terminating the pluggable transport process when becoming
dormant might need to be reconsidered?
>> 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.
When DormantTimeoutDisabledByIdleStreams is set to 0, what happens to
idle client connections when Tor goes dormant?
>> Will it close client connections on receiving SIGNAL DORMANT?
>
> No.
>
>> 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.
Sorry, do you mean it might be a good idea for Tor to become active
again/send an event in that case? Should I open a ticket for this if it
looks like we'll need it?
Cheers,
Michael
Attachment:
0x11044FD19FC527CC.asc
Description: application/pgp-keys
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev