Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
-+-
 Reporter:  ahf  |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_information
 Priority:  High |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:
 Keywords:  042-proposed, anti-censorship-   |  Actual Points:  2.5
  roadmap-2020Q1, 042-deferred-20190918  |
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by gaba):

 * keywords:  042-proposed, anti-censorship-roadmap-july,
 042-deferred-20190918 => 042-proposed, anti-censorship-roadmap-2020Q1,
 042-deferred-20190918


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
-+-
 Reporter:  ahf  |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_information
 Priority:  High |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:
 Keywords:  042-proposed, anti-censorship-   |  Actual Points:  2.5
  roadmap-july, 042-deferred-20190918|
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by dcf):

 * reviewer:  dcf =>


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
-+-
 Reporter:  ahf  |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_information
 Priority:  High |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:
 Keywords:  042-proposed, anti-censorship-   |  Actual Points:  2.5
  roadmap-july   |
Parent ID:   | Points:  3
 Reviewer:  dcf  |Sponsor:
 |  Sponsor28-must
-+-
Changes (by teor):

 * status:  needs_review => needs_information


Comment:

 This ticket is on the network team review list, but there's nothing we can
 do about it.
 Putting in needs_information until the external reviews have been
 completed.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
-+-
 Reporter:  ahf  |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:
 Keywords:  042-proposed, anti-censorship-   |  Actual Points:  2.5
  roadmap-july   |
Parent ID:   | Points:  3
 Reviewer:  dcf  |Sponsor:
 |  Sponsor28-must
-+-
Changes (by gaba):

 * keywords:  042-proposed, network-team-roadmap-2019-Q1Q2 => 042-proposed,
 anti-censorship-roadmap-july


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
-+-
 Reporter:  ahf  |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:
 Keywords:  042-proposed, network-team-  |  Actual Points:  2.5
  roadmap-2019-Q1Q2  |
Parent ID:   | Points:  3
 Reviewer:  dcf  |Sponsor:
 |  Sponsor28-must
-+-
Changes (by gaba):

 * keywords:  042-proposed => 042-proposed, network-team-roadmap-2019-Q1Q2


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_review
 Priority:  High  |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  042-proposed  |  Actual Points:  2.5
Parent ID:| Points:  3
 Reviewer:  dcf   |Sponsor:  Sponsor19
--+

Comment (by dcf):

 Sorry, I didn't know you wanted me to look at this more. It  looks fine to
 me. For more comments, I suggest asking the developer of ptadapter, and
 Brandon Wiley (blanu) who worked on the PT2.0 spec and said he was
 interested in this topic.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_review
 Priority:  High  |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  042-proposed  |  Actual Points:  2.5
Parent ID:| Points:  3
 Reviewer:  dcf   |Sponsor:  Sponsor19
--+
Changes (by ahf):

 * points:   => 3
 * actualpoints:   => 2.5


Comment:

 Added
 https://github.com/ahf/torspec/commit/af7539f6590726e496c6bb6a49a506233ed10a7f
 and
 https://github.com/ahf/torspec/commit/acdc9cf5cd11e89636d69e515c0f40d23bc48c16

 I try to make 3.3 more general and I think i fixed the itemized list too.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_review
 Priority:  High  |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  042-proposed  |  Actual Points:
Parent ID:| Points:
 Reviewer:  dcf   |Sponsor:  Sponsor19
--+

