Re: [tor-bugs] #24110 [Core Tor/Tor]: document control protocol router status format surprises when using microdescriptors

[Tor Bug Tracker & Wiki]

#24110: document control protocol router status format surprises when using
microdescriptors
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  bwauth-needs, tor-control, tor-  |  Actual Points:
  spec, 033-triage-20180320, |
  033-removed-20180320   |
Parent ID:  #7646| Points:  1
 Reviewer:   |Sponsor:
 |  SponsorV-can
-+-
Changes (by teor):

 * parent:  #24094 => #7646


Comment:

 We'll need to document the current implementation as part of adding a new
 one in #7646.

--
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] #24110 [Core Tor/Tor]: document control protocol router status format surprises when using microdescriptors

[Tor Bug Tracker & Wiki]

#24110: document control protocol router status format surprises when using
microdescriptors
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  bwauth-needs, tor-control, tor-  |  Actual Points:
  spec, 033-triage-20180320, |
  033-removed-20180320   |
Parent ID:  #24094   | Points:  1
 Reviewer:   |Sponsor:
 |  SponsorV-can
-+-

Comment (by teor):

 There are other surprises in control port networkstatuses, regardless of
 whether microdescriptors are used:
 * there is no Unmeasured flag on w lines

 See https://github.com/pastly/simple-bw-scanner/issues/145

--
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] #24110 [Core Tor/Tor]: document control protocol router status format surprises when using microdescriptors

[Tor Bug Tracker & Wiki]

#24110: document control protocol router status format surprises when using
microdescriptors
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  bwauth-needs, tor-control, tor-spec  |  Actual Points:
Parent ID:  #24094   | Points:  1
 Reviewer:   |Sponsor:
 |  SponsorV-can
-+-
Changes (by teor):

 * parent:   => #24094


--
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] #24110 [Core Tor/Tor]: document control protocol router status format surprises when using microdescriptors

[Tor Bug Tracker & Wiki]

#24110: document control protocol router status format surprises when using
microdescriptors
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  bwauth-needs, tor-control, tor-spec  |  Actual Points:
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
 |  SponsorV-can
-+-

Comment (by arma):

 Replying to [comment:12 catalyst]:
 > * TODO: check whether it's possible for a single instance of tor to
 download both ns- and microdescriptor-flavored consensuses.

 Yes, it should be possible. Anybody who is a dir cache does it, because
 they want to fetch both of them so they can serve both.

 But a given Tor will only make client-side path selection choices based on
 one of them -- whichever flavor it is set to use. That's controlled by
 UseMicrodescriptors and the associated consensus param.

 One of the challenges is that it's unclear which use case we're trying to
 cover here, and they at least somewhat contradict: telling the controller
 about new directory objects, or telling the controller about information
 that we're going to be using for our future circuit choices.

--
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] #24110 [Core Tor/Tor]: document control protocol router status format surprises when using microdescriptors (was: NS_CONTROL_PORT formats change when using microdescriptors)

[Tor Bug Tracker & Wiki]

#24110: document control protocol router status format surprises when using
microdescriptors
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  bwauth-needs, tor-control, tor-spec  |  Actual Points:
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
 |  SponsorV-can
-+-

--
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