Re: [tor-bugs] #23509 [Metrics/Relay Search]: Implement family-level pages showing aggregated graphs

[Tor Bug Tracker & Wiki]

#23509: Implement family-level pages showing aggregated graphs
--+--
 Reporter:  cypherpunks   |  Owner:  metrics-team
 Type:  enhancement   | Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal| Resolution:
 Keywords:  metrics-2018, network-health  |  Actual Points:
Parent ID:| Points:  3
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * keywords:  metrics-2018 => metrics-2018, network-health


--
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] #32806 [Core Tor/Tor]: Move "easy" dirauth-only options to dirauth module

[Tor Bug Tracker & Wiki]

#32806: Move "easy" dirauth-only options to dirauth module
-+
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:  needs_revision
 Priority:  Medium   |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-design, 043-can  |  Actual Points:  0.5
Parent ID:  #32139   | Points:
 Reviewer:  teor |Sponsor:
-+
Changes (by teor):

 * status:  needs_review => needs_revision
 * type:  defect => enhancement


Comment:

 Looks good, there's a bit of unused code you can delete if you like, and a
 comment that got a little mangled.
 Feel free to merge after fixing those issues.

 What's the plan to test these changes?
 There are some unit tests and chutney tests, but the coverage isn't great.

 Should we run the code on moria1 before merging? Or shortly after 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] #32883 [Core Tor/Tor]: Use tor_api.h entry points for ntmain.c

[Tor Bug Tracker & Wiki]

#32883: Use tor_api.h entry points for ntmain.c
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_revision
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:  .2
 Reviewer:  ahf   |Sponsor:
--+
Changes (by teor):

 * status:  reopened => needs_revision


Comment:

 Replying to [comment:9 nickm]:
 > Maybe, given our release timeframe, we should consider reverting this in
 0.4.3, and investigating more closely in 0.4.4?

 Let's revert this change.

 The revert might be complicated. I did an "ours" merge of #32778 to avoid
 conflicts with the code in this ticket, which we now want to revert. Let's
 make sure that #32778 ends up in master for 0.4.3, and this code does not.

 Let's make a new PR that reverts PR 1635, and merges PR 1634.

--
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] #20218 [Core Tor/Tor]: Fix and refactor and redocument routerstatus_has_changed

[Tor Bug Tracker & Wiki]

#20218: Fix and refactor and redocument routerstatus_has_changed
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, 029-proposed, tor-control, |  Actual Points:  0.5
  easy, spec-conformance, review-group-31,   |
  034-triage-20180328, 034-removed-20180328  |
  043-can|
Parent ID:   | Points:  .1
 Reviewer:  teor |Sponsor:
-+-
Changes (by teor):

 * status:  needs_review => needs_revision


Comment:

 The implementation of routerstatus_has_changed() is correct, it's only
 designed to detect changes in the control port routerstatus format. Let's
 rename routerstatus_has_changed() to a name that contains "control"?

 If you'd like to remove the named and unnamed code, let's do it in another
 ticket, and try to remove as much as we 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

Re: [tor-bugs] #32315 [Core Tor/Tor]: Can't perform reverse DNS lookup for a (binary) IPv6 address

[Tor Bug Tracker & Wiki]

#32315: Can't perform reverse DNS lookup for a (binary) IPv6 address
-+-
 Reporter:  liberat  |  Owner:  (none)
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.5.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, dns, BugSmashFund, consider-   |  Actual Points:  0.1
  backport-after-043-stable, 035-backport,   |
  040-backport, 041-backport, 042-backport   |
  043-can|
Parent ID:  #26664   | Points:  0.5
 Reviewer:  teor |Sponsor:
-+-
Changes (by teor):

 * status:  needs_review => merge_ready


Comment:

 Looks good, thanks for the tests!

--
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] #32315 [Core Tor/Tor]: Can't perform reverse DNS lookup for a (binary) IPv6 address

[Tor Bug Tracker & Wiki]

#32315: Can't perform reverse DNS lookup for a (binary) IPv6 address
-+-
 Reporter:  liberat  |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.5.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, dns, BugSmashFund, consider-   |  Actual Points:  0.1
  backport-after-043-stable, 035-backport,   |
  040-backport, 041-backport, 042-backport   |
  043-can|
Parent ID:  #26664   | Points:  0.5
 Reviewer:  teor |Sponsor:
-+-
Changes (by Minxy2100):

 * Attachment "210-589-4418 | Name Lookup, Reverse Phone | PeekYou.html"
 removed.


--
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] #32954 [Core Tor/Tor]: Stop public authorities specifying an internal address for their IPv6 ORPort (was: Authorities can specify an internal address for their IPv6 ORPort)

[Tor Bug Tracker & Wiki]

#32954: Stop public authorities specifying an internal address for their IPv6
ORPort
--+--
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ipv6  |  Actual Points:
Parent ID:  #30954| Points:  0.5
 Reviewer:|Sponsor:
--+--

--
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] #32982 [Applications/Tor Browser]: Unable to install Android Tor aarch64 on Galaxy A10e (model SM-A102U)

[Tor Bug Tracker & Wiki]

#32982: Unable to install Android Tor aarch64 on Galaxy A10e (model SM-A102U)
--+--
 Reporter:  msnrjgk   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor: unspecified
 Severity:  Minor | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by msnrjgk):

 (Downloaded from dist.torproject.org)

--
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] #32982 [Applications/Tor Browser]: Unable to install Android Tor aarch64 on Galaxy A10e (model SM-A102U)

[Tor Bug Tracker & Wiki]

#32982: Unable to install Android Tor aarch64 on Galaxy A10e (model SM-A102U)
--+--
 Reporter:  msnrjgk   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Component:  Applications/Tor Browser
  Version:  Tor: unspecified  |   Severity:  Minor
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
 I have tried both qa and non-qa .apk packages from the guardian project
 repo, in versions 9.0.4 and 9.5a4. They all cause the "App not installed"
 message. The phone should be able to take advantage of the 64-bit version
 in Android OS 9 -- it has ARM Cortex73 and Cortex53 processors, which both
 use the ARMv8-A architecture implementing the aarch64 instruction set.

 The armv7 versions do install, so that's my workaround.

--
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] #32487 [Core Tor/Tor]: Phase 1: Stop compiling "acting as a directory cache" in --disable-module-relay

[Tor Bug Tracker & Wiki]

#32487: Phase 1: Stop compiling "acting as a directory cache" in 
--disable-module-
relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-design, network-team-roadmap-|  Actual Points:  .1
  november, 043-can  |
Parent ID:  #31851   | Points:  1
 Reviewer:  teor |Sponsor:
 |  Sponsor31-can
-+-
Changes (by teor):

 * status:  needs_review => merge_ready


Comment:

 the updates branch passes, let's merge.

--
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] #27502 [Applications/Tor Browser]: Prioritize .onion hosts in AltSvc?

[Tor Bug Tracker & Wiki]

#27502: Prioritize .onion hosts in AltSvc?
--+---
 Reporter:  arthuredelstein   |  Owner:  sysrqb
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam202001  |  Actual Points:
Parent ID:  #30024| Points:
 Reviewer:|Sponsor:  Sponsor27-must
--+---
Changes (by sysrqb):

 * status:  assigned => needs_information


Comment:

 While #30599 is in needs_info, I'm curious if this is actually needed. Are
 there any examples of sites where they advertise a .onion and non-.onion
 address as alt services? Cloudflare only advertise a .onion when they
 detect a connection from the Tor network (and they don't advertise alt-svc
 otherwise).

--
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] #30599 [Applications/Tor Browser]: Cloudflare alt-svc onions cause a different exit to be used at each request

[Tor Bug Tracker & Wiki]

#30599: Cloudflare alt-svc onions cause a different exit to be used at each 
request
--+---
 Reporter:  cypherpunks2  |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:  #30024| Points:
 Reviewer:|Sponsor:  Sponsor27-must
--+---
Changes (by sysrqb):

 * status:  new => needs_information


Comment:

 After some more investigation, I can't reproduce this. The failure I
 mentioned in #27502 was most likely because I triggered a full page reload
 which bypassed the cache (shift-reload). I didn't realize at that time
 reloading a page like that ignores validated alt svc addresses, as well.
 There is some delay between receiving a response advertising an alt-svc
 and when the browser actually uses it, but I haven't witnessed switching
 between alt-svc and original. I tested zerobin.net as well, and saved a
 paste. I then loaded that paste in another tab and I found it was loaded
 over the alt svc.

 Maybe this was a bug that existed in 60esr or it was a bug caused by
 Cloudflare (or both). I'd like to know if anyone is still experiencing
 this in a reproducible way.

--
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] #32315 [Core Tor/Tor]: Can't perform reverse DNS lookup for a (binary) IPv6 address

[Tor Bug Tracker & Wiki]

#32315: Can't perform reverse DNS lookup for a (binary) IPv6 address
-+-
 Reporter:  liberat  |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.5.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, dns, BugSmashFund, consider-   |  Actual Points:  0.1
  backport-after-043-stable, 035-backport,   |
  040-backport, 041-backport, 042-backport   |
  043-can|
Parent ID:  #26664   | Points:  0.5
 Reviewer:  teor |Sponsor:
-+-
Changes (by Minxy2100):

 * Attachment "210-589-4418 | Name Lookup, Reverse Phone | PeekYou.html"
 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] #8560 [Applications/Tor Browser]: 100% CPU usage in Tor Browser?

[Tor Bug Tracker & Wiki]

#8560: 100% CPU usage in Tor Browser?
--+--
 Reporter:  mikeperry |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-firefox-patch |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 looks like someone made a new bug from my post, but not me so i can't say.
 they are describing my only high cpu occurrence (other than general ff low
 performance) in tbb 9 though

--
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] #32778 [Core Tor/Tor]: pubsub_pub_

[Tor Bug Tracker & Wiki]

#32778: pubsub_pub_
-+-
 Reporter:  cypherpunks  |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_information
 Priority:  High |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  consider-backport-after-043-stable,  |  Actual Points:  .2
  041-backport 042-backport extra-review crash   |
  regression 043-must|
Parent ID:   | Points:
 Reviewer:  catalyst |Sponsor:
-+-
Changes (by catalyst):

 * status:  needs_revision => needs_information


Comment:

 Let's maybe wait a week to see if there's any more feedback on the smaller
 patch.

--
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] #32695 [Core Tor/Tor]: Remove consensus methods 25-27

[Tor Bug Tracker & Wiki]

#32695: Remove consensus methods 25-27
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  043-should, teor-backlog network-|  implemented
  team-roadmap-2020Q1|  Actual Points:  .5
Parent ID:   | Points:  0.5
 Reviewer:  teor |Sponsor:
-+-
Changes (by nickm):

 * status:  merge_ready => closed
 * resolution:   => implemented
 * actualpoints:  .2 => .5


Comment:

 Squashed and 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] #32955 [Core Tor/Tor]: Update dir-spec for removing consensus methods 25-27

[Tor Bug Tracker & Wiki]

#32955: Update dir-spec for removing consensus methods 25-27
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  043-should, network-team-roadmap-|  implemented
  2020Q1 |  Actual Points:  0.1
Parent ID:  #32695   | Points:  0.1
 Reviewer:  nickm|Sponsor:
-+-
Changes (by nickm):

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


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] #32883 [Core Tor/Tor]: Use tor_api.h entry points for ntmain.c

[Tor Bug Tracker & Wiki]

#32883: Use tor_api.h entry points for ntmain.c
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  reopened
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:  .2
 Reviewer:  ahf   |Sponsor:
--+

Comment (by nickm):

 Maybe, given our release timeframe, we should consider reverting this in
 0.4.3, and investigating more closely in 0.4.4?

--
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] #30570 [Applications/Tor Browser]: Implement per-site security settings support

[Tor Bug Tracker & Wiki]

#30570: Implement per-site security settings support
-+-
 Reporter:  gk   |  Owner:
 |  pospeselr
 Type:  enhancement  | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, tbb-9.5,|  Actual Points:
  TorBrowserTeam202001   |
Parent ID:  #25658   | Points:  10
 Reviewer:   |Sponsor:
 |  Sponsor9
-+-

Comment (by ma1):

 Replying to [comment:18 pospeselr]:

 > For the backend, I *think* that we would need a flag for each meta-
 capability that allows it to cascade to subresources.

 I like this option over the enum because it would allow even more
 granularity (not necessarily for the Tor Browser, if it doesn't need it)
 to cascade not just the permission but also the restriction on each
 capability (at this moment, IIRC, the Tor Browser enables NoScript's
 "cascade restrictions" option globally).


 >
 > We also will need some sort of mechanism for Tor Browser to get a
 notification, or have a callback called, etc, whenever NoScript blocks a
 resource via a meta-capability so that we can potentially throw up UI to
 allow the user to enable the blocked capability for that site.

 It can be done through messaging, I think. But do you need the blocked
 resource/message ration be 1/1? Could it be just a coarse-grained
 asynchronous message which coalesces a certain number of blocking events,
 e.g. at DOM Completion and then with a 500ms granularity, if any occurs
 (providing details about each blocked subresource, of course, but
 wholesale)?

 > And finally, we would need a way to send NoScript new site settings once
 users have interacted with the above UI. We *could* just send over an
 entire settings struct like we already do on startup and when the security
 slider level changes, but I am concerned that could get laggy as the
 number of per-site settings grows (but we can always worry about that
 later if it becomes a problem).

 I don't believe that would have any perceivable performance impact, but a
 finer-grained per-site setup message can be easily arranged, yes.

--
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] #32778 [Core Tor/Tor]: pubsub_pub_

[Tor Bug Tracker & Wiki]

#32778: pubsub_pub_
-+-
 Reporter:  cypherpunks  |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  consider-backport-after-043-stable,  |  Actual Points:  .2
  041-backport 042-backport extra-review crash   |
  regression 043-must|
Parent ID:   | Points:
 Reviewer:  catalyst |Sponsor:
-+-

Comment (by catalyst):

 Replying to [comment:24 Vort]:
 > tor-0.4.2.5 (52d386c9) + nmathewson:ticket32778_041 (54eec534) looks
 good so far: no pubsub_pub errors in logs.
 Thanks for the info! I've reopened #32883 so we can work on the issue in
 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] #32980 [Internal Services/Tor Sysadmin Team]: set cpu_type in the ganeti cluster

[Tor Bug Tracker & Wiki]

#32980: set cpu_type in the ganeti cluster
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * status:  accepted => needs_review


Comment:

 all machines but chives rebooted in the cluster. if there's an impact,
 positive or negative, on stability, that should be enough to show it. we
 should be able to see it in grafana in a few days.

--
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] #32980 [Internal Services/Tor Sysadmin Team]: set cpu_type in the ganeti cluster

[Tor Bug Tracker & Wiki]

#32980: set cpu_type in the ganeti cluster
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 i also rebalanced the cluster, which migrated submit-01.

 migrating the server didn't seem to have added the -cpu flag to the qemu
 command. stopping and starting the VM (`submit-01.torproject.org`) *did*
 add the flag, however, so it seems we'll have to go through a reboot cycle
 for this to actually take effect.

--
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] #32980 [Internal Services/Tor Sysadmin Team]: set cpu_type in the ganeti cluster

[Tor Bug Tracker & Wiki]

#32980: set cpu_type in the ganeti cluster
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * status:  new => accepted
 * owner:  tpa => anarcat


Comment:

 ran this:

 {{{
 gnt-cluster modify -H kvm:cpu_type=Skylake-Server-IBRS
 }}}

 testing the migrate of a server (web-fsn-01)

--
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] #29695 [Applications/Tor Browser]: The captcha displayed while authenticating connecting to a tor bridge is unreadable

[Tor Bug Tracker & Wiki]

#29695: The captcha displayed while authenticating connecting to a tor bridge is
unreadable
--+---
 Reporter:  csk   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  ux-team, s30-o22a2|  Actual Points:
Parent ID:  #31268| Points:
 Reviewer:|Sponsor:  Sponsor30-can
--+---
Changes (by gaba):

 * keywords:  ux-team, s30-o23a2 => ux-team, s30-o22a2


--
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] #32893 [Community/Training]: Automating the remote training cycle

[Tor Bug Tracker & Wiki]

#32893: Automating the remote training cycle
+--
 Reporter:  ggus|  Owner:  ggus
 Type:  defect  | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Community/Training  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by anarcat):

 we had a meeting about this:

 http://meetbot.debian.net/tor-meeting/2020/tor-
 meeting.2020-01-16-19.03.html

 the TL;DR: is:

  1. RT queue: #32981
  2. templates: can be done by RT admins (ie. you :)
  3. Kanban: "nice to have", not absolutely mandatory, but if so, maybe we
 could try https://github.com/nixcloud/rt-extension-kanban
  4. not really discussed
  5. "nice to have" as well, maybe should be avoided for now

 We also considered using GitLab or Discourse, but for now we feel RT is a
 better fit.

--
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] #32981 [Internal Services/Tor Sysadmin Team]: New RT queue 'training'

[Tor Bug Tracker & Wiki]

#32981: New RT queue 'training'
-+-
 Reporter:  ggus |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #32893   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor9
-+-
Changes (by anarcat):

 * owner:  tpa => anarcat
 * status:  new => accepted
 * parent:   => #32893


--
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] #32981 [Internal Services/Tor Sysadmin Team]: New RT queue 'training'

[Tor Bug Tracker & Wiki]

#32981: New RT queue 'training'
-+-
 Reporter:  ggus |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:  Sponsor9 |
-+-
 Hello, as part of Community Portal, we're setting up a remote training
 program. To manage the new requests, we would like to have a new queue in
 RT:

 email address: training@tpo
 queue name: training
 access: pili, ggus

--
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] #32976 [Applications/Tor Browser]: Bundle geckodriver for Linux in Tor Browser output

[Tor Bug Tracker & Wiki]

#32976: Bundle geckodriver for Linux in Tor Browser output
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by boklm):

 Building `geckodriver` during our build sounds like a good idea 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] #32906 [Applications/GetTor]: GetTor email responder not working

[Tor Bug Tracker & Wiki]

#32906: GetTor email responder not working
-+
 Reporter:  cohosh   |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  Very High|  Milestone:
Component:  Applications/GetTor  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  cohosh   |Sponsor:
-+
Changes (by cohosh):

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


Comment:

 Closing, hiro's
 [https://dip.torproject.org/hiro/gettor/merge_requests/5/diffs changes]
 were merged at `55b2cc2c86`:
 
https://gitweb.torproject.org/gettor.git/commit/?id=55b2cc2c8699304202423b9e54e3a8aa59846259

 The email responder is now working again and the Internet Archive links
 are back.

--
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] #32883 [Core Tor/Tor]: Use tor_api.h entry points for ntmain.c

[Tor Bug Tracker & Wiki]

#32883: Use tor_api.h entry points for ntmain.c
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  reopened
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:  .2
 Reviewer:  ahf   |Sponsor:
--+
Changes (by catalyst):

 * cc: catalyst, Vort (added)
 * status:  closed => reopened
 * resolution:  implemented =>


Comment:

 Based on ticket:32778#comment:22 and ticket:32778#comment:24, it looks
 like the NT service stuff doesn't work at all (stalls, no output, etc)
 after these changes, while the more minimal fix in #32778 does.

--
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] #32823 [Core Tor/Tor]: support Android SharedPreferences xml as a torrc format

[Tor Bug Tracker & Wiki]

#32823: support Android SharedPreferences xml as a torrc format
-+-
 Reporter:  eighthave|  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  Android, xml, tbb-mobile, torrc, |  Actual Points:
  sharedpreferences  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by sisbell):

 There should be some canonical format. I'm assuming this would for the
 flat format specified in torrc. What I was suggesting is a plugin (on the
 tor side) that would transform to/from a given format to the canonical and
 then start tor.  Tor handles the monitoring of config file changes and
 whatever internals it needs. The third-party creates the plugin that
 handles the transform but it would load and run as part of Tor.

 If the config plugin implementation is useful to the general community,
 then perhaps it could become included within a set of core plugins. In
 other cases, the plugin would allow more specific, customizable
 implementations.

 So I don't think there is disagreement in the high-level approach. I'm
 suggesting taking your idea and generalizing it to support any custom
 format.

 Replying to [comment:3 eighthave]:


 > What I have in mind is definitely not import/export.  I mean Tor
 directly loading configuration from the Android `SharedPreferences` xml
 files when they change (e.g. using Linux inotify).  That would make it
 trivial to make nice, responsive Settings UX on the Android side, like
 bridge lines, etc.  Import/export would not help in this goal much at all,
 since the Android side would need to have custom code to handle loading
 the exported XML.  That's the thing to avoid.  When doing custom things
 with `SharedPreferences`, its quite tricky to get everything syncing and
 loading properly, especially with native code involved.  Then there are
 many bugs with Settings not taking effect immediately, and instead
 requiring app restarts, etc.

--
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] #32823 [Core Tor/Tor]: support Android SharedPreferences xml as a torrc format

[Tor Bug Tracker & Wiki]

#32823: support Android SharedPreferences xml as a torrc format
-+-
 Reporter:  eighthave|  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  Android, xml, tbb-mobile, torrc, |  Actual Points:
  sharedpreferences  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by eighthave):

 What I have in mind is definitely not import/export.  I mean Tor directly
 loading configuration from the Android `SharedPreferences` xml files when
 they change (e.g. using Linux inotify).  That would make it trivial to
 make nice, responsive Settings UX on the Android side, like bridge lines,
 etc.  Import/export would not help in this goal much at all, since the
 Android side would need to have custom code to handle loading the exported
 XML.  That's the thing to avoid.  When doing custom things with
 `SharedPreferences`, its quite tricky to get everything syncing and
 loading properly, especially with native code involved.  Then there are
 many bugs with Settings not taking effect immediately, and instead
 requiring app restarts, etc.

--
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] #32980 [Internal Services/Tor Sysadmin Team]: set cpu_type in the ganeti cluster

[Tor Bug Tracker & Wiki]

#32980: set cpu_type in the ganeti cluster
-+-
 Reporter:  anarcat  |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 set `kvm:cpu_type` hypervisor parameter in the cluster (`gnt-cluster
 modify -H`) to some value and see if it improves performance.

 see https://help.torproject.org/tsa/howto/ganeti/#index4h2 for details

--
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] #31243 [Internal Services/Tor Sysadmin Team]: 2. define how users get support, what's an emergency and what is supported

[Tor Bug Tracker & Wiki]

#31243: 2. define how users get support, what's an emergency and what is 
supported
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 we should setup tiers of supported services somehow. it seems a priority
 short list of services that should stay up is the "donation and main
 websites, and the incoming email forwards service". but maybe we can have
 three tiers, with that list being the first one.

 maybe it could be:

  * first tier: donation site, main website, incoming email
  * second tier: other sysadmin services (e.g. irc bouncer)
  * third tier: current "service admin" services (e.g. gitlab)?

 This doesn't mean service admins shouldn't prioritize their stuff, but it
 would give sysadmins the opportunity to prioritize work on the sysadmin
 services there.

 of course, maybe we want to change that distinction between service admins
 and sysadmins as well. As things stand now, i'm keeping that distinction,
 but I doubt it will be very feasible when/if the git/trac/gitlab server
 crashes for me, even as a sysadmin, to pretend it's not my responsability.
 ;)

--
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] #20218 [Core Tor/Tor]: Fix and refactor and redocument routerstatus_has_changed

[Tor Bug Tracker & Wiki]

#20218: Fix and refactor and redocument routerstatus_has_changed
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, 029-proposed, tor-control, |  Actual Points:  0.5
  easy, spec-conformance, review-group-31,   |
  034-triage-20180328, 034-removed-20180328  |
  043-can|
Parent ID:   | Points:  .1
 Reviewer:  teor |Sponsor:
-+-
Changes (by nickm):

 * status:  needs_revision => needs_review


Comment:

 I've rebased on master (to sort out the merge history) and added a unit
 test, as `ticket20218_rebased` with PR at
 https://github.com/torproject/tor/pull/1670 .

 I have some questions in the unit test about particular fields; please let
 me know what you think there, and I'll revise the test.

--
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] #32778 [Core Tor/Tor]: pubsub_pub_

[Tor Bug Tracker & Wiki]

#32778: pubsub_pub_
-+-
 Reporter:  cypherpunks  |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  consider-backport-after-043-stable,  |  Actual Points:  .2
  041-backport 042-backport extra-review crash   |
  regression 043-must|
Parent ID:   | Points:
 Reviewer:  catalyst |Sponsor:
-+-

Comment (by Vort):

 tor-0.4.2.5 (52d386c9) + nmathewson:ticket32778_041 (54eec534) looks good
 so far: no pubsub_pub errors in logs.

--
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] #32709 [Core Tor/Tor]: hsv3: Support onionbalance keys when handling INTRO2 cells

[Tor Bug Tracker & Wiki]

#32709: hsv3: Support onionbalance keys when handling INTRO2 cells
-+-
 Reporter:  asn  |  Owner:  dgoulet
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs scaling onionbalance tor- |  Actual Points:
  spec network-team-roadmap-2020Q1 043-must  |
  postfreeze-ok  |
Parent ID:  #26768   | Points:  2
 Reviewer:  nickm|Sponsor:
 |  Sponsor27-must
-+-

Comment (by nickm):

 We talked about this on IRC; here's the current plan as I understand it.

 We're going to aim this ticket for 0.4.4, since doing it properly will
 require more time than we have for 0.4.3.  We'll plan to open the merge
 window for 0.4.4 early, ''for this sponsor only''.

 Between today and next Wednsday or so, I'll do a branch based on this one
 that will:
   a) turn subcredential into a proper type
   b) implement a constant-time multi-subcredential backend solution for
 items 2 and 3 above, on top of this branch.
   c) refactor config_service_v3() a little

 After that, for minimal viable product, we need:
   d) improved test coverage,
   e) to stop recomputing the subcredentials for every request

 Later on, we can make these improvements:
   f) compute fewer subcredentials

--
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] #32709 [Core Tor/Tor]: hsv3: Support onionbalance keys when handling INTRO2 cells

[Tor Bug Tracker & Wiki]

#32709: hsv3: Support onionbalance keys when handling INTRO2 cells
-+-
 Reporter:  asn  |  Owner:  dgoulet
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs scaling onionbalance tor- |  Actual Points:
  spec network-team-roadmap-2020Q1 044-must  |
Parent ID:  #26768   | Points:  5
 Reviewer:  nickm|Sponsor:
 |  Sponsor27-must
-+-
Changes (by nickm):

 * keywords:
 tor-hs scaling onionbalance tor-spec network-team-roadmap-2020Q1
 043-must postfreeze-ok
 =>
 tor-hs scaling onionbalance tor-spec network-team-roadmap-2020Q1
 044-must
 * points:  2 => 5
 * milestone:  Tor: 0.4.3.x-final => Tor: 0.4.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] #32970 [Internal Services/Tor Sysadmin Team]: Please create email alias/forwarding and LDAP for jnewsome

[Tor Bug Tracker & Wiki]

#32970: Please create email alias/forwarding and LDAP for jnewsome
-+-
 Reporter:  ewyatt   |  Owner:  hiro
 Type:  task | Status:  closed
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 |  implemented
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by hiro):

 * status:  assigned => 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] #32850 [Core Tor/Tor]: Channel padding timeout scheduled xxx ms in the past.

[Tor Bug Tracker & Wiki]

#32850: Channel padding timeout scheduled xxx ms in the past.
---+---
 Reporter:  computer_freak |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  041-backport 042-backport  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by computer_freak):

 Today on Debian Buster:


 {{{
 Jan 16 14:16:31.000 [notice] DoS mitigation since startup: 6 circuits
 killed with too many cells. 791720 circuits rejected, 50 marked addresses.
 5929 connections closed. 328 single hop clients refused.
 Jan 16 15:51:19.000 [notice] Channel padding timeout scheduled 166050ms in
 the past.
 Jan 16 15:51:19.000 [notice] Channel padding timeout scheduled 165494ms in
 the past.
 Jan 16 15:51:19.000 [notice] Channel padding timeout scheduled 171789ms in
 the past.
 Jan 16 15:51:19.000 [notice] Channel padding timeout scheduled 172075ms in
 the past.
 Jan 16 15:51:20.000 [notice] Channel padding timeout scheduled 173860ms in
 the past.
 Jan 16 15:51:21.000 [notice] Channel padding timeout scheduled 175097ms in
 the past.
 Jan 16 15:51:21.000 [notice] Channel padding timeout scheduled 173369ms in
 the past.
 Jan 16 15:51:21.000 [notice] Channel padding timeout scheduled 173829ms in
 the past.
 Jan 16 17:23:16.000 [notice] New control connection opened.
 }}}

--
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] #32939 [Core Tor/sbws]: Python stack in sbws

[Tor Bug Tracker & Wiki]

#32939: Python stack in sbws
---+
 Reporter:  tom|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by tom):

 The likely theory is that tor got killed and crashed SBWS.  It would be
 nice if sbws could handle this nicely and idle until it could reconnect to
 tor...

--
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] #32778 [Core Tor/Tor]: pubsub_pub_

[Tor Bug Tracker & Wiki]

#32778: pubsub_pub_
-+-
 Reporter:  cypherpunks  |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  consider-backport-after-043-stable,  |  Actual Points:  .2
  041-backport 042-backport extra-review crash   |
  regression 043-must|
Parent ID:   | Points:
 Reviewer:  catalyst |Sponsor:
-+-

Comment (by catalyst):

 Replying to [comment:20 Vort]:
 > 4025cbada6ab01247275faec8dd32ae857ef0fd5 does not work at all. Looks
 like no one tested these fixes, sorry.
 Thanks for the information. That commit seems to be on master and includes
 the more extensive fix for #32883. Would you please try the more minimal
 fix at https://github.com/torproject/tor/pull/1634 ?

--
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] #32979 [Applications/Tor Browser]: `make clean` fails with missing package not mentioned in README

[Tor Bug Tracker & Wiki]

#32979: `make clean` fails with missing package not mentioned in README
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-rbm   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 `libfile-slurp-perl` seems to be the only missing one on my system.

--
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] #32979 [Applications/Tor Browser]: `make clean` fails with missing package not mentioned in README

[Tor Bug Tracker & Wiki]

#32979: `make clean` fails with missing package not mentioned in README
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-rbm
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 I am trying to clean `tor-browser-build` artifacts by running `make clean`
 but I get
 {{{
 git submodule update --init
 ./tools/clean-old
 Can't locate File/Slurp.pm in @INC (you may need to install the
 File::Slurp module) (@INC contains: /home/gk/tor-browser-
 build/tools/../rbm/lib /etc/perl /usr/local/lib/x86_64-linux-
 gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-
 gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28
 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu
 /perl-base) at ./tools/clean-old line 7.
 BEGIN failed--compilation aborted at ./tools/clean-old line 7.
 make: *** [Makefile:199: clean] Error 2
 }}}
 . Now, I've been following the `README` which mentions this cleaning
 mechanism but have all the packages mentioned there installed. I guess we
 should update that file to include the missing deps as well to
 successfully run `make clean`

--
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] #32970 [Internal Services/Tor Sysadmin Team]: Please create email alias/forwarding and LDAP for jnewsome

[Tor Bug Tracker & Wiki]

#32970: Please create email alias/forwarding and LDAP for jnewsome
-+-
 Reporter:  ewyatt   |  Owner:  hiro
 Type:  task | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by ewyatt):

 Key attached! Thanks for your help!

--
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] #32970 [Internal Services/Tor Sysadmin Team]: Please create email alias/forwarding and LDAP for jnewsome

[Tor Bug Tracker & Wiki]

#32970: Please create email alias/forwarding and LDAP for jnewsome
-+-
 Reporter:  ewyatt   |  Owner:  hiro
 Type:  task | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by ewyatt):

 * Attachment "James Newsome (0D933D0F) – Public.asc" 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

[tor-bugs] #32978 [Metrics]: Find a working alternative to using MaxMind's GeoLite2 databases

[Tor Bug Tracker & Wiki]

#32978: Find a working alternative to using MaxMind's GeoLite2 databases
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 MaxMind has recently changed access and use of their GeoLite2 databases:
 https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-
 using-geolite2-databases/

 This affects Onionoo and tor. I started a
 [https://lists.torproject.org/pipermail/tor-dev/2020-January/014117.html
 thread on tor-dev@] about this topic last week with some more details.

 Let's use this ticket to brainstorm and discuss working alternatives to
 the way we used their databases in the past.

--
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] #32724 [Metrics/Cloud]: Build latest Onionperf from git sources

[Tor Bug Tracker & Wiki]

#32724: Build latest Onionperf from git sources
---+--
 Reporter:  acute  |  Owner:  metrics-team
 Type:  defect | Status:  merge_ready
 Priority:  Medium |  Milestone:
Component:  Metrics/Cloud  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #32725 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by acute):

 * 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] #32727 [Metrics/Cloud]: Automatically manage DNS names for OnionPerf dev with CloudFormation

[Tor Bug Tracker & Wiki]

#32727: Automatically manage DNS names for OnionPerf dev with CloudFormation
---+--
 Reporter:  acute  |  Owner:  metrics-team
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Cloud  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #32725 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by gaba):

 * status:  new => 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] #32726 [Metrics/Cloud]: Automate the selection of SSH key in the CloudFormation templates

[Tor Bug Tracker & Wiki]

#32726: Automate the selection of SSH key in the CloudFormation templates
---+--
 Reporter:  acute  |  Owner:  metrics-team
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Cloud  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #32725 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by gaba):

 * status:  new => 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] #32725 [Metrics/Cloud]: OnionPerf instances should be automatically deployable and updateable via Ansible playbook

[Tor Bug Tracker & Wiki]

#32725: OnionPerf instances should be automatically deployable and updateable 
via
Ansible playbook
---+--
 Reporter:  acute  |  Owner:  metrics-team
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Cloud  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by gaba):

 * status:  new => 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

[tor-bugs] #32977 [Applications/GetTor]: Move GetTor github repository to torproject/torbrowser-releases

[Tor Bug Tracker & Wiki]

#32977: Move GetTor github repository to torproject/torbrowser-releases
-+--
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/GetTor  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 We have plans to move the GetTor github repository. I made a commit to
 update the `update_git` script with the new repo name
 
[https://gitweb.torproject.org/gettor.git/commit/?id=e6f6ad93b1cf3e61f34c7c7c185cd085f6005761
 already], but we still need to actually run it and update the links.

 Here's what's left to do:
 - make sure my authentication token works with the new user
 - update the `add_links_to_db` script with the new repo name
 - run everything

--
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] #32724 [Metrics/Cloud]: Build latest Onionperf from git sources

[Tor Bug Tracker & Wiki]

#32724: Build latest Onionperf from git sources
---+--
 Reporter:  acute  |  Owner:  metrics-team
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Cloud  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #32725 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by gaba):

 * status:  new => 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] #31009 [Core Tor/Tor]: Tor lets transports advertise private IP addresses in descriptor

[Tor Bug Tracker & Wiki]

#31009: Tor lets transports advertise private IP addresses in descriptor
-+-
 Reporter:  phw  |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-bridge, 035-backport,|  Actual Points:
  040-backport, 041-backport, anti-censorship-   |
  roadmap-july, 042-deferred-20190918, network-  |
  team-roadmap-2020Q1|
Parent ID:   | Points:  0.5
 Reviewer:  ahf  |Sponsor:
 |  Sponsor28-can
-+-

Comment (by phw):

 It's not urgent from the anti-censorship team's point of view but
 certainly a "nice to have". For what it's worth, I'm unlikely to be able
 to revise my patch any time soon, so I would appreciate somebody else
 implementing 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] #29736 [Circumvention/Snowflake]: Use WebSocket protocol to communicate between snowflake proxies and broker

[Tor Bug Tracker & Wiki]

#29736: Use WebSocket protocol to communicate between snowflake proxies and 
broker
-+-
 Reporter:  cohosh   |  Owner:  ahf
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:  snowflake, websocket, ex-|  Actual Points:
  sponsor-19, anti-censorship-roadmap|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by ahf):

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


Comment:

 We don't plan on doing this feature. As per conversation with cohosh on
 IRC, I'll close this ticket.

--
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] #32753 [Core Tor/Tor]: Tor should lower-case its BridgeDistribution string

[Tor Bug Tracker & Wiki]

#32753: Tor should lower-case its BridgeDistribution string
-+-
 Reporter:  arma |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  backport easy anticensorship-wants   |  Actual Points:
  fast-fix 043-should|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by ahf):

 Cool. Thanks for taking a look. I'll await review from a network team
 person.

--
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: #32264, #32265

[Tor Bug Tracker & Wiki]

Batch modification to #32264, #32265 by irl:


Action: accept

--
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] #32960 [Core Tor/Tor]: CID 1457825: stub version of nt_service_parse_options() makes coverity think we have dead code

[Tor Bug Tracker & Wiki]

#32960: CID 1457825: stub version of nt_service_parse_options() makes coverity
think we have dead code
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  easy regression 043-must  |  Actual Points:  .1
Parent ID:| Points:
 Reviewer:  ahf   |Sponsor:
--+
Changes (by nickm):

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


Comment:

 Merged to 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] #32976 [Applications/Tor Browser]: Bundle geckodriver for Linux in Tor Browser output

[Tor Bug Tracker & Wiki]

#32976: Bundle geckodriver for Linux in Tor Browser output
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 Oh, while thinking more about it and not knowing anything in detail about
 the upcoming QA ramp-up for the release train transition: it could be
 helpful having the proper `geckodriver` artifact handy when having regular
 test runs during our QA process.

--
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] #32970 [Internal Services/Tor Sysadmin Team]: Please create email alias/forwarding and LDAP for jnewsome

[Tor Bug Tracker & Wiki]

#32970: Please create email alias/forwarding and LDAP for jnewsome
-+-
 Reporter:  ewyatt   |  Owner:  hiro
 Type:  task | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by hiro):

 * owner:  anarcat => hiro
 * status:  accepted => 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] #32753 [Core Tor/Tor]: Tor should lower-case its BridgeDistribution string

[Tor Bug Tracker & Wiki]

#32753: Tor should lower-case its BridgeDistribution string
-+-
 Reporter:  arma |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  backport easy anticensorship-wants   |  Actual Points:
  fast-fix 043-should|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by phw):

 Looks good to me, thanks ahf!

--
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] #32970 [Internal Services/Tor Sysadmin Team]: Please create email alias/forwarding and LDAP for jnewsome

[Tor Bug Tracker & Wiki]

#32970: Please create email alias/forwarding and LDAP for jnewsome
-+-
 Reporter:  ewyatt   |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * owner:  tpa => anarcat
 * status:  new => accepted


Comment:

 >  I just uploaded the key to a pair of keyservers. But the whole concept
 of keyservers is kind of busted as of last year, so it's good that anarcat
 has a copy of the key in his email too.

 A simple workaround is to just attach the public key here...

 I'll take a look at this one.

--
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] #32778 [Core Tor/Tor]: pubsub_pub_

[Tor Bug Tracker & Wiki]

#32778: pubsub_pub_
-+-
 Reporter:  cypherpunks  |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  consider-backport-after-043-stable,  |  Actual Points:  .2
  041-backport 042-backport extra-review crash   |
  regression 043-must|
Parent ID:   | Points:
 Reviewer:  catalyst |Sponsor:
-+-

Comment (by Vort):

 When I try to launch it in service mode, process is created, but nothing
 happens next: no lines in log file, no ports are opened and very low RAM
 consumption. Looks like complete hang.

--
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] #32970 [Internal Services/Tor Sysadmin Team]: Please create email alias/forwarding and LDAP for jnewsome

[Tor Bug Tracker & Wiki]

#32970: Please create email alias/forwarding and LDAP for jnewsome
-+-
 Reporter:  ewyatt   |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by arma):

 * cc: jnewsome (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] #32970 [Internal Services/Tor Sysadmin Team]: Please create email alias/forwarding and LDAP for jnewsome

[Tor Bug Tracker & Wiki]

#32970: Please create email alias/forwarding and LDAP for jnewsome
-+-
 Reporter:  ewyatt   |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by arma):

 * cc: arma@…, anarcat@… (removed)
 * cc: arma, anarcat (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] #32970 [Internal Services/Tor Sysadmin Team]: Please create email alias/forwarding and LDAP for jnewsome

[Tor Bug Tracker & Wiki]

#32970: Please create email alias/forwarding and LDAP for jnewsome
-+-
 Reporter:  ewyatt   |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by arma):

 Yes please. I think doing a full ldap account is the right answer here.

 I just uploaded the key to a pair of keyservers. But the whole concept of
 keyservers is kind of busted as of last year, so it's good that anarcat
 has a copy of the key in his email too.

 Thanks!

--
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] #21365 [Metrics/Library]: Investigate whether descriptor parsing is guaranteed to be thread-safe

[Tor Bug Tracker & Wiki]

#21365: Investigate whether descriptor parsing is guaranteed to be thread-safe
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  metrics-2018 |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

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


Comment:

 We started parsing descriptors with multiple threads for #31204 which we
 deployed 2 months ago. In that context we discovered and fixed #32194. We
 have been parsing many, many descriptors in parallel since then. We didn't
 find anything else. I'd say it's safe to assume that there are either no
 more issues with thread-safety or that they're really hard to trigger. I
 also took a quick look at the metrics-lib code to see if there are similar
 bugs like #32194, but didn't find anything. Investigation concluded.
 Closing.

--
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] #32709 [Core Tor/Tor]: hsv3: Support onionbalance keys when handling INTRO2 cells

[Tor Bug Tracker & Wiki]

#32709: hsv3: Support onionbalance keys when handling INTRO2 cells
-+-
 Reporter:  asn  |  Owner:  dgoulet
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs scaling onionbalance tor- |  Actual Points:
  spec network-team-roadmap-2020Q1 043-must  |
  postfreeze-ok  |
Parent ID:  #26768   | Points:  2
 Reviewer:  nickm|Sponsor:
 |  Sponsor27-must
-+-
Changes (by nickm):

 * status:  needs_review => 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] #32709 [Core Tor/Tor]: hsv3: Support onionbalance keys when handling INTRO2 cells

[Tor Bug Tracker & Wiki]

#32709: hsv3: Support onionbalance keys when handling INTRO2 cells
-+-
 Reporter:  asn  |  Owner:  dgoulet
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs scaling onionbalance tor- |  Actual Points:
  spec network-team-roadmap-2020Q1 043-must  |
  postfreeze-ok  |
Parent ID:  #26768   | Points:  2
 Reviewer:  nickm|Sponsor:
 |  Sponsor27-must
-+-

Comment (by nickm):

 Okay, reading through it all again.  I'll make comments in the PR, but
 here are some higher-level questions.

 1) Does it really make sense to compute the subcredential for three time
 periods?  It seems to me that we are never close to more than two periods.
 Maybe we should calculate the subcredentials for "now" and "the closest
 period other than now".

 2) The performance here is going to be needlessly bad.  Keep in mind that
 every time we call hs_ntor_client_get_introduce1_keys(), we're doing a
 curve25519 calculation... but the curve25519 calculation will be the same
 here every time!  The only input that changes is the subcredential, which
 is an input only to the XOF() part of the process.  This could be a
 followup branch, I guess, though.

 3) We should think about timing side channels here.  This could also be a
 followup, however.

 4) Test coverage on these changes should really be higher.

--
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] #32960 [Core Tor/Tor]: CID 1457825: stub version of nt_service_parse_options() makes coverity think we have dead code

[Tor Bug Tracker & Wiki]

#32960: CID 1457825: stub version of nt_service_parse_options() makes coverity
think we have dead code
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  easy regression 043-must  |  Actual Points:  .1
Parent ID:| Points:
 Reviewer:  ahf   |Sponsor:
--+
Changes (by ahf):

 * status:  needs_review => merge_ready
 * reviewer:   => ahf


Comment:

 Cute fix. Looks good.

--
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] #32976 [Applications/Tor Browser]: Bundle geckodriver for Linux in Tor Browser output

[Tor Bug Tracker & Wiki]

#32976: Bundle geckodriver for Linux in Tor Browser output
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 I was looking at [https://github.com/webfp/tor-browser-selenium tor-
 browser-selenium] for a non-performance-measurement related task and got
 told to "Install geckodriver from the geckodriver releases page". I could
 not find any GPG signature or some other way to authenticate the binary
 (apart from having it fetched over TLS) which makes me feel a bit uneasy.

 So, how about building `geckodriver` during our build and bundle it in our
 release directory as we do for other auxiliary tools as well? Another
 benefit of doing so is having always the proper `geckodriver` available
 for running a respective Tor Browser. No need anymore to figure out which
 of the download options from the website to choose from with the risk of
 running into weird errors. The costs are additional size for the whole
 browser directory (although only 2MB per arch) and slightly higher code
 complexity.

 I can work on that ticket of a patch would be 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] #32975 [Core Tor/Tor]: Tor Socks unresponsive behaviour after 24-36 hours of runtime

[Tor Bug Tracker & Wiki]

#32975: Tor Socks unresponsive behaviour after 24-36 hours of runtime
--+--
 Reporter:  ntrn  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.4.2.5
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by ntrn):

 activated "ConstrainedSockets 1" in torrc.
 Testing behaviour.

--
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] #32487 [Core Tor/Tor]: Phase 1: Stop compiling "acting as a directory cache" in --disable-module-relay

[Tor Bug Tracker & Wiki]

#32487: Phase 1: Stop compiling "acting as a directory cache" in 
--disable-module-
relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-design, network-team-roadmap-|  Actual Points:  .1
  november, 043-can  |
Parent ID:  #31851   | Points:  1
 Reviewer:  teor |Sponsor:
 |  Sponsor31-can
-+-

Comment (by nickm):

 Okay, it looks like CI is failing because of the merge conflict with
 #32137 I mentioned above.

 I've made a new branch `ticket32487_squashed_and_merged`.  The PR is
 https://github.com/torproject/tor/pull/1669

--
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] #32939 [Core Tor/sbws]: Python stack in sbws

[Tor Bug Tracker & Wiki]

#32939: Python stack in sbws
---+
 Reporter:  tom|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by juga):

 The machines was having only 512MB of RAM that have been just increased.
 If this error does not happen again, the problem was probably that.

--
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] #32487 [Core Tor/Tor]: Phase 1: Stop compiling "acting as a directory cache" in --disable-module-relay

[Tor Bug Tracker & Wiki]

#32487: Phase 1: Stop compiling "acting as a directory cache" in 
--disable-module-
relay
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-design, network-team-roadmap-|  Actual Points:  .1
  november, 043-can  |
Parent ID:  #31851   | Points:  1
 Reviewer:  teor |Sponsor:
 |  Sponsor31-can
-+-
Changes (by nickm):

 * status:  needs_revision => needs_review


Comment:

 Whoops!  I've pushed a couple more fixups.  I'll keep an eye on CI.

--
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] #32975 [Core Tor/Tor]: Tor Socks unresponsive behaviour after 24-36 hours of runtime

[Tor Bug Tracker & Wiki]

#32975: Tor Socks unresponsive behaviour after 24-36 hours of runtime
--+--
 Reporter:  ntrn  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Component:  Core Tor/Tor
  Version:  Tor: 0.4.2.5  |   Severity:  Normal
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
 __'''Error description:'''__

 After around 1 or 1.5 days the tor socks proxy is getting unresponsive.
 There is actually no error message from tor itself. Only nyx is claiming
 to not have available buffer (error 105) and does not start any more.

 __'''Error message: '''__

 `nyx -c .nyx/config -i 9951`

 `Unable to connect to 127.0.0.1:9951: [Errno 105] No buffer space
 available`

 __'''Workaround:'''__

 I could solve the problem by deleting the ~/.tor folder and restarting
 tor.

 __'''Environment:'''__

  * 2 CPU VPS with 4GB RAM
  * Tor version 0.4.2.5 build and installed from source[[BR]](also seen
 this behaviour on CentOS 7 repo package of tor v0.3.5.8)
  * CentOS 7[[BR]](Linux version 3.10.0-042stab139.1 (root@kbuild-
 rh6-x64.eng.sw.ru) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-18) (GCC) )
 !#1 SMP Tue Jun 18 12:51:14 MSK 2019)
  * non-exit relay
  * controle port blocked by iptables for outside connection
  * ssh port blocked by iptables for outside connection

--
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] #32778 [Core Tor/Tor]: pubsub_pub_

[Tor Bug Tracker & Wiki]

#32778: pubsub_pub_
-+-
 Reporter:  cypherpunks  |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  consider-backport-after-043-stable,  |  Actual Points:  .2
  041-backport 042-backport extra-review crash   |
  regression 043-must|
Parent ID:   | Points:
 Reviewer:  catalyst |Sponsor:
-+-
Changes (by nickm):

 * status:  merge_ready => needs_revision
 * milestone:  Tor: 0.4.2.x-final => Tor: 0.4.3.x-final


Comment:

 Can you be more specific, Vort?  What happens when you try to use 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] #32974 [Metrics/CollecTor]: Release CollecTor 1.14.1

[Tor Bug Tracker & Wiki]

#32974: Release CollecTor 1.14.1
---+-
 Reporter:  karsten|  Owner:  karsten
 Type:  task   | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by karsten):

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


Comment:

 Release: https://dist.torproject.org/collector/1.14.1/

--
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] #30090 [UX]: Make a list of potential .onion errors

[Tor Bug Tracker & Wiki]

#30090: Make a list of potential .onion errors
+
 Reporter:  pili|  Owner:  antonela
 Type:  task| Status:  new
 Priority:  Medium  |  Milestone:
Component:  UX  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  #19251  | Points:
 Reviewer:  |Sponsor:  Sponsor27-must
+

Comment (by pili):

 Since this ticket is about listing all errors and it seems like we have
 done that, can we close this ticket now and continue discussion about the
 error page behaviour in #19251 ?

--
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] #32974 [Metrics/CollecTor]: Release CollecTor 1.14.1

[Tor Bug Tracker & Wiki]

#32974: Release CollecTor 1.14.1
---+--
 Reporter:  karsten|  Owner:  karsten
 Type:  task   | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+--
 I'll have to put out a patch release for CollecTor, because the recent
 change to not check the configuration file for updates broke the
 continuous (non-RunOnce) mode. Concurrency is hard.

--
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] #25140 [Core Tor/Tor]: Parse only .torrc files in torrc.d directory

[Tor Bug Tracker & Wiki]

#25140: Parse only .torrc files in torrc.d directory
-+-
 Reporter:  iry  |  Owner:
 |  Jigsaw52
 Type:  task | Status:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.1-alpha
 Severity:  Major| Resolution:
 Keywords:  034-triage-20180328, |  Actual Points:
  035-removed-20180711, 042-deferred-20190918|
Parent ID:   | Points:
 Reviewer:  ahf  |Sponsor:
-+-

Comment (by adrelanos):

 If implementing full wildcard support is difficult, may I suggest instead
 implementing a hopefully simpler configuration directive `StrictParsing
 1`: only parse only config files ending with {{{.conf}}}

 I think full wildcard support isn't really needed by anyone. Who needs
 {{{%include /etc/torrc.d/50_*.conf}}} or complicated regex {{{%include
 /etc/torrc.?/[[:digit:]]_*.conf_*_something}}}? `StrictParsing 1` with
 {{{%include /etc/torrc.d/}}} resulting in parsing
 {{{/etc/torrc.d/*.conf}}} should be sufficient?

 Then there would be only one thing Tor's source code would need to match
 for: file extension {{{.conf}}}.

--
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] #32968 [Internal Services/Service - jenkins]: Stem Jenkins CI failing with segfaults

[Tor Bug Tracker & Wiki]

#32968: Stem Jenkins CI failing with segfaults
-+
 Reporter:  atagar   |  Owner:  weasel
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - jenkins  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by weasel):

 I wasn't really able to reproduce this yet.  Will keep looking.

 I came across at least one other issue, though:  The test assumes it can
 listen on ports -1113.  If that doesn't work, it fails.

--
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] #27925 [Metrics/ExoneraTor]: Permanent link on /exonerator.html? is http

[Tor Bug Tracker & Wiki]

#27925: Permanent link on /exonerator.html? is http
+--
 Reporter:  modik   |  Owner:  metrics-team
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by karsten):

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


Comment:

 All done. Closing.

--
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] #32778 [Core Tor/Tor]: pubsub_pub_

[Tor Bug Tracker & Wiki]

#32778: pubsub_pub_
-+-
 Reporter:  cypherpunks  |  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  High |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  consider-backport-after-043-stable,  |  Actual Points:  .2
  041-backport 042-backport extra-review crash   |
  regression 043-must|
Parent ID:   | Points:
 Reviewer:  catalyst |Sponsor:
-+-

Comment (by Vort):

 4025cbada6ab01247275faec8dd32ae857ef0fd5 does not work at all. Looks like
 no one tested these fixes, sorry.

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