Comment (by dcf):

 Thanks, I think we can work with this design.

 * "If no feature extensions are supported by the parent process this
 variable SHOULD be left empty."\\
   "The PT proxy SHOULD announce its own set of supported feature
 extensions ..., but only if the `TOR_PT_FEATURES` environment variable is
 present."
   * I don't understand the reason for forbidding the PT proxy from sending
 `FEATURES` when `TOR_PT_FEATURES` is not set/present. I think the PT proxy
 should always be free to send `FEATURES`. 3.3 already says "The parent
 process MUST ignore lines received from PT proxies with unknown keywords,"
 so it's safe.
   * There's an ambiguity with the terms "empty" and "present". They could
 mean "the environment variable is unset" or "the environment variable is
 set to an empty string." IMO it's best if both of those possibilities have
 the same meaning.
 * "less resource conserving"
   * Should be "more resource conserving".
 * "The PT proxy MUST only write the `FEATURES` message once during the
 lifetime of the PT proxy process."
   * IMO it's better to specify what should happens if this is violated;
 e.g., the parent process must ignore any `FEATURES` line after the first.

 I can live without it, but because messages from the parent process to the
 PT proxy on stdin are a major change to the spec, it would be good to have
 something analogous to 3.3 (or make 3.3 more general) that says what those
 messages look like, what should happen if there's an unknown message
 (ignore), etc.

 You should invite the author of
 [https://github.com/twisteroidambassador/ptadapter ptadapter] to comment
 on the changes, because they will have to implement the parent process
 half.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_review
 Priority:  High  |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  042-proposed  |  Actual Points:
Parent ID:| Points:
 Reviewer:  dcf   |Sponsor:  Sponsor19
--+
Changes (by ahf):

 * keywords:   => 042-proposed


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_review
 Priority:  High  |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:  dcf   |Sponsor:  Sponsor19
--+
Changes (by ahf):

 * keywords:  041-proposed =>
 * milestone:  Tor: unspecified => Tor: 0.4.2.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+--
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_review
 Priority:  High  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  041-proposed  |  Actual Points:
Parent ID:| Points:
 Reviewer:  dcf   |Sponsor:  Sponsor19
--+--
Changes (by ahf):

 * reviewer:   => dcf


Comment:

 WIP patch for the feature negotiation in the PT's:
 https://github.com/ahf/tor/commit/f6d74d8c4fb2306114d41d7bd25525285ff3d453

 Adding dcf as reviewer here so the ticket doesn't get handled by the
 needs_review assignment team on Monday.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+--
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_review
 Priority:  High  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  041-proposed  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor19
--+--

Comment (by ahf):

 Thanks a lot for this feedback. I've updated the document now. See
 https://github.com/ahf/torspec/compare/feature/dormant for changes.

 - I have entirely reworded the negotiation process to make use of
 environment variables like the rest of the startup configuration. We now
 use the "TOR_PT_FEATURES" environment variable for the parent process to
 let the PT proxy know of its supported feature extensions. The PT proxy
 can announce its own set of supported feature extensions using the
 "FEATURES" message. I think that addresses all of your concerns in the
 first 6 bullets.
 - I have reworded the dormant messages to be on the form "DORMANT ENTER"
 and "DORMANT EXIT" and the PT proxy response is now made to match the
 request from the parent process.

 I might have missed some details here, please let me know if you spot
 anything and thanks for the review! :-)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+--
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_review
 Priority:  High  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  041-proposed  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor19
--+--

Comment (by dcf):

 Replying to [comment:7 ahf]:
 > I've tried to make a proposal patch here:
 https://github.com/ahf/torspec/commit/49d1cf355c350816ded4ea2e7d5772042aaa9d08

 This looks pretty good.

 * "The PT proxy SHOULD respond to the `FEATURES` message using the
 `FEATURES-ACK` message..."
   * Does the PT proxy necessarily have to wait for `FEATURES` before
 responding with `FEATURES-ACK`? It would be simpler if both sides just
 send a `FEATURES` line declaring their own features.
 * "...a comma-separated list of ''mutually supported'' features..."
   * Maybe the "mutually supported" isn't necessary. It's simpler if both
 sides just declare ''all'' the features they support. Otherwise you also
 have to specify what should happen if a PT proxy violates the spec and
 declares a feature set that is not a subset of the parent process's
 feature set--which is probably that the parent process should ignore the
 features it doesn't support, which amounts to the same.
 * "The PT proxy SHOULD respond to the `FEATURES` message..."
   * I think this needs some language saying what it means if the PT proxy
 does not respond to the `FEATURES` message (backward compatibility); i.e.,
 that the PT proxy's feature set is the empty set. Symmetrically for the PT
 proxy's interpretation: lack of a `FEATURES` option means the parent
 process's feature set is the empty set.
 * "Example message from parent process to PT proxy: `FEATURES
 dormant,x,y`"\\
   "Example response from PT proxy to parent proxy: `FEATURES-ACK
 dormant,y`"
   * I would like the spec to say what should happen when the feature set
 is empty. Specifically, whether a space character is required before the
 null list, `FEATURES` or `FEATURES `.
 * "...the `FEATURES` message that is written to the PT proxy's standard
 input."
   * Why is `FEATURES` on standard input, and not an environment variable
 like every other global configuration? There's no grammar yet in the spec
 for parent→PT standard input messages (presumably it looks like section
 3.3). If `FEATURES` is on standard input, what happens if it is sent more
 than once? What happens if it is sent more than once with different
 feature sets?
 * "Once the Pluggable Transport Specification version have been
 successfully negotiated..."
   * The spec should say when the PT proxy is allowed to send `FEATURES-
 ACK` is allowed and when it is not allowed. It has to be after `VERSION`.
 Can it come after `CMETHODS DONE` or `SMETHODS DONE`? What happens if the
 PT proxy sends it more than once?
 * "The PT proxy MUST acknowledge the request using: `SIGNAL DORMANT-ENTER-
 DONE`"
   * What happens if the parent process sends `SIGNAL DORMANT-ENTER` more
 than once without an intervening `SIGNAL DORMANT-EXIT`? Must the PT proxy
 acknowledge each one, even when it has not changed its own state? I.e.,
 are the acknowledgements edge-triggered or level-triggered?
   * Personally I would remove the MUST language here as it's kind of
 ineffectual--can a PT proxy reply with `SIGNAL DORMANT-ENTER-DONE` 60
 seconds later? Is the parent process going to wait and enforce the MUST?
 If not, it's not really a MUST. I feel the MUST language will encourage PT
 proxies to lie about their current state (I need to send `SIGNAL DORMANT-
 ENTER-DONE` because the spec says so, even if I currently am not capable
 of going dormant). What tor is really interested is not whether the PT
 proxy has received and understood the `SIGNAL DORMANT-ENTER` message, it's
 the points in time when the PT proxy actually changes its dormant state,
 so the spec should reflect that.
   * I would make the messages the same in both directions; e.g. use
 `SIGNAL DORMANT-ENTER` in both directions, without a special `SIGNAL
 DORMANT-ENTER-DONE` in the PT→parent direction.
 * Or even simplify more: `DORMANT ENTER` and `DORMANT EXIT`.

 Side note, one of the features I would like tor to advertise is `reads-
 stdout`, so a PT proxy can know whether it's safe to use `LOG` or not.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+--
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_review
 Priority:  High  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  041-proposed  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor19
--+--
Changes (by dcf):

 * cc: dcf (added)


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+--
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_review
 Priority:  High  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  041-proposed  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor19
--+--
Changes (by ahf):

 * status:  new => needs_review


Comment:

 I've tried to make a proposal patch here:
 https://github.com/ahf/torspec/commit/49d1cf355c350816ded4ea2e7d5772042aaa9d08

 I think it works like you describe in (3) that it's purely asynchronous
 and it always behaves as a hint to the PT that now is the time for the PT
 to enter its dormant state. If the PT is busy with something, it will wait
 a bit, and respond once its able to fulfill the request.

 This spec update also contains your (1) where the Tor process and the PT
 negotiates supported features. If the PT does NOT announce dormant
 support, Tor wont send the "SIGNAL DORMANT-*" events. All events in the
 update must be confirmed by either Tor or the PT as per (2).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+--
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  High  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  041-proposed  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor19
--+--

Comment (by dcf):

 In the [http://meetbot.debian.net/tor-meeting/2019/tor-
 meeting.2019-05-09-17.01.html anti-censorship meeting today], we
 brainstormed two potential designs for communicating dormant mode with
 PTs:

 1. A ''startup'' mode, where the PT declares during the initial exchange
 with tor, "I support dormant mode," and thereafter tor implicitly assumes
 that the PT becomes dormant when requested to do so.
 2. An ''acknowledgement'' mode, where tor sends a command to the PT to
 enter/leave dormant mode, and the PT responds with a message saying "OK, I
 am entering/leaving dormant mode." If the PT doesn't send such an
 acknowledgement, it means the PT doesn't support dormant mode.

 Here's a third potential design to think about:

 3. An ''asynchronous'' mode, where both tor and PT send each other
 messages that are (at the protocol level) purely advisory: "I am entering
 dormant mode" and "I am leaving dormant mode." Of course the PT would take
 tor's "I am entering dormant mode" as a hint to enter dormant mode itself,
 but there would be no protocol-level binding between the messages: each
 side is merely keeping the other informed about its current status.

 It could be a good first use of the [ticket:28181 STATUS] feature. The
 PT→tor messages could look like
 {{{
 STATUS TRANSPORT=whatever DORMANT="on"
 STATUS TRANSPORT=whatever DORMANT="off"
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+--
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  High  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  041-proposed  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor19
--+--
Changes (by ahf):

 * parent:  #28179 =>


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  High  |  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #28179| Points:
 Reviewer:|Sponsor:  Sponsor19
--+
Changes (by gaba):

 * sponsor:  Sponsor8 => Sponsor19


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  High  |  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #28179| Points:
 Reviewer:|Sponsor:  Sponsor8
--+
Changes (by nickm):

 * priority:  Medium => High
 * milestone:  Tor: unspecified => Tor: 0.4.0.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+--
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:  Sponsor8  |
--+--
 Bug #28179 makes us able to handle PT processes better and read output
 from stdout/stderr, but with the recent dormant mode we should figure out
 this interaction works for PT's.

 Especially on Windows this becomes a problem because we will probably stop
 reading from stdout/stderr when Tor enters its dormant mode to disable the
 timer that ticks once a second.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
--+--
 Reporter:  ahf   |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #28179| Points:
 Reviewer:|Sponsor:  Sponsor8
--+--
Changes (by ahf):

 * parent:   => #28179


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs