Re: [tor-bugs] #22564 [Applications/Tor Browser]: Hide firefox sync

[Tor Bug Tracker & Wiki]

#22564: Hide firefox sync
-+-
 Reporter:  Dbryrtfbcbhgf|  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-7.0-issues, tbb-regression,  |  Actual Points:
  TorBrowserTeam201709R  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by arthuredelstein):

 * keywords:  tbb-7.0-issues, tbb-regression => tbb-7.0-issues, tbb-
 regression, TorBrowserTeam201709R
 * status:  new => needs_review


Comment:

 Here's a branch with two patches for review. The first patch is a fixup
 that the hides Sync UI elements. The second patch is a regression test.

 https://github.com/arthuredelstein/tor-browser/commits/22564

 And here's a torbutton patch for review, that removes some Sync UI hiding
 code that has been moved into the tor-browser fixup patch.

 https://github.com/arthuredelstein/torbutton/commit/22564

--
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] #23415 [Core Tor/Tor]: sample_laplace_distribution() should take multiple random inputs

[Tor Bug Tracker & Wiki]

#23415: sample_laplace_distribution() should take multiple random inputs
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, security-low, privcount,  |  Actual Points:
  031-backport, 030-backport, 029-backport, 028  |
  -backport-maybe, 026-backport-maybe|
Parent ID:  #23061   | Points:  0.5
 Reviewer:   |Sponsor:
-+-

Comment (by catalyst):

 I meant that the new function would exclude -1.0 and +1.0, so `1 -
 fabs(x)` would still be nonzero.

--
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] #22934 [Core Tor/Tor]: PADDING cells can't be sent immediately after a VERSIONS cell

[Tor Bug Tracker & Wiki]

#22934: PADDING cells can't be sent immediately after a VERSIONS cell
-+
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  merge_ready
 Priority:  Medium   |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor |Version:  Tor: 0.3.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, tor-relay  |  Actual Points:  .1
Parent ID:  #18856   | Points:  0.5
 Reviewer:   |Sponsor:
-+
Changes (by teor):

 * status:  needs_review => merge_ready


Comment:

 That seems correct: VPADDING is allowed before or after VERSIONS. PADDING
 only works reliably once the handshake is complete.

 Here are the VPADDING tests:
 https://github.com/teor2345/endosome/blob/master/client-or-22929.py#L37

--
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] #22848 [Core Tor/Tor]: Increase default Tor buffer sizes on Windows

[Tor Bug Tracker & Wiki]

#22848: Increase default Tor buffer sizes on Windows
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  windows, performance tor-relay   |  Actual Points:
  win32  |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
-+-

Comment (by teor):

 Replying to [comment:4 nickm]:
 > Is there a solution that you recommend here?  Or should we just leave
 this alone for now?

 On Windows 7/Vista (and earlier?) relays, set the equivalent of
 `ConstrainedSockSize 262144`.

--
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] #13605 [Core Tor/Tor]: Create a client/relay-side ReducedExitPolicy

[Tor Bug Tracker & Wiki]

#13605: Create a client/relay-side ReducedExitPolicy
--+
 Reporter:  mikeperry |  Owner:  (none)
 Type:  enhancement   | Status:
  |  needs_revision
 Priority:  Medium|  Milestone:  Tor:
  |  unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-relay, easy, review-group-18  |  Actual Points:
Parent ID:| Points:  medium
 Reviewer:|Sponsor:
--+

Comment (by teor):

 Apart from unit tests, these two things need to be changed:

 The maximum exit policy is now `EXIT_POLICY_ADD_REDUCED`.
 {{{
 #define EXIT_POLICY_REJECT_LOCAL_INTERFACES  (1 << 3)
 #define EXIT_POLICY_ADD_REDUCED  (1 << 4)
 #define EXIT_POLICY_OPTION_MAX
 EXIT_POLICY_REJECT_LOCAL_INTERFACES
 /* All options set: used for unit testing */
 #define EXIT_POLICY_OPTION_ALL ((EXIT_POLICY_OPTION_MAX << 1)
 - 1)
 }}}
 Please check all uses of EXIT_POLICY_OPTION_ALL to make sure they still
 function as designed.

 The last line of the changes file needs a newline, not an escape sequence:
 {{{
 operator to use a reduced exit policy rather than the default one. Closes\
 ticket 13605.
 }}}

--
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] #19661 [Core Tor/Tor]: tor refuses to use /dev/null as a config file

[Tor Bug Tracker & Wiki]

#19661: tor refuses to use /dev/null as a config file
+--
 Reporter:  weasel  |  Owner:  cypherpunks
 Type:  enhancement | Status:  needs_revision
 Priority:  Medium  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor|Version:  Tor: 0.2.8.5-rc
 Severity:  Normal  | Resolution:
 Keywords:  lorax, integration  |  Actual Points:
Parent ID:  | Points:  .1
 Reviewer:  nickm   |Sponsor:
+--
Changes (by teor):

 * keywords:  easy, lorax, integration => lorax, integration


--
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] #23415 [Core Tor/Tor]: sample_laplace_distribution() should take multiple random inputs

[Tor Bug Tracker & Wiki]

#23415: sample_laplace_distribution() should take multiple random inputs
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, security-low, privcount,  |  Actual Points:
  031-backport, 030-backport, 029-backport, 028  |
  -backport-maybe, 026-backport-maybe|
Parent ID:  #23061   | Points:  0.5
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * status:  needs_review => needs_revision


Comment:

 Replying to [comment:3 catalyst]:
 > Wouldn't it be better to have a function that outputs a random double in
 (-1.0, +1.0)?  If you're only using 53 bits of entropy from a RNG call
 that generates 64, there are spare bits to use for generating the sign.

 sample_laplace_distribution() takes the log of a strictly positive
 floating point number, and then applies a random sign.

 We could use sgn() and abs() to decompose `[-1.0, 1.0]` into `{+, -}` and
 `[0.0, 1.0]`, but we'd still have to reject `0.0` before doing the log,
 and then apply the sign. So it seems more complex than the alternative.

--
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] #20534 [Core Tor/Tor]: Revise hard-coded download schedules

[Tor Bug Tracker & Wiki]

#20534: Revise hard-coded download schedules
--+
 Reporter:  teor  |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Low   |  Milestone:  Tor:
  |  0.3.2.x-final
Component:  Core Tor/Tor  |Version:  Tor:
  |  0.2.9.1-alpha
 Severity:  Normal| Resolution:
 Keywords:  regression, triaged-out-20170124  |  Actual Points:
Parent ID:| Points:  0.5
 Reviewer:|Sponsor:
--+

Comment (by teor):

 Replying to [comment:18 nickm]:
 > Merged, leaving open for documentation

 We should document and close this.
 Given that things are working, the other child tickets aren't a high
 priority.

--
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] #20607 [Core Tor/Chutney]: Revise chutney download schedules for exponential backoff

[Tor Bug Tracker & Wiki]

#20607: Revise chutney download schedules for exponential backoff
--+--
 Reporter:  teor  |  Owner:  teor
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #20534| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 0.2.7 is EOL, 0.2.8 will follow in 2018, but chutney still needs to work
 with 0.2.6 until its LTS expires in 2019.

--
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] #20606 [Core Tor/Tor]: Make the test network exponential backoff multiplier configurable

[Tor Bug Tracker & Wiki]

#20606: Make the test network exponential backoff multiplier configurable
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.1-alpha
 Severity:  Normal   | Resolution:  wontfix
 Keywords:  test-network, configuration, torrc,  |  Actual Points:
  chutney, backoff, download-schedule|
Parent ID:  #20534   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 I don't think we want to make this configurable: it's unlikely to be
 useful, and it's one more torrc option. We should do #20605 instead.

--
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] #20605 [Core Tor/Tor]: Reduce the exponential backoff variance

[Tor Bug Tracker & Wiki]

#20605: Reduce the exponential backoff variance
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  backoff, tor-client download-|  Actual Points:
  schedule   |
Parent ID:  #20534   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by teor):

 This would be nice, particularly for chutney.
 But it's not a high priority, as nothing is broken right now.

--
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] #22511 [Community]: Tor Code of Conduct

[Tor Bug Tracker & Wiki]

#22511: Tor Code of Conduct
---+
 Reporter:  alison |  Owner:  (none)
 Type:  task   | Status:  new
 Priority:  Medium |  Milestone:
Component:  Community  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #22079 | Points:
 Reviewer: |Sponsor:
---+

Comment (by isis):

 Replying to [comment:8 cypherpunks]:
 > http://quillette.com/2017/07/18/neurodiversity-case-free-speech/

 Yeah, now ''that's'' the way to do it, buddy. Link to a white
 supremacist's blog post. ''Brilliant''. That'll show those politically-
 correct Tor developers.

--
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] #23424 [Applications/Tor Browser]: Stop exposing the moz-icon URL scheme to the web

[Tor Bug Tracker & Wiki]

#23424: Stop exposing the moz-icon URL scheme to the web
--+--
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 We should do this if Mozilla doesn't get to it.
 https://bugzilla.mozilla.org/show_bug.cgi?id=1222924

--
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] #22511 [Community]: Tor Code of Conduct

[Tor Bug Tracker & Wiki]

#22511: Tor Code of Conduct
---+
 Reporter:  alison |  Owner:  (none)
 Type:  task   | Status:  new
 Priority:  Medium |  Milestone:
Component:  Community  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #22079 | Points:
 Reviewer: |Sponsor:
---+

Comment (by nickm):

 Your three-month latency makes me more and more confident that arma was
 correct above.

--
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] #22511 [Community]: Tor Code of Conduct

[Tor Bug Tracker & Wiki]

#22511: Tor Code of Conduct
---+
 Reporter:  alison |  Owner:  (none)
 Type:  task   | Status:  new
 Priority:  Medium |  Milestone:
Component:  Community  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #22079 | Points:
 Reviewer: |Sponsor:
---+

Comment (by cypherpunks):

 htp://quillette.com/2017/07/18/neurodiversity-case-free-speech/

--
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] #22511 [Community]: Tor Code of Conduct

[Tor Bug Tracker & Wiki]

#22511: Tor Code of Conduct
---+
 Reporter:  alison |  Owner:  (none)
 Type:  task   | Status:  new
 Priority:  Medium |  Milestone:
Component:  Community  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #22079 | Points:
 Reviewer: |Sponsor:
---+

Comment (by cypherpunks):

 Replying to [comment:5 isis]:
 Just buzzwords, false assumptions, false statements and sophistry.

--
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] #23361 [Core Tor/Tor]: prop224: client can pick super old rendezvous points

[Tor Bug Tracker & Wiki]

#23361: prop224: client can pick super old rendezvous points
-+
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  merge_ready
 Priority:  High |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:  SponsorR-can
-+

Comment (by asn):

 OK I tested this branch again to make sure that nothing broke in the
 meanwhile.
 Branch seems to work well.

 To test, I used a client with this branch, connected to an hsv3 service
 and made sure that the rendezvous point used supported the hsv3 protocol
 and data made it to the service. I did this test about 20 times to make
 sure that we only pick legit RPs.

--
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] #23361 [Core Tor/Tor]: prop224: client can pick super old rendezvous points

[Tor Bug Tracker & Wiki]

#23361: prop224: client can pick super old rendezvous points
-+
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  merge_ready
 Priority:  High |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:  SponsorR-can
-+
Changes (by asn):

 * status:  needs_revision => merge_ready


Comment:

 Ouch. Seems like I left a bad comment in there.

 Pushed a fixup that addresses it.

 Let me know if you want me to rebase the whole branch on master.

--
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] #22281 [Core Tor/Tor]: Prevent pattern of bugs caused by calling get_options() within options_validate() etc

[Tor Bug Tracker & Wiki]

#22281: Prevent pattern of bugs caused by calling get_options() within
options_validate() etc
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  .1
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  new => accepted
 * owner:  (none) => nickm
 * actualpoints:   => .1


Comment:

 I think that approach could be reasonable.  I wrote it up as a branch
 `ticket22281`.  Needs 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] #22281 [Core Tor/Tor]: Prevent pattern of bugs caused by calling get_options() within options_validate() etc

[Tor Bug Tracker & Wiki]

#22281: Prevent pattern of bugs caused by calling get_options() within
options_validate() etc
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  .1
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  accepted => needs_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] #22805 [Core Tor/Tor]: Remove or_circuit_t.is_first_hop, because it's not accurate any more

[Tor Bug Tracker & Wiki]

#22805: Remove or_circuit_t.is_first_hop, because it's not accurate any more
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  technical-debt, security-review  |  Actual Points:  .3
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 note to self: does this break test-network-all?  Try it before merging.

--
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] #22136 [Core Tor/Tor]: Make entry relays expire idle client and bridge connections

[Tor Bug Tracker & Wiki]

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

 * status:  new => closed
 * resolution:   => duplicate


--
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] #21585 [Core Tor/Tor]: Check code that uses consensus membership to find clients

[Tor Bug Tracker & Wiki]

#21585: Check code that uses consensus membership to find clients
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  triaged-out-20170308, tor-relay is-  |  implemented
  client refactor client-detection technical-|  Actual Points:
  debt   |
Parent ID:  #22805   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  new => closed
 * resolution:   => implemented


--
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] #22805 [Core Tor/Tor]: Remove or_circuit_t.is_first_hop, because it's not accurate any more

[Tor Bug Tracker & Wiki]

#22805: Remove or_circuit_t.is_first_hop, because it's not accurate any more
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  technical-debt, security-review  |  Actual Points:  .3
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  accepted => needs_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] #22805 [Core Tor/Tor]: Remove or_circuit_t.is_first_hop, because it's not accurate any more

[Tor Bug Tracker & Wiki]

#22805: Remove or_circuit_t.is_first_hop, because it's not accurate any more
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  technical-debt, security-review  |  Actual Points:  .3
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  new => accepted
 * owner:  (none) => nickm
 * actualpoints:   => .3


Comment:

 My branch `bug22805` now fixes the issues here that I could identify.

--
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] #21585 [Core Tor/Tor]: Check code that uses consensus membership to find clients

[Tor Bug Tracker & Wiki]

#21585: Check code that uses consensus membership to find clients
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  triaged-out-20170308, tor-relay is-  |  Actual Points:
  client refactor client-detection technical-|
  debt   |
Parent ID:  #22805   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 The parent ticket now includes a fixes for the router_get_by_id_digest()
 issues too.  I've opened #23423 to track the
 connection_or_digest_is_known_relay() issue

--
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] #23423 [Core Tor/Tor]: Remove redundant calls to connection_or_digest_is_known_relay()

[Tor Bug Tracker & Wiki]

#23423: Remove redundant calls to connection_or_digest_is_known_relay()
-+-
 Reporter:  nickm|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Low  |  Milestone:  Tor: unspecified
Component:  Core |Version:
  Tor/Tor|
 Severity:  Minor|   Keywords:  refactor, redundant, technical-debt
Actual Points:   |  Parent ID:
   Points:  2|   Reviewer:
  Sponsor:   |
-+-
 Many calls to this function occur along with, and are redundant with,
 channel_is_client().

--
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] #23423 [Core Tor/Tor]: Remove redundant calls to connection_or_digest_is_known_relay()

[Tor Bug Tracker & Wiki]

#23423: Remove redundant calls to connection_or_digest_is_known_relay()
-+-
 Reporter:  nickm|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Low  |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Minor| Resolution:
 Keywords:  refactor, redundant, technical-debt  |  Actual Points:
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 See #21585 for some background

--
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] #23422 [- Select a component]: my proxy with tor

[Tor Bug Tracker & Wiki]

#23422: my proxy with tor
--+---
 Reporter:  massado   |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:  not a bug
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by nickm):

 * status:  new => closed
 * resolution:   => not a bug


Comment:

 Hi!  This is a bugtracker, for reporting bugs in Tor.  It isn't a tech
 support site.

--
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] #23422 [- Select a component]: my proxy with tor

[Tor Bug Tracker & Wiki]

#23422: my proxy with tor
--+
 Reporter:  massado   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by massado):

 dear,
 i want to use the program dork searcher but the ask me put my proxy and
 port, i want to know how can i check my proxy and port with tor?

 Thank you.

 Best regards.

 Massado

--
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] #23422 [- Select a component]: my proxy with tor

[Tor Bug Tracker & Wiki]

#23422: my proxy with tor
--+
 Reporter:  massado   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 dear,
 i want to use the program dork searcher but the ask me put my proxy and
 port, i want to know how can i check my proxy and port with tor?

 Thank you.

 Best regards.

 Massado

--
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] #21585 [Core Tor/Tor]: Check code that uses consensus membership to find clients

[Tor Bug Tracker & Wiki]

#21585: Check code that uses consensus membership to find clients
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  triaged-out-20170308, tor-relay is-  |  Actual Points:
  client refactor client-detection technical-|
  debt   |
Parent ID:  #22805   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 There is also a problem with connection_or_digest_is_known_relay() -- it
 is used redundantly with channel_is_client() in a few places.

--
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] #23383 [Metrics/Metrics website]: Apply Tor style guide to redesigned Tor Metrics website

[Tor Bug Tracker & Wiki]

#23383: Apply Tor style guide to redesigned Tor Metrics website
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 antonela, thanks for making that mockup!

 My initial reaction is that I feel that the white-on-purple makes the
 website look a little less official than the colored Tor onion does. Do
 you have any ideas how to change that towards using the colored Tor logo?

 However, even if not, I could imagine that we use this version for now to
 conform more with the style guide and at the same time avoid to redesign
 more parts than necessary. And when the other Tor (sub)sites are
 redesigned, or when we do the next Tor Metrics website redesign, we switch
 to the colored onion. However, I'd also like to hear what linda and iwakeh
 think before moving forward in this direction.

--
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] #22136 [Core Tor/Tor]: Make entry relays expire idle client and bridge connections

[Tor Bug Tracker & Wiki]

#22136: Make entry relays expire idle client and bridge connections
--+
 Reporter:  teor  |  Owner:  (none)
 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
--+

Comment (by nickm):

 The patch on the parent ticket makes us look at channel_is_client.

--
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] #21585 [Core Tor/Tor]: Check code that uses consensus membership to find clients

[Tor Bug Tracker & Wiki]

#21585: Check code that uses consensus membership to find clients
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  triaged-out-20170308, tor-relay is-  |  Actual Points:
  client refactor client-detection technical-|
  debt   |
Parent ID:  #22805   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 The patch in the parent ticket kills off the is_first_hop flag.

 I have looked over all the uses of node_get_by_id() to make sure we aren't
 using it for client-testing without an appropriate wrapper
 [connection_or_digest_is_known_relay].  I also looked at the routerstatus-
 lookup functions.

 There is a problem with the router_get_by_id_digest() function -- it is
 used too much, when some other test would be more correct.

--
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] #15161 [Applications/Tor Messenger]: CTCP fingerprinting

[Tor Bug Tracker & Wiki]

#15161: CTCP fingerprinting
+--
 Reporter:  cypherpunks |  Owner:  sukhbir
 Type:  defect  | Status:  reopened
 Priority:  Immediate   |  Milestone:
Component:  Applications/Tor Messenger  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by sukhbir):

 We are keeping CTCP responses. The change in the above pull request is
 that CTCP TIME returns the time in UTC instead of the local time with the
 seconds timer stripped to prevent detailed time resolution.

--
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] #15161 [Applications/Tor Messenger]: CTCP fingerprinting

[Tor Bug Tracker & Wiki]

#15161: CTCP fingerprinting
+--
 Reporter:  cypherpunks |  Owner:  sukhbir
 Type:  defect  | Status:  reopened
 Priority:  Immediate   |  Milestone:
Component:  Applications/Tor Messenger  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by sukhbir):

 Pull request for review: https://github.com/TheTorProject/tor-messenger-
 build/pull/14

--
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] #23383 [Metrics/Metrics website]: Apply Tor style guide to redesigned Tor Metrics website

[Tor Bug Tracker & Wiki]

#23383: Apply Tor style guide to redesigned Tor Metrics website
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by antonela):

 Karsten, I made a mockup to show how the logo should work.
 https://share.riseup.net/#2GdUbDtOzAsriUiOZiXcSQ

 Also, the assets are here, both white and color versions (.png, .svg,)
 https://share.riseup.net/#JkYCWtrCmBy3OJ4rru_qyw

 let me know if you need anything else :)

--
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] #22848 [Core Tor/Tor]: Increase default Tor buffer sizes on Windows

[Tor Bug Tracker & Wiki]

#22848: Increase default Tor buffer sizes on Windows
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  windows, performance tor-relay   |  Actual Points:
  win32  |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 Is there a solution that you recommend here?  Or should we just leave this
 alone for now?

--
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] #22824 [Core Tor/Tor]: Establish guidelines for using assertions

[Tor Bug Tracker & Wiki]

#22824: Establish guidelines for using assertions
+--
 Reporter:  catalyst|  Owner:  nickm
 Type:  task| Status:  accepted
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.2.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-doc, technical-debt, style  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by nickm):

 * owner:  catalyst => nickm
 * status:  new => accepted


--
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] #22860 [Obfuscation/Pluggable transport]: Ubuntu 16.04 apparmor policy blocks obfs4proxy without modification

[Tor Bug Tracker & Wiki]

#22860: Ubuntu 16.04 apparmor policy blocks obfs4proxy without modification
-+-
 Reporter:  ccppuu   |  Owner:  asn
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Obfuscation/Pluggable transport  |Version:
 Severity:  Major| Resolution:
 Keywords:  apparmor, obfs4proxy, tor-pt |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * owner:  (none) => asn
 * component:  Core Tor/Tor => Obfuscation/Pluggable transport
 * milestone:  Tor: 0.3.2.x-final =>


Comment:

 This looks like a PT bug to me, not a Tor bug?

--
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] #22880 [Core Tor/Tor]: NETINFO cells are used for clock skew checks

[Tor Bug Tracker & Wiki]

#22880: NETINFO cells are used for clock skew checks
--+
 Reporter:  teor  |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-spec, technical-debt  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * owner:  (none) => nickm
 * status:  new => accepted


--
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] #23146 [Core Tor/Tor]: prop280: Finish privcount-in-Tor proposal (280)

[Tor Bug Tracker & Wiki]

#23146: prop280: Finish privcount-in-Tor proposal (280)
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:  3
 Reviewer:|Sponsor:  SponsorQ
--+
Changes (by nickm):

 * milestone:  Tor: 0.3.2.x-final => Tor: 0.3.3.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] #22955 [Core Tor/Tor]: Specify how PrivCount will work with Tor

[Tor Bug Tracker & Wiki]

#22955: Specify how PrivCount will work with Tor
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  privcount |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  SponsorQ-can
--+
Changes (by nickm):

 * milestone:  Tor: 0.3.2.x-final => Tor: 0.3.3.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] #22996 [Core Tor/Tor]: The router protocol versions section in dir-spec is out of date

[Tor Bug Tracker & Wiki]

#22996: The router protocol versions section in dir-spec is out of date
---+---
 Reporter:  teor   |  Owner:  nickm
 Type:  defect | Status:  accepted
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-spec, technical-debt, doc  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by nickm):

 * owner:  (none) => nickm
 * status:  new => accepted


--
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] #23090 [Core Tor/Tor]: Sandbox failure on Debian 8.9 under OpenVZ with kernel version 2.6.32

[Tor Bug Tracker & Wiki]

#23090: Sandbox failure on Debian 8.9 under OpenVZ with kernel version 2.6.32
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.9
 Severity:  Normal   | Resolution:  fixed
 Keywords:  sandbox, log, error-message, |  Actual Points:
  usability  |
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 ab18e5e5fcff7fbdbf0905e6dd2585b7e4a10108 improves the warning.

--
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] #23123 [Core Tor/Tor]: Cannibalized HS circuit don't have their timestamp_dirty updated

[Tor Bug Tracker & Wiki]

#23123: Cannibalized HS circuit don't have their timestamp_dirty updated
--+
 Reporter:  dgoulet   |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor:
  |  0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  tor-hs, tor-circuit, prop224  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  merge_ready => closed
 * resolution:   => fixed


Comment:

 Merged!

--
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] #23361 [Core Tor/Tor]: prop224: client can pick super old rendezvous points

[Tor Bug Tracker & Wiki]

#23361: prop224: client can pick super old rendezvous points
-+
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  needs_revision
 Priority:  High |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:  SponsorR-can
-+
Changes (by nickm):

 * status:  reopened => needs_revision


--
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] #23361 [Core Tor/Tor]: prop224: client can pick super old rendezvous points

[Tor Bug Tracker & Wiki]

#23361: prop224: client can pick super old rendezvous points
-+
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  prop224, tor-hs  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:  SponsorR-can
-+
Changes (by nickm):

 * status:  merge_ready => closed
 * resolution:   => fixed


Comment:

 Okay; I merged the spec branch, but I get a pile of warnings when I try to
 merge it.  It looks like there was a runaway comment.

 I'm fine with just fixing the comment and merging, but if it's been
 unbuildable, that means that nobody has has tried testing the code, right?

--
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] #23361 [Core Tor/Tor]: prop224: client can pick super old rendezvous points

[Tor Bug Tracker & Wiki]

#23361: prop224: client can pick super old rendezvous points
-+
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  reopened
 Priority:  High |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:  SponsorR-can
-+
Changes (by nickm):

 * status:  closed => reopened
 * resolution:  fixed =>


--
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] #22212 [Core Tor/Tor]: [warn] channelpadding_compute_time_until_pad_for_netflow(): Bug: Channel padding timeout scheduled 164729ms in the past. Did the monotonic clock just jump?

[Tor Bug Tracker & Wiki]

#22212: [warn] channelpadding_compute_time_until_pad_for_netflow(): Bug: Channel
padding timeout scheduled 164729ms in the past. Did the monotonic clock
just jump?
--+
 Reporter:  arma  |  Owner:  mikeperry
 Type:  defect| Status:  reopened
 Priority:  Medium|  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.1.1-alpha
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by nickm):

 (Mike, any insight here?)

--
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] [Tor Bug Tracker & Wiki] Batch modify: #22276, #22278, #22861

[Tor Bug Tracker & Wiki]

Batch modification to #22276, #22278, #22861 by nickm:
milestone to Tor: 0.3.2.x-final

--
Tickets 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] #21074 [Core Tor/Tor]: setrlimit fails OSX Sierra

[Tor Bug Tracker & Wiki]

#21074: setrlimit fails OSX Sierra
-+-
 Reporter:  cypherpunks  |  Owner:  nickm
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.6.7
 Severity:  Normal   | Resolution:
 Keywords:  OSX Sierra setrlimit, tbb-wants, |  Actual Points:
  031-backport   |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  OSX Sierra setrlimit, tbb-wants => OSX Sierra setrlimit, tbb-
 wants, 031-backport
 * milestone:  Tor: 0.3.1.x-final => Tor: 0.3.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] #23077 [Core Tor/Tor]: Channelpadding tests rely on actual time; can fail

[Tor Bug Tracker & Wiki]

#23077: Channelpadding tests rely on actual time; can fail
--+
 Reporter:  nickm |  Owner:  mikeperry
 Type:  defect| Status:  assigned
 Priority:  High  |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  unittest, channelpadding  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * owner:  (none) => mikeperry
 * status:  new => assigned


--
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] #22400 [Core Tor/Tor]: We bootstrap from different primary guards when we start with a non-live consensus and not enough guards in the state file

[Tor Bug Tracker & Wiki]

#22400: We bootstrap from different primary guards when we start with a non-live
consensus and not enough guards in the state file
---+---
 Reporter:  arma   |  Owner:  nickm
 Type:  defect | Status:
   |  needs_information
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.3.x-final
Component:  Core Tor/Tor   |Version:  Tor:
   |  0.3.0.7
 Severity:  Normal | Resolution:
 Keywords:  tor-client tor-guard 030-backport  |  Actual Points:
Parent ID: | Points:  3
 Reviewer:  asn|Sponsor:
---+---
Changes (by nickm):

 * status:  accepted => needs_information
 * cc: arma (added)
 * milestone:  Tor: 0.3.1.x-final => Tor: 0.3.3.x-final


Comment:

 Roger, did you want to say more here?  If not we should just close this.

--
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] #22934 [Core Tor/Tor]: PADDING cells can't be sent immediately after a VERSIONS cell

[Tor Bug Tracker & Wiki]

#22934: PADDING cells can't be sent immediately after a VERSIONS cell
-+
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor |Version:  Tor: 0.3.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, tor-relay  |  Actual Points:  .1
Parent ID:  #18856   | Points:  0.5
 Reviewer:   |Sponsor:
-+
Changes (by nickm):

 * status:  accepted => needs_review
 * actualpoints:   => .1


Comment:

 If I understand this ticket correctly, you're saying we _do_ allow
 VPADDING here?  If so, let's just say "use VPADDING for this" in the spec.
 I've put a patch to do this in my torspec repository as `bug22934`.  What
 do you think?

--
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] #21759 [Metrics/CollecTor]: Add persistence for torperf/onionperf

[Tor Bug Tracker & Wiki]

#21759: Add persistence for torperf/onionperf
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  merge_ready
 Priority:  Medium |  Milestone:  CollecTor 1.4.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by iwakeh):

 Replying to [comment:14 iwakeh]:
 > Regarding the first part of comment:12:
 > The discussion should be taken to a ticket summarizing the changes for
 all modules.
 > I'll look for an appropriate ticket or create a new one.

 The new ticket is #23421.

--
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] #23421 [Metrics/CollecTor]: use persistence functionality throughout all CollecTor modules

[Tor Bug Tracker & Wiki]

#23421: use persistence functionality throughout all CollecTor modules
---+---
 Reporter:  iwakeh |  Owner:  metrics-team
 Type:  enhancement| Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by iwakeh):

 * status:  new => needs_information


Comment:

 Here's an overview (cf. #21757 comment:12 following):

* bridge-desc (all types): after sanitation the descriptor is written;
 if one descriptor cannot be sanitized, it is skipped
* relay-desc (all types): descriptors written one by one skipping
 problematic ones
* exitlists: always stored as a single file.
* onionperf: currently implemented using an implicit transaction, i.e.,
 all descriptors in one downloaded descriptor file are only stored, if all
 were valid. This is different from the sync-approach where
 invalid/unparseable descriptors are ignored, but valid ones stored no
 matter if they came in one file.

--
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] #22934 [Core Tor/Tor]: PADDING cells can't be sent immediately after a VERSIONS cell

[Tor Bug Tracker & Wiki]

#22934: PADDING cells can't be sent immediately after a VERSIONS cell
-+
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  accepted
 Priority:  Medium   |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor |Version:  Tor: 0.3.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, tor-relay  |  Actual Points:
Parent ID:  #18856   | Points:  0.5
 Reviewer:   |Sponsor:
-+

Comment (by nickm):

 >I think we should fix this by changing the channel state immediately
 after the VERSIONS cell is read, rather than after all the cells in the
 buffer are processed.

 FWIW, this makes me a touch nervous -- did you mean, changing the
 negotiated version?  I worry that if we change the "state" field itself,
 we'll accidentally make other parts of the code think that the channel has
 finished authenticating.

--
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] #22934 [Core Tor/Tor]: PADDING cells can't be sent immediately after a VERSIONS cell

[Tor Bug Tracker & Wiki]

#22934: PADDING cells can't be sent immediately after a VERSIONS cell
-+
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  accepted
 Priority:  Medium   |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor |Version:  Tor: 0.3.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, tor-relay  |  Actual Points:
Parent ID:  #18856   | Points:  0.5
 Reviewer:   |Sponsor:
-+
Changes (by nickm):

 * owner:  (none) => nickm
 * status:  new => accepted


Comment:

 So, two issues here: "can this happen on clients that are doing padding"
 and "what behavior should we allow"?

 I am fairly confident that the answer to the first question is "no".  The
 function `channelpadding_send_padding_cell_for_callback()` is where the
 code sends its cells, and it is always checks whether the channel state is
 CHAN_STATE_OPEN.  We only set the channel to that state when the OR
 connection enters OR_CONN_STATE_OPEN.  The same check is performed in
 channelpadding_decide_to_pad_channel().

 So we won't trigger this today from the channel padding code.  Hooray!

 So, what _should_ we be doing?  It's sure desirable to allow PADDING and
 VPADDING after the VERSIONS cell, but we can't actually do that until some
 Tors allow it, and we need some means to signal that they will.

 I suggest that for 0.3.2, we just fix the spec to note that this doesn't
 work, and for 0.3.3 we write a proposal and implement it.

--
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] #23421 [Metrics/CollecTor]: use persistence functionality throughout all CollecTor modules

[Tor Bug Tracker & Wiki]

#23421: use persistence functionality throughout all CollecTor modules
---+--
 Reporter:  iwakeh |  Owner:  metrics-team
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+--
 As discussed in
 [https://trac.torproject.org/projects/tor/ticket/21272#comment:18 #21272
 comment:18] and before.

 All storing of files should be done by the persist-mechanism, i.e.,
 a o.t.c.persist.*Persistence classes should also be used for storing
 descriptors initially (i.e., when fetched from authorities).

--
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] #20615 [Core Tor/Tor]: Your Guard is failing an extremely large amounts of circuits.

[Tor Bug Tracker & Wiki]

#20615: Your Guard is failing an extremely large amounts of circuits.
--+
 Reporter:  bug_bunny |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.2.8.9
 Severity:  Normal| Resolution:
 Keywords:  performance   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * milestone:  Tor: 0.3.1.x-final => Tor: 0.3.3.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] #23077 [Core Tor/Tor]: Channelpadding tests rely on actual time; can fail

[Tor Bug Tracker & Wiki]

#23077: Channelpadding tests rely on actual time; can fail
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  unittest, channelpadding  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * priority:  Medium => High


--
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] #22789 [Core Tor/Tor]: Tor 0.3.1.4-alpha crash on OpenBSD-current

[Tor Bug Tracker & Wiki]

#22789: Tor 0.3.1.4-alpha crash on OpenBSD-current
-+-
 Reporter:  fredzupy |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.4-alpha
 Severity:  Major| Resolution:  fixed
 Keywords:  tor, crash, inet_pton, c99,  |  Actual Points:  3
  openbsd, 024-backport, 025-backport,   |
  026-backport, 027-backport, 028-backport,  |
  029-backport, 030-backport, review-group-20|
  trove-2017-007 |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  SponsorV
-+-
Changes (by nickm):

 * status:  reopened => closed
 * resolution:   => fixed


Comment:

 Retroactively changed the changelog in master, though usually we don't do
 this. b268dca41175fe438441d3e4137766efee30da35

--
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] #23361 [Core Tor/Tor]: prop224: client can pick super old rendezvous points

[Tor Bug Tracker & Wiki]

#23361: prop224: client can pick super old rendezvous points
-+
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  merge_ready
 Priority:  High |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:  SponsorR-can
-+
Changes (by asn):

 * status:  needs_review => merge_ready


--
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] #23361 [Core Tor/Tor]: prop224: client can pick super old rendezvous points

[Tor Bug Tracker & Wiki]

#23361: prop224: client can pick super old rendezvous points
-+
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  needs_review
 Priority:  High |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:  SponsorR-can
-+
Changes (by asn):

 * status:  needs_revision => needs_review


Comment:

 Spec patch can be found in `bug23361` in my repo. Putting this back in
 `needs_review`.

 I also made #23420 for the padding feature that David mentioned in
 comment:11.

--
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] #23420 [Core Tor/Tor]: prop224: Pad legacy rendezvous cells to match v3 cells

[Tor Bug Tracker & Wiki]

#23420: prop224: Pad legacy rendezvous cells to match  v3 cells
--+
 Reporter:  asn   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  prop224, prop224-extra, tor-hs
Actual Points:|  Parent ID:
   Points:  1 |   Reviewer:
  Sponsor:|
--+
 We should do what proposal 224 section 4.3 says and pad legacy rend cells
 to 168 bytes so that they all look the same .

--
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] #21915 [Core Tor/DirAuth]: Add a new directory authority: Nicholas Merrill

[Tor Bug Tracker & Wiki]

#21915: Add a new directory authority: Nicholas Merrill
--+--
 Reporter:  dgoulet   |  Owner:  (none)
 Type:  task  | Status:  new
 Priority:  High  |  Milestone:  Tor: unspecified
Component:  Core Tor/DirAuth  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dcf):

 * cc: dcf (added)


Comment:

 I'm Ccing myself so I can see that the new dirauth gets added to OONI's
 test list, once its addresses are available.

--
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] #23243 [Metrics/Metrics website]: write a spec for web-server-access log descriptors

[Tor Bug Tracker & Wiki]

#23243: write a spec for web-server-access log descriptors
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 Another addition:

 Even though Tor's Apache webservers are configured to only provide three
 ip addresses (e.g. `0.0.0.{0,1,2}`) all lines with different ips are
 accepted and sanitized to ip `0.0.0.0`.

 Or, should such lines be discarded?

--
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] #2681 [Core Tor/Tor]: brainstorm ways to let Tor clients use yesterday's consensus more safely

[Tor Bug Tracker & Wiki]

#2681: brainstorm ways to let Tor clients use yesterday's consensus more safely
-+-
 Reporter:  arma |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop212, tor-client, small-feature,  |  Actual Points:
  tor-dos-dirauth, low-bandwidth, sponsor4,  |
  sponsor8-maybe |
Parent ID:  #2664| Points:  5
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by nickm):

 * milestone:  Tor: 0.3.2.x-final => Tor: 0.3.3.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] #8305 [Metrics/Metrics website]: Use clearer colors in the "Consumed bandwidth by Exit/Guard flag combination" graph

[Tor Bug Tracker & Wiki]

#8305: Use clearer colors in the "Consumed bandwidth by Exit/Guard flag
combination" graph
-+---
 Reporter:  arma |  Owner:  (none)
 Type:  enhancement  | Status:  needs_information
 Priority:  Low  |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by iwakeh):

 * cc: linda (added)


Comment:

 Related to applying Tor Style guide (cf. #23383).
 CC-ing Linda:  Maybe, there are already well functioning color scales
 defined in the style guide, which could be useful here?

--
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] #22266 [Core Tor/Tor]: fix the jump-to-80% issue

[Tor Bug Tracker & Wiki]

#22266: fix the jump-to-80% issue
+
 Reporter:  catalyst|  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  High|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  usability, ux, ux-team  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+
Changes (by nickm):

 * milestone:  Tor: 0.3.2.x-final => Tor: 0.3.3.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] #21915 [Core Tor/DirAuth]: Add a new directory authority: Nicholas Merrill

[Tor Bug Tracker & Wiki]

#21915: Add a new directory authority: Nicholas Merrill
--+--
 Reporter:  dgoulet   |  Owner:  (none)
 Type:  task  | Status:  new
 Priority:  High  |  Milestone:  Tor: unspecified
Component:  Core Tor/DirAuth  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by nickm):

 * milestone:  Tor: 0.3.2.x-final => Tor: unspecified


Comment:

 I'm putting this ticket in "unspecified" for now, but I'm happy to take it
 as soon as the directory authority operators tell me it's time.

--
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] #22972 [Core Tor/Tor]: tor expert bundle only read the first letter from config

[Tor Bug Tracker & Wiki]

#22972: tor expert bundle only read the first letter from config
-+-
 Reporter:  lanealucy|  Owner:  erinn
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.9
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, win32, needs-insight,|  Actual Points:
  needs-win32-testing|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  tor-client => tor-client, win32, needs-insight, needs-
 win32-testing
 * milestone:  Tor: 0.3.2.x-final => Tor: unspecified


Comment:

 Does it work if the quotes are not given?  If the torrc path doesn't
 include spaces?

--
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] #23013 [Core Tor/Tor]: Tor 0.3.0.9 tarball was missing ReleaseNotes entry

[Tor Bug Tracker & Wiki]

#23013: Tor 0.3.0.9 tarball was missing ReleaseNotes entry
--+--
 Reporter:  arma  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by nickm):

 * priority:  Medium => Low
 * milestone:  Tor: 0.3.2.x-final => Tor: unspecified


Comment:

 I'm fine taking a patch to have "make distcheck" check this and complain,
 but I'm also happy just having the checklist and trying to follow it.

--
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] #23146 [Core Tor/Tor]: prop280: Finish privcount-in-Tor proposal (280)

[Tor Bug Tracker & Wiki]

#23146: prop280: Finish privcount-in-Tor proposal (280)
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:  3
 Reviewer:|Sponsor:  SponsorQ
--+
Changes (by nickm):

 * status:  new => accepted
 * owner:  (none) => nickm


--
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] #23372 [Core Tor/Tor]: test: stack-use-after-scope in hs_service/build_update_descriptors

[Tor Bug Tracker & Wiki]

#23372: test: stack-use-after-scope in hs_service/build_update_descriptors
--+
 Reporter:  dgoulet   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Blocker   | Resolution:
 Keywords:  tor-test, tor-hs prop224  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * keywords:  tor-test, tor-hs => tor-test, tor-hs prop224
 * severity:  Normal => Blocker


--
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] #20119 [Core Tor/Tor]: Tor should exit if it fails to write its PidFile, under principle of least confusion. Also, maybe Tor should create the directory that the PidFile points to

[Tor Bug Tracker & Wiki]

#20119: Tor should exit if it fails to write its PidFile, under principle of 
least
confusion. Also, maybe Tor should create the directory that the PidFile
points to
-+-
 Reporter:  yurivict271  |  Owner:  nickm
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.7
 Severity:  Normal   | Resolution:
 Keywords:  easy, fs, tor-relay, usability,  |  Actual Points:  0
  startup|
Parent ID:   | Points:  .5
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  accepted => needs_review


Comment:

 I've done the minimal version (no directory creation), as `ticket20119` in
 my public repository.

 (If we're using the principle of least surprise to justify ourselves here,
 let's not create the directory.)

--
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] #20119 [Core Tor/Tor]: Tor should exit if it fails to write its PidFile, under principle of least confusion. Also, maybe Tor should create the directory that the PidFile points to

[Tor Bug Tracker & Wiki]

#20119: Tor should exit if it fails to write its PidFile, under principle of 
least
confusion. Also, maybe Tor should create the directory that the PidFile
points to
-+-
 Reporter:  yurivict271  |  Owner:  nickm
 Type:  enhancement  | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.7
 Severity:  Normal   | Resolution:
 Keywords:  easy, fs, tor-relay, usability,  |  Actual Points:  0
  startup|
Parent ID:   | Points:  .5
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  new => accepted
 * owner:  (none) => nickm
 * actualpoints:   => 0
 * type:  defect => enhancement
 * milestone:  Tor: unspecified => Tor: 0.3.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] #22731 [Core Tor/Tor]: Relative DataDirectory + RunAsDaemon = Tor can't read or write most of its datadirectory files

[Tor Bug Tracker & Wiki]

#22731: Relative DataDirectory + RunAsDaemon = Tor can't read or write most of 
its
datadirectory files
--+
 Reporter:  arma  |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  .1
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  accepted => needs_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] #22731 [Core Tor/Tor]: Relative DataDirectory + RunAsDaemon = Tor can't read or write most of its datadirectory files

[Tor Bug Tracker & Wiki]

#22731: Relative DataDirectory + RunAsDaemon = Tor can't read or write most of 
its
datadirectory files
--+
 Reporter:  arma  |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  .1
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  new => accepted
 * owner:  (none) => nickm
 * actualpoints:   => .1


Comment:

 See branch `bug22731` in my public repository for a simple implementation
 here.  It turns out that the warn_about_relative_paths() function already
 did most of what we want.

--
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] #23215 [Metrics/CollecTor]: set annotation from descriptor during sync-runs

[Tor Bug Tracker & Wiki]

#23215: set annotation from descriptor during sync-runs
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  defect | Status:  merge_ready
 Priority:  Medium |  Milestone:  CollecTor 1.3.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by iwakeh):

 * status:  needs_review => merge_ready


Comment:

 I added a little more test variety and the changelog entry as
 [https://gitweb.torproject.org/user/iwakeh/collector.git/log/?h=task-23215
 another commit to the above branch].

 Regarding the nitpick:  I find it easier to distinguish between "anno" and
 annos" than "annotation" and "annotations"; in general very long variable
 names feel/look like cluttering.  I changed a few occurrences, but would
 not want to make it a rule.  Anyway, there are all these 'sb', 'is',
 'bais', etc. all over the codebases.  It is true though, that 'anno' might
 be misunderstood as year.

 Setting this to merge ready as I only made very minor changes.  Please
 check again before merging.

--
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] #20168 [Core Tor/Tor]: Clarify our #if{n}def by commenting what they are at the #elif/#else/#endif

[Tor Bug Tracker & Wiki]

#20168: Clarify our #if{n}def by commenting what they are at the 
#elif/#else/#endif
--+
 Reporter:  dgoulet   |  Owner:  cjb
 Type:  enhancement   | Status:  needs_review
 Priority:  Very Low  |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Trivial   | Resolution:
 Keywords:  easy, lorax   |  Actual Points:  .1
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  needs_revision => needs_review
 * reviewer:  nickm =>
 * actualpoints:   => .1


Comment:

 Hm.  So, let's try again. I don't think we can require a specific vim
 plugin if we're going to have this be a regular part of our toolchain.  So
 how about we try it in Python?  I've put a script in an `annotate_ifdefs`
 branch in my public repository that I think does just about everything we
 want.  I've put a sample of its output in `annotate_ifdefs_sample_output`,
 but we should re-run it immediately on merge if we decide to take it.

--
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] #22101 [Core Tor/Tor]: Can't have relative DataDirectory with CookieAuthentication enabled

[Tor Bug Tracker & Wiki]

#22101: Can't have relative DataDirectory with CookieAuthentication enabled
--+
 Reporter:  pastly|  Owner:  Jigsaw52
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor:
  |  0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  wontfix
 Keywords:  review-group-18, review-group-19  |  Actual Points:
Parent ID:  #22731| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  needs_revision => closed
 * resolution:   => wontfix


Comment:

 wontfixing in favor of parent.

--
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] #20456 [Core Tor/Tor]: Relative paths don't work for PidFile and control_auth_cookie

[Tor Bug Tracker & Wiki]

#20456: Relative paths don't work for PidFile and control_auth_cookie
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:  duplicate
 Keywords:  regression?, triaged-out-20170308  |  Actual Points:
Parent ID:  #22101 | Points:  .5
 Reviewer: |Sponsor:
---+---
Changes (by nickm):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 closing in favor of abovementioned tickets.

--
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] #22102 [Core Tor/Tor]: Can't HUP with a relative path in Log line

[Tor Bug Tracker & Wiki]

#22102: Can't HUP with a relative path in Log line
--+
 Reporter:  pastly|  Owner:  Jigsaw52
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor:
  |  0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  wontfix
 Keywords:  review-group-18, review-group-19  |  Actual Points:
Parent ID:  #22731| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  needs_revision => closed
 * resolution:   => wontfix


Comment:

 wontfixing in favor of parent.

--
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] #22692 [Applications/Tor Browser]: Backport Linux content sandboxing from Firefox 54

[Tor Bug Tracker & Wiki]

#22692: Backport Linux content sandboxing from Firefox 54
-+-
 Reporter:  jld  |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  GeorgKoppen201709,   |  Actual Points:
  TorBrowserTeam201709R  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by boklm):

 The `tor-browser-build` patch looks good to me.

--
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] #20424 [Core Tor/Tor]: Remove --enable-openbsd-malloc (Tor maxes CPU when --enable-openbsd-malloc is used) (was: Tor maxes CPU when --enable-openbsd-malloc is used)

[Tor Bug Tracker & Wiki]

#20424: Remove --enable-openbsd-malloc (Tor maxes CPU when 
--enable-openbsd-malloc
is used)
+
 Reporter:  icanhasaccount  |  Owner:  (none)
 Type:  defect  | Status:  needs_revision
 Priority:  Low |  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Minor   | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:  .2
 Reviewer:  |Sponsor:
+
Changes (by nickm):

 * milestone:  Tor: 0.3.2.x-final => Tor: 0.3.4.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] [Tor Bug Tracker & Wiki] Batch modify: #7729, #7743, #13605, #19661, ...

[Tor Bug Tracker & Wiki]

Batch modification to #7729, #7743, #13605, #19661, #7869, #8298, #16301, 
#17903 by nickm:
milestone to Tor: unspecified

Comment:
Mark some needs_revision tickets as unspecified. If/when the revisions happen, 
they can go back into a live milestone.

--
Tickets 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] #22173 [Core Tor/Tor]: Support looking up node by ed25519 identity (backend)

[Tor Bug Tracker & Wiki]

#22173: Support looking up node by ed25519 identity (backend)
--+
 Reporter:  dgoulet   |  Owner:  nickm
 Type:  enhancement   | Status:  needs_review
 Priority:  High  |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  2
Parent ID:| Points:  1
 Reviewer:|Sponsor:
--+

Comment (by nickm):

 If you'd rather look on oniongit, I've also put the branch in a merge
 request at https://oniongit.eu/nickm/tor/merge_requests/7

--
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] #23382 [Applications/Tor Browser]: rbm: Error when the tmp_dir directory does not exist

[Tor Bug Tracker & Wiki]

#23382: rbm: Error when the tmp_dir directory does not exist
+--
 Reporter:  boklm   |  Owner:  boklm
 Type:  task| Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201709R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by boklm):

 * keywords:  tbb-rbm, TorBrowserTeam201709 => tbb-rbm,
   TorBrowserTeam201709R


--
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] #23382 [Applications/Tor Browser]: rbm: Error when the tmp_dir directory does not exist

[Tor Bug Tracker & Wiki]

#23382: rbm: Error when the tmp_dir directory does not exist
---+--
 Reporter:  boklm  |  Owner:  boklm
 Type:  task   | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201709  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by boklm):

 * status:  assigned => needs_review


Comment:

 I attached a patch for `rbm.git` creating the directory if it does not
 exist yet.

--
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] #23382 [Applications/Tor Browser]: rbm: Error when the tmp_dir directory does not exist

[Tor Bug Tracker & Wiki]

#23382: rbm: Error when the tmp_dir directory does not exist
---+--
 Reporter:  boklm  |  Owner:  boklm
 Type:  task   | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201709  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by boklm):

 * Attachment "0001-Bug-23382-create-tmp_dir-if-it-does-not-exist.patch"
 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] #22591 [Webpages/Blog]: Clicking on a comment does not directly jump to it (although the blog seems to try)

[Tor Bug Tracker & Wiki]

#22591: Clicking on a comment does not directly jump to it (although the blog 
seems
to try)
---+--
 Reporter:  gk |  Owner:  hiro
 Type:  defect | Status:  reopened
 Priority:  Medium |  Milestone:
Component:  Webpages/Blog  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #22013 | Points:
 Reviewer: |Sponsor:
---+--

Comment (by cypherpunks):

 Replying to [comment:22 hiro]:
 > JS is disabled everywhere on the dev blog at the moment. So if you have
 the time to surf around a bit that would be nice. There isn't the same
 comment on the prod and dev blogs, but certainly we use the same template.
 STR in comment:10 still works.

--
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] #23415 [Core Tor/Tor]: sample_laplace_distribution() should take multiple random inputs

[Tor Bug Tracker & Wiki]

#23415: sample_laplace_distribution() should take multiple random inputs
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, security-low, privcount,  |  Actual Points:
  031-backport, 030-backport, 029-backport, 028  |
  -backport-maybe, 026-backport-maybe|
Parent ID:  #23061   | Points:  0.5
 Reviewer:   |Sponsor:
-+-

Comment (by catalyst):

 Wouldn't it be better to have a function that outputs a random double in
 (-1.0, +1.0)?  If you're only using 53 bits of entropy from a RNG call
 that generates 64, there are spare bits to use for generating the sign.

--
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] #10089 [Applications/Tor Browser]: middlemouse.contentLoadURL is set to true by default

[Tor Bug Tracker & Wiki]

#10089: middlemouse.contentLoadURL is set to true by default
-+-
 Reporter:  WDXfjqDN4QKGYrlY |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:  new
 Priority:  Low  |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff59-esr-will-have, tbb-backport,|  Actual Points:
  tbb-pref   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * keywords:
 middlemouse, privacy, tbb-firefox-patch, tbb-linkability, ff59-esr-
 will-have, tbb-backport
 => ff59-esr-will-have, tbb-backport, tbb-pref


--
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] #23419 [Internal Services/Service - git]: Delete accidentally-added branches from tor.git repository

[Tor Bug Tracker & Wiki]

#23419: Delete accidentally-added branches from tor.git repository
-+
 Reporter:  nickm|  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Low  |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+
 It looks like some fool (me) has, over the years, added two branches to
 the tor.git repository that should not have gone there.  They are
 `storage_labeled` and `bug19769_029`.

 It would be good to have these branches removed; they don't belong there.

--
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] #23415 [Core Tor/Tor]: sample_laplace_distribution() should take multiple random inputs

[Tor Bug Tracker & Wiki]

#23415: sample_laplace_distribution() should take multiple random inputs
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, security-low, privcount,  |  Actual Points:
  031-backport, 030-backport, 029-backport, 028  |
  -backport-maybe, 026-backport-maybe|
Parent ID:  #23061   | Points:  0.5
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 Should this be in needs_review? I see a suggestion for writing a patch,
 but I don't see the actual patch itself.

--
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] #21642 [Core Tor/Tor]: Prop275: Eliminate "published" times from microdescriptor consensus

[Tor Bug Tracker & Wiki]

#21642: Prop275: Eliminate "published" times from microdescriptor consensus
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  .5
Parent ID:| Points:  2
 Reviewer:|Sponsor:  Sponsor4
--+
Changes (by nickm):

 * cc: prop275, dir-bandwidth, needs-analysis (added)
 * milestone:  Tor: 0.3.2.x-final => Tor: 0.3.4.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] #20832 [Core Tor/Tor]: Design proposals to further improve guard security

[Tor Bug Tracker & Wiki]

#20832: Design proposals to further improve guard security
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  assigned
 Priority:  Medium|  Milestone:  Tor:
  |  0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-guard, TorCoreTeam201705  |  Actual Points:
Parent ID:  #20822| Points:  2
 Reviewer:|Sponsor:  SponsorV-can
--+
Changes (by nickm):

 * milestone:  Tor: 0.3.2.x-final => Tor: 0.3.3.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