[tor-bugs] #23928 [Core Tor/Tor]: Tor drops all connections

[Tor Bug Tracker & Wiki]

#23928: Tor drops all connections
--+--
 Reporter:  BoBeR182  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.1.7
 Severity:  Major |   Keywords:  tor dropping connections
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Tor drops all my connections.

 This is what journalctl has to say:

 REDACTED26:36 REDACTED Tor[13516]: Bug: /usr/bin/tor(_start+0x2a)
 [0x56150e7fb67a] (on Tor 0.3.1.7 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: Bug:
 /usr/lib/libc.so.6(__libc_start_main+0xea) [0x7f19752f3f6a] (on Tor
 0.3.1.7 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: Bug: /usr/bin/tor(main+0x1a)
 [0x56150e7fb61a] (on Tor 0.3.1.7 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: Bug: /usr/bin/tor(tor_main+0xf35)
 [0x56150e802da5] (on Tor 0.3.1.7 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: Bug:
 /usr/bin/tor(do_main_loop+0x252) [0x56150e7ffe92] (on Tor 0.3.1.7
 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: Bug:
 /usr/lib/libevent-2.1.so.6(event_base_loop+0x53f) [0x7f1976620b1f] (on Tor
 0.3.1.7 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: Bug:
 /usr/lib/libevent-2.1.so.6(+0x220d8) [0x7f19766200d8] (on Tor 0.3.1.7
 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: Bug: /usr/bin/tor(+0x4beef)
 [0x56150e7feeef] (on Tor 0.3.1.7 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: Bug: /usr/bin/tor(+0x10b987)
 [0x56150e8be987] (on Tor 0.3.1.7 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: Bug:
 /usr/bin/tor(connection_edge_process_inbuf+0x1ea) [0x56150e8c668a] (on Tor
 0.3.1.7 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: Bug:
 /usr/bin/tor(connection_edge_package_raw_inbuf+0x1ee) [0x56150e825bae] (on
 Tor 0.3.1.7 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: Bug:
 /usr/bin/tor(connection_edge_send_command+0x62) [0x56150e825892] (on Tor
 0.3.1.7 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: Bug:
 /usr/bin/tor(relay_send_command_from_edge_+0x451) [0x56150e825421] (on Tor
 0.3.1.7 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: Bug:
 /usr/bin/tor(log_backtrace+0x45) [0x56150e923975] (on Tor 0.3.1.7
 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: Bug: . Stack trace: (on Tor 0.3.1.7
 6babd3d9ba9318b3)
 REDACTED26:36 REDACTED Tor[13516]: circuit_package_relay_cell(): Bug:
 outgoing relay cell sent from src/or/relay.c:839 has n_chan==NULL.
 Dropping. (on Tor 0.3.1.7 6babd3d9ba9318b3)

--
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] #23901 [Internal Services/Service - git]: Add Stefani Banerian (bastet) to the dirauth-conf git repository

[Tor Bug Tracker & Wiki]

#23901: Add Stefani Banerian (bastet) to the dirauth-conf git repository
-+
 Reporter:  micah|  Owner:  tor-gitadm
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  dirauth, git |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by Sebastian):

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


Comment:

 [x]

--
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] #23926 [Internal Services/Service - trac]: Please create a component for Metrics/Bot

[Tor Bug Tracker & Wiki]

#23926: Please create a component for Metrics/Bot
--+
 Reporter:  irl   |  Owner:  qbi
 Type:  task  | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by qbi):

 * status:  new => closed
 * 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] #23871 [Metrics/Atlas]: Atlas top-10 drop down broken

[Tor Bug Tracker & Wiki]

#23871: Atlas top-10 drop down broken
---+---
 Reporter:  phoul  |  Owner:  Hedylogos
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by Hedylogos):

 * status:  accepted => needs_information


--
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] #23871 [Metrics/Atlas]: Atlas top-10 drop down broken

[Tor Bug Tracker & Wiki]

#23871: Atlas top-10 drop down broken
---+---
 Reporter:  phoul  |  Owner:  Hedylogos
 Type:  defect | Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by Hedylogos):

 setting the limit to 100 in router.js at line 106? fixes this problem.
 {{{
 
https://onionoo.torproject.org/summary?type=relay=-consensus_weight=100=true
 }}}
 But there might be performances issues which should be fixed already
 #15395 and #19452

--
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] #23016 [Applications/Tor Browser]: "Print to File" does not create the expected file in non-English locales

[Tor Bug Tracker & Wiki]

#23016: "Print to File" does not create the expected file in non-English locales
-+-
 Reporter:  intrigeri|  Owner:
 |  pospeselr
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  AffectsTails, tbb-7.0-issues, tbb-   |  Actual Points:
  regression, tbb-e10s   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by pospeselr):

 So I've recreated intrigeri's setup mentioned above in a VM: debian,
 reconfigured to fr_FR, and using stock 7.0.6 French Tor Browser and I am
 seeing print errors, though not in the way described :(

 With the above described configuration about:tor always fails to print,
 while about:support always succeeds.  The javascript.use_us_english_locale
 setting has no effect on the outcome.

 Discovered in all this that apparently build we release don't have
 symbols(?) so haven't had much luck debugging this issue.  Simply dropping
 in a locally built version of Tor Browser on top of the install seems to
 make the issue go away and behave as expected.  Working on building FR sku
 from scratch via rbm and working from there once I've a build with symbols
 and source.

--
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] #23871 [Metrics/Atlas]: Atlas top-10 drop down broken

[Tor Bug Tracker & Wiki]

#23871: Atlas top-10 drop down broken
---+---
 Reporter:  phoul  |  Owner:  Hedylogos
 Type:  defect | Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by Hedylogos):

 * status:  new => accepted
 * owner:  metrics-team => Hedylogos


--
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] #23927 [Core Tor/Tor]: I can not get Tor to start on my ubuntu relay 16.04.3 LTS

[Tor Bug Tracker & Wiki]

#23927: I can not get Tor to start on my ubuntu relay 16.04.3 LTS
---+
 Reporter:  Dbryrtfbcbhgf  |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Tor   |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 When I SSH to my relay running Ubuntu 16.04.3 LTS relay running Tor
 0.3.1.7, I use the command "service tor start" and nothing happens, I
 check my notice logs and it is not running. The only way I can get it
 running is to type "tor" click "return" and then termate Terminal. "I do
 not think that is how I should start tor"


 my relay.
 https://atlas.torproject.org/#details/F02966BCABC42BE89AFF4C3E138C3CCA0FDF4D2C

--
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] #23868 [Metrics/Atlas]: Long contactInfo is not properly displayed

[Tor Bug Tracker & Wiki]

#23868: Long contactInfo is not properly displayed
---+---
 Reporter:  cypherpunks|  Owner:  Hedylogos
 Type:  defect | Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by Hedylogos):

 
https://github.com/jorenvandeweyer/atlas/commit/0f30e213b2920928ab6c20b13f6f6d9f37e618e9

--
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] #23868 [Metrics/Atlas]: Long contactInfo is not properly displayed

[Tor Bug Tracker & Wiki]

#23868: Long contactInfo is not properly displayed
---+--
 Reporter:  cypherpunks|  Owner:  Hedylogos
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by Hedylogos):

 * 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] #22261 [Metrics/Onionoo]: Remove the $ from family fingerprints

[Tor Bug Tracker & Wiki]

#22261: Remove the $ from family fingerprints
-+--
 Reporter:  teor |  Owner:  karsten
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2017 |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by irl):

 * status:  needs_review => assigned
 * owner:  irl => karsten


Comment:

 Reassigning to karsten as this is an Onionoo issue 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] #23868 [Metrics/Atlas]: Long contactInfo is not properly displayed

[Tor Bug Tracker & Wiki]

#23868: Long contactInfo is not properly displayed
---+---
 Reporter:  cypherpunks|  Owner:  Hedylogos
 Type:  defect | Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by Hedylogos):

 * owner:  metrics-team => Hedylogos
 * 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] #23890 [Metrics/Atlas]: Display >365 as years in relative first seen time and drop hours and seconds

[Tor Bug Tracker & Wiki]

#23890: Display >365 as years in relative first seen time and drop hours and
seconds
---+--
 Reporter:  cypherpunks|  Owner:  Hedylogos
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by Hedylogos):

 * 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] #23890 [Metrics/Atlas]: Display >365 as years in relative first seen time and drop hours and seconds

[Tor Bug Tracker & Wiki]

#23890: Display >365 as years in relative first seen time and drop hours and
seconds
---+---
 Reporter:  cypherpunks|  Owner:  Hedylogos
 Type:  enhancement| Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by Hedylogos):

 
https://github.com/jorenvandeweyer/atlas/commit/9fba94d39f77f6e867fe491c7b78b0fd86156c4d

--
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] #23890 [Metrics/Atlas]: Display >365 as years in relative first seen time and drop hours and seconds

[Tor Bug Tracker & Wiki]

#23890: Display >365 as years in relative first seen time and drop hours and
seconds
---+---
 Reporter:  cypherpunks|  Owner:  Hedylogos
 Type:  enhancement| Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by Hedylogos):

 * status:  new => accepted
 * owner:  metrics-team => Hedylogos


--
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] #23893 [Applications/Tor Browser]: Tor Browser page tabs crash on initial loading of sites including Tor

[Tor Bug Tracker & Wiki]

#23893: Tor Browser page tabs crash on initial loading of sites including Tor
--+
 Reporter:  rollingstone  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  worksforme
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by gk):

 * status:  needs_information => closed
 * resolution:   => worksforme


Comment:

 Replying to [comment:4 rollingstone]:
 > I am beginning to think ipVanish is the problem. I have been using Tor
 browser without it and I haven't had a page crash yet. I haven't tried the
 alpha yet

 Neat. Let's assume ipVanish is the culprit. No need to test the alpha
 then. Please reopen this bug if our assumption was wrong.

--
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] #23921 [Applications/Tor Browser]: Video not working (Tab crashing OR mp4 decoder not found)

[Tor Bug Tracker & Wiki]

#23921: Video not working (Tab crashing OR mp4 decoder not found)
--+---
 Reporter:  sd3e2423ada   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  duplicate
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by gk):

 * status:  reopened => 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] #23918 [Applications/Tor Browser]: tor button and tor browser home page says "not connected to network"

[Tor Bug Tracker & Wiki]

#23918: tor button and tor browser home page says "not connected to network"
--+---
 Reporter:  tortracfree   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-torbutton |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by gk):

 Replying to [comment:4 tortracfree]:
 > Replying to [comment:3 gk]:
 > > Could you add additional logs in case this happens again?
 > Do you mean right now or when it happens again?

 When it happens again.

--
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] #23921 [Applications/Tor Browser]: Video not working (Tab crashing OR mp4 decoder not found)

[Tor Bug Tracker & Wiki]

#23921: Video not working (Tab crashing OR mp4 decoder not found)
--+--
 Reporter:  sd3e2423ada   |  Owner:  tbb-team
 Type:  defect| Status:  reopened
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * 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] #23921 [Applications/Tor Browser]: Video not working (Tab crashing OR mp4 decoder not found)

[Tor Bug Tracker & Wiki]

#23921: Video not working (Tab crashing OR mp4 decoder not found)
--+--
 Reporter:  sd3e2423ada   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  fixed
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 No worries. Glad it works for you now. This is actually a duplicate of
 #23807.

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

[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 Hello71):

 * Attachment "0001-Add-with-jemalloc.-20424-23777.patch" added.

 patch to add --with-jemalloc

--
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] #23926 [Internal Services/Service - trac]: Please create a component for Metrics/Bot

[Tor Bug Tracker & Wiki]

#23926: Please create a component for Metrics/Bot
--+-
 Reporter:  irl   |  Owner:  qbi
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 Please create the component Metrics/Bot and set the default owner to
 myself (irl) 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

[tor-bugs] #23925 [Applications/Tor Browser]: 2018 Tor Browser banner

[Tor Bug Tracker & Wiki]

#23925: 2018 Tor Browser banner
--+--
 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:|
--+--
 At end of 2018 we will likely want to make another fundraising banner in
 Tor Browser with a donation button. Let's make the activation time the
 same for all time zones, so we have a simultaneous launch.

--
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] #23924 [Core Tor/Tor]: Improve control-spec.txt

[Tor Bug Tracker & Wiki]

#23924: Improve control-spec.txt
--+--
 Reporter:  tom   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_review
 Priority:  Very Low  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-control tor-spec  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by catalyst):

 * keywords:   => tor-control tor-spec
 * status:  new => needs_review
 * milestone:   => Tor: unspecified


Comment:

 Replying to [ticket:23924 tom]:
 > I was reading through control-spec.txt and made some commits I think
 would improve it: https://github.com/tomrittervg/torspec/commits/control-
 spec-editorial-1
 >
 >
 > (Do we have a torspec component? Couldn't find it if so...)
 I don't think so, but we do seem to use a tor-spec keyword.

--
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] #21951 [Applications/Tor Launcher]: Helping censored users bootstrap to Tor: Tor launcher improvements and automation (was: Helping censored users boostrap to Tor: Tor launcher improvem

[Tor Bug Tracker & Wiki]

#21951: Helping censored users bootstrap to Tor: Tor launcher improvements and
automation
---+--
 Reporter:  linda  |  Owner:  linda
 Type:  project| Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ux-team, TorBrowserTeam201710  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  Sponsor4
---+--

--
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] #23924 [Core Tor/Tor]: Improve control-spec.txt

[Tor Bug Tracker & Wiki]

#23924: Improve control-spec.txt
--+
 Reporter:  tom   |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Very Low  |  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 I was reading through control-spec.txt and made some commits I think would
 improve it: https://github.com/tomrittervg/torspec/commits/control-spec-
 editorial-1


 (Do we have a torspec component? Couldn't find it if so...)

--
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] #23915 [Applications/Tor Browser Sandbox]: 7.0.7 and later fails to work without `SECCOMP_FILTER_FLAG_TSYNC`.

[Tor Bug Tracker & Wiki]

#23915: 7.0.7 and later fails to work without `SECCOMP_FILTER_FLAG_TSYNC`.
--+-
 Reporter:  yawning   |  Owner:  yawning
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser Sandbox  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by arma):

 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] #23922 [Community/Tor Browser Manual]: The Uninstalling page does not mention the TorBrowser-Data directory on OSX

[Tor Bug Tracker & Wiki]

#23922: The Uninstalling page does not mention the TorBrowser-Data directory on 
OSX
--+--
 Reporter:  boklm |  Owner:  phoul
 Type:  defect| Status:  reopened
 Priority:  Medium|  Milestone:
Component:  Community/Tor Browser Manual  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by cypherpunks):

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


Comment:

 Oops, the ticket above is for `Webpages/Website` and not `Community/Tor
 Browser Manual`, really sorry for 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] #23922 [Community/Tor Browser Manual]: The Uninstalling page does not mention the TorBrowser-Data directory on OSX

[Tor Bug Tracker & Wiki]

#23922: The Uninstalling page does not mention the TorBrowser-Data directory on 
OSX
--+---
 Reporter:  boklm |  Owner:  phoul
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Community/Tor Browser Manual  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by cypherpunks):

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


Comment:

 It seems that this is a duplicate of #22611 (sorry if that's not the case)
 which already has a patch up for review by pastly.

--
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] #23923 [Core Tor/Tor]: Tor stops working with "Failed to find node for hop #1 of our path. Discarding this circuit."

[Tor Bug Tracker & Wiki]

#23923: Tor stops working with "Failed to find node for hop #1 of our path.
Discarding this circuit."
--+
 Reporter:  boklm |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by cypherpunks):

 Maybe related to #21969 and its child 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] #22261 [Metrics/Onionoo]: Remove the $ from family fingerprints

[Tor Bug Tracker & Wiki]

#22261: Remove the $ from family fingerprints
-+--
 Reporter:  teor |  Owner:  irl
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2017 |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 I have made Atlas not care if there are $ signs or not.

 
https://gitweb.torproject.org/atlas.git/commit/?id=8500dc6f34ad32b3c8fb7ef72a1a59e29de756f0

--
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] #23912 [Core Tor/Stem]: Add bastet to stem

[Tor Bug Tracker & Wiki]

#23912: Add bastet to stem
---+-
 Reporter:  tom|  Owner:  atagar
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:  implemented
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by atagar):

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


Comment:

 Perfect, thanks Tom! I checked with Stefani a few days ago and she asked
 for us to hold off on this addition (and by extension the DocTor checks)
 until after the switchover. Looks perfect to me - pushed.

--
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] #23923 [Core Tor/Tor]: Tor stops working with "Failed to find node for hop #1 of our path. Discarding this circuit."

[Tor Bug Tracker & Wiki]

#23923: Tor stops working with "Failed to find node for hop #1 of our path.
Discarding this circuit."
--+
 Reporter:  boklm |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 A user on the blog reported a problem with Tor 0.3.2.x, when using
 bridges:
 {{{
 [notice] Tor has not observed any network activity for the past 80
 seconds. Disabling circuit build timeout recording.
 [warn] Failed to find node for hop #1 of our path. Discarding this
 circuit.
 }}}

 https://blog.torproject.org/comment/271969#comment-271969

--
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] #23922 [Community/Tor Browser Manual]: The Uninstalling page does not mention the TorBrowser-Data directory on OSX

[Tor Bug Tracker & Wiki]

#23922: The Uninstalling page does not mention the TorBrowser-Data directory on 
OSX
--+---
 Reporter:  boklm |  Owner:  phoul
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Community/Tor Browser Manual  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by mcs):

 * cc: brade, mcs (added)


Comment:

 Good catch. We should also mention that if the Tor Browser application is
 in the Applications folder, the directory to remove is
 ~/Library/Application Support/TorBrowser-Data/

--
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] #23922 [Community/Tor Browser Manual]: The Uninstalling page does not mention the TorBrowser-Data directory on OSX

[Tor Bug Tracker & Wiki]

#23922: The Uninstalling page does not mention the TorBrowser-Data directory on 
OSX
--+---
 Reporter:  boklm |  Owner:  phoul
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Community/Tor Browser Manual  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+---
 On OSX, the Tor Browser profile is stored in the directory `TorBrowser-
 Data` next to the Tor Browser directory.

 The Uninstalling page in the manual is mentioning the Tor Browser
 directory, however it does not mention the `TorBrowser-Data` directory
 that some users might want to remove too.

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

Re: [tor-bugs] #23848 [Core Tor/Tor]: Replace all exit() calls with return code style

[Tor Bug Tracker & Wiki]

#23848: Replace all exit() calls with return code style
-+-
 Reporter:  hellais  |  Owner:  nickm
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-mobile,0.3.5-deferrable  |  Actual Points:
Parent ID:  #23684   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  accepted => needs_review


Comment:

 See branch `exit_carefully` in my public repository.

 This branch handles all but a few cases that I had marked as ` bad
 exit`.  I'm hoping to add tests, and also to open tickets for the
 remaining cases.

 (The remaining cases are all ones where IMO safe recovery is potentially
 difficult.  I also added some "" comments for cases where
 options_act() is behaving poorly, but IMO those are separate bugs.)

--
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] #23848 [Core Tor/Tor]: Replace all exit() calls with return code style

[Tor Bug Tracker & Wiki]

#23848: Replace all exit() calls with return code style
-+-
 Reporter:  hellais  |  Owner:  nickm
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-mobile,0.3.5-deferrable  |  Actual Points:
Parent ID:  #23684   | 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] #23799 [Internal Services/Service - git]: Please create git repository user/irl/metrics-bot (was: Please create git repository user/irl/atlasbot)

[Tor Bug Tracker & Wiki]

#23799: Please create git repository user/irl/metrics-bot
-+
 Reporter:  irl  |  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Description changed by irl:

Old description:

> Please create a git repository at user/irl/atlasbot to contain the
> sources for the Twitter bot powering @TorAtlas.
>
> I should have read/write access to this repository, everyone should have
> read access.
>

> {{{
> repo user/irl/atlasbot
> RW   = irl
> config gitweb.category   = "Users' development
> repositories"
> user/irl/atlasbot "Iain R. Learmonth" = "Atlasbot Sources"
> }}}
>
> (I don't do anywhere near enough gitolite for someone to not double check
> that before pasting it)

New description:

 Please create a git repository at user/irl/metrics-bot to contain the
 sources for the Twitter bot powering @TorAtlas.

 I should have read/write access to this repository, everyone should have
 read access.


 {{{
 repo user/irl/metrics-bot
 RW   = irl
 config gitweb.category   = "Users' development
 repositories"
 user/irl/metrics-bot "Iain R. Learmonth" = "metrics-bot Sources"
 }}}

 (I don't do anywhere near enough gitolite for someone to not double check
 that before pasting 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] #23921 [Applications/Tor Browser]: Video not working (Tab crashing OR mp4 decoder not found)

[Tor Bug Tracker & Wiki]

#23921: Video not working (Tab crashing OR mp4 decoder not found)
--+--
 Reporter:  sd3e2423ada   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  fixed
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by sd3e2423ada):

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


Comment:

 You are correct. Just got the 7.0.7 popup. Fixed. 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

Re: [tor-bugs] #23799 [Internal Services/Service - git]: Please create git repository user/irl/atlasbot

[Tor Bug Tracker & Wiki]

#23799: Please create git repository user/irl/atlasbot
-+
 Reporter:  irl  |  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by irl):

 * cc: karsten (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] #23920 [Applications/Tor Browser]: TB 7.0.2 xul.dll

[Tor Bug Tracker & Wiki]

#23920: TB 7.0.2 xul.dll
--+
 Reporter:  Ferro69   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  worksforme
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by gk):

 * status:  new => closed
 * severity:  Normal => Major
 * component:  - Select a component => Applications/Tor Browser
 * owner:  (none) => tbb-team
 * keywords:  xul.dll => tbb-crash
 * resolution:   => worksforme


Comment:

 There is no reason to be stuck with Tor Browser based on 52.2.0 if you are
 on Windows XP. Please update to the latest Tor Browser, 7.0.7, and reopen
 this bug if you still have these problems.

--
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] #23921 [Applications/Tor Browser]: Video not working (Tab crashing OR mp4 decoder not found)

[Tor Bug Tracker & Wiki]

#23921: Video not working (Tab crashing OR mp4 decoder not found)
--+---
 Reporter:  sd3e2423ada   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by gk):

 * status:  new => needs_information
 * severity:  Normal => Major
 * component:  - Select a component => Applications/Tor Browser
 * priority:  Medium => High
 * keywords:  video => tbb-crash
 * owner:  (none) => tbb-team


Comment:

 What do you mean with most recent version? See on `about:tor` the version
 number on the upper right corner. We released 7.0.7 yesterday and it
 should address your problem.

--
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] #21366 [Metrics/Onionoo]: Support whitespace in search term (as does Onionoo)

[Tor Bug Tracker & Wiki]

#21366: Support whitespace in search term (as does Onionoo)
-+--
 Reporter:  cypherpunks  |  Owner:  karsten
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2018 |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Replying to [comment:24 irl]:
 > If this is implemented in Onionoo, I guess no changes in Atlas are
 needed as long as there's no internal escaping going on that I haven't
 spotted?

 Right, and it looks like there's no such internal escaping going on. If I
 enter `contact:"John Doe"` into Atlas' search bar, I see a request to
 `https://onionoo.torproject.org/summary?search=contact:John
 Doe` going out. That request is a 400 so far, but that's what we
 would change on Onionoo's side. So, I'd say nothing to do on the Atlas
 side.

--
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] #23921 [- Select a component]: Video not working (Tab crashing OR mp4 decoder not found)

[Tor Bug Tracker & Wiki]

#23921: Video not working (Tab crashing OR mp4 decoder not found)
--+
 Reporter:  sd3e2423ada   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:  video |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by sd3e2423ada):

 Addition: running video in regular Firefox on the same machine
 (stable/nightly) works fine.

--
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] #23921 [- Select a component]: Video not working (Tab crashing OR mp4 decoder not found)

[Tor Bug Tracker & Wiki]

#23921: Video not working (Tab crashing OR mp4 decoder not found)
--+
 Reporter:  sd3e2423ada   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:  video |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by sd3e2423ada):

 One addition: running video in regular Firefox on the same machine
 (stable/nightly) works fine.

--
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] #23921 [- Select a component]: Video not working (Tab crashing OR mp4 decoder not found)

[Tor Bug Tracker & Wiki]

#23921: Video not working (Tab crashing OR mp4 decoder not found)
--+
 Reporter:  sd3e2423ada   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:  video
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 When opening YouTube and clicking on any video, the second the video would
 load the tab crashes with „Gah. Your tab just crashed.“. Click any other
 video on YouTube to recreate the same error.

 Using other video sites (tried numerous) the console log shows something
 like this: (what they all have in common is that the mp4 „could not be
 decoded“)

 ,,''load failed. video.php'',,

 ,,''All candidate resources failed to load. Media load paused.
 video.php'',,

 ,,'' element has no “src” attribute. Media resource load failed.
 video.php'',,

 ,,''All candidate resources failed to load. Media load paused.
 video.php'',,

 ,,'' element has no “src” attribute. Media resource load failed.
 video.php'',,

 ,,''All candidate resources failed to load. Media load paused.
 video.php'',,

 ,,'' element has no “src” attribute. Media resource load failed.
 video.php'',,

 ,,''All candidate resources failed to load. Media load paused.
 video.php'',,

 ,,''Media resource https://xyz.com/file.mp4 could not be decoded.'',,

 ,,''All candidate resources failed to load. Media load paused.
 video.php'',,

 ,,''Media resource https://xyz.com/file.mp4 could not be decoded. '',,

 ,,''video.php All candidate resources failed to load. Media load pause'',,

 Running most recent (stable) TorBrowser + MacOS 10.13. Nothing changed in
 about:config or regarding extensions. This appeared first two months ago
 with a stable TorBrowser version. Tried updating the stable version since
 then + nightly builds without any success of watching video with
 !TorBrowser.

--
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] #21366 [Metrics/Onionoo]: Support whitespace in search term (as does Onionoo)

[Tor Bug Tracker & Wiki]

#21366: Support whitespace in search term (as does Onionoo)
-+--
 Reporter:  cypherpunks  |  Owner:  karsten
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2018 |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 If this is implemented in Onionoo, I guess no changes in Atlas are needed
 as long as there's no internal escaping going on that I haven't spotted?

--
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] #23713 [Metrics/Onionoo]: Add as_name parameter

[Tor Bug Tracker & Wiki]

#23713: Add as_name parameter
-+--
 Reporter:  cypherpunks  |  Owner:  karsten
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 I think as and as_name are both fine, the _number does look redundant to
 me.

 nusenu: I would encourage you though, to consider making the URLs link to
 as:X as this would be a more accurate search, especially as AS names would
 have to be a partial string search to be useful to end users. e.g. I might
 search for OVH instead of "OVH SAS". Exact string searches would only be
 useful to applications that probably have the AS number already.

--
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] #23713 [Metrics/Onionoo]: Add as_name parameter

[Tor Bug Tracker & Wiki]

#23713: Add as_name parameter
-+--
 Reporter:  cypherpunks  |  Owner:  karsten
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * status:  new => accepted
 * owner:  metrics-team => karsten


Comment:

 Sounds useful to me. We should probably implement #21366 first to fully
 support AS names containing spaces. But other than that I don't see any
 major problems.

 For the sake of consistency between field names and parameter names we
 might consider renaming the "as_number" ''field'' to just "as". That's
 also more consistent with "country" for the country code and
 "country_name" for the country name. This change would require a major
 version bump, but in this case we could easily include both fields for a
 few months until clients are updated. So, adding an "as" field would be
 the minor protocol change and removing the "as_number" field would be the
 major protocol change. Or maybe the latter would also be a minor change,
 because the field is optional. Anyway, something to consider and somewhat
 related to this feature request.

--
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] #21637 [Metrics/Onionoo]: Include both declared and reachable IPv6 OR addresses

[Tor Bug Tracker & Wiki]

#21637: Include both declared and reachable IPv6 OR addresses
+--
 Reporter:  teor|  Owner:  metrics-team
 Type:  enhancement | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Metrics/Onionoo |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2017, ipv6  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by karsten):

 Replying to [comment:14 Sebastian]:
 > Can someone please summarize this "only some dirauths vote running"
 stuff and send it to the dirauth list? That seems super broken and we
 really should get all dirauths on the same page wrt ipv6

 Sure, I'll send my findings to that list, and teor can follow up as
 needed. (I thought that all of this is already known information. Maybe it
 is, we'll find out.)

--
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] #23829 [Metrics/Onionoo]: Add support for search term negation

[Tor Bug Tracker & Wiki]

#23829: Add support for search term negation
-+--
 Reporter:  cypherpunks  |  Owner:  karsten
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Replying to [comment:7 cypherpunks]:
 > I is probably not valuable to implement negation for unqualified search
 terms, but I
 > still would see a use case in being able to say "not in IP block
 a.b.(c.)" - which implies that we might want a new `ip` url parameter?

 Yes, or maybe "address" to be more consistent with the field names
 "or_addresses", "exit_addresses", and "dir_address".

 We should also consider adding a "nickname" parameter.

 And we should extend the "fingerprint" parameter to provide the same
 functionality as passing a fingerprint or fingerprint part to the "search"
 parameter. At the same time, or shortly after, we can deprecate the
 "lookup" parameter. That latter part requires a major protocol version
 bump, the other parts do not.

 Do you mind opening tickets for these if you agree that these would be
 useful to have? Happy to discuss these new/changed parameters more, but
 preferably on new tickets.

 Agreeing with the rest, this ticket is ready for implementation.

--
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] #21637 [Metrics/Onionoo]: Include both declared and reachable IPv6 OR addresses

[Tor Bug Tracker & Wiki]

#21637: Include both declared and reachable IPv6 OR addresses
+--
 Reporter:  teor|  Owner:  metrics-team
 Type:  enhancement | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Metrics/Onionoo |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2017, ipv6  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by Sebastian):

 Can someone please summarize this "only some dirauths vote running" stuff
 and send it to the dirauth list? That seems super broken and we really
 should get all dirauths on the same page wrt ipv6

--
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] #21637 [Metrics/Onionoo]: Include both declared and reachable IPv6 OR addresses

[Tor Bug Tracker & Wiki]

#21637: Include both declared and reachable IPv6 OR addresses
+--
 Reporter:  teor|  Owner:  metrics-team
 Type:  enhancement | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Metrics/Onionoo |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2017, ipv6  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by karsten):

 Replying to [comment:12 teor]:
 > Replying to [comment:10 karsten]:
 > > Replying to [comment:9 teor]:
 > > > This is how things will work when authorities upgrade to 0.3.3,
 assuming we merge the IPv6 fixes in #20916.
 > >
 > > Hmm, can you elaborate how either the upgrade or the bugfix will
 affect us here?
 >
 > Authorities will vote Running for relays with unreachable IPv6
 addresses, but drop the unreachable address from the vote.
 > At the moment, they vote not Running, and drop the entire relay from the
 consensus.

 It took me a while to figure out why I'm seeing relays with unreachable
 IPv6 address and the Running flag in the consensus. Turns out that only
 tor26 and gabelmoo check whether an IPv6 address is reachable and hence
 remove the Running flag from relays in their vote. But given that all the
 other authorities don't perform this check and assign the Running flag to
 relays, they end up in the consensus as Running. And #20916 will fix the
 part about votes not containing the Running flag for these relays? If so,
 okay. This shouldn't block deploying this Onionoo feature, though.

 I also found a minor bug in my branch and pushed a fixup commit.

 I'd say that
 [https://gitweb.torproject.org/user/karsten/onionoo.git/log/?h=task-21637
 my updated task-21637 branch] is ready for code review 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] #23780 [Obfuscation/Snowflake]: Tor repeatedly tells me that "Your Guard is failing an extremely large amount of circuits" when using snowflake

[Tor Bug Tracker & Wiki]

#23780: Tor repeatedly tells me that "Your Guard is failing an extremely large
amount of circuits" when using snowflake
---+
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:  Tor: 0.3.2.2-alpha
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by cypherpunks):

 * version:  Tor: 0.3.2.1-alpha => Tor: 0.3.2.2-alpha


--
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] #23920 [- Select a component]: TB 7.0.2 xul.dll

[Tor Bug Tracker & Wiki]

#23920: TB 7.0.2 xul.dll
--+-
 Reporter:  Ferro69   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:  xul.dll
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 Hi

 Sometimes, TB (based on Mozilla Firefox 52.2.0. 32 bits) crashes very
 often and always because of xul.dll
 I cant' update it because I'm on winXP and want to keep it.
 Any idea ?

 PS: don't have the logs 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] #23716 [Metrics/Website]: Rename Operation section to Services

[Tor Bug Tracker & Wiki]

#23716: Rename Operation section to Services
-+---
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by irl):

 Yes, essentially that was what I was thinking, I only raised it now as it
 may have influenced our choice of the new name for Operation.

 The changes lgtm. I do think it's a good idea to have the roadmap and the
 website agree before the roadmap is put out.

--
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] #23838 [Applications/Tor Browser]: Use OONI to inform Tor Launcher user workflow

[Tor Bug Tracker & Wiki]

#23838: Use OONI to inform Tor Launcher user workflow
--+--
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by hellais):

 We started working on this as part of the following branch on ooni-
 pipeline: https://github.com/TheTorProject/ooni-pipeline/pull/98.

--
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] #23829 [Metrics/Onionoo]: Add support for search term negation

[Tor Bug Tracker & Wiki]

#23829: Add support for search term negation
-+--
 Reporter:  cypherpunks  |  Owner:  karsten
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by cypherpunks):

 > Ah! Well, you're right that nicknames and IPs are mutually exclusive.
 But other unqualified search terms are not. For example, `` could be
 the beginning of a hex-encoded fingerprint, any 4 hex character block in
 the middle of a space-separated fingerprint, the beginning of a
 base64-encoded fingerprint, the beginning of an IPv6 address, the
 beginning of a nickname, and maybe even something else I didn't think of
 right now. It would probably be very confusing to look at the results of
 `search=!` and guess which relays were excluded and why. Hmm.

 the unqualified search term can be:
 - nickname
 - fingerprint
 - base64 fingerprint
 - IP address
 - hashed fingerprint

 I is probably not valuable to implement negation for unqualified search
 terms, but I
 still would see a use case in being able to say "not in IP block a.b.(c.)"
 - which implies that we might want a new 'ip' url parameter?

 >> All use-cases can be formed with the ! sign being used in the value
 part only, right?
 > Yes.

 Ok than it is less confusing to accept `!` in the value part only.

 > I'm inclined to take back the suggestion to negate search terms. If we
 limit negation to parameters like "flag", "as", and so on, that might be
 more intuitive. And we could always extend it to the "search" parameter
 later on in a backward-compatible if we change our minds. But I think we
 should start without the "search" parameter, except for values of
 qualified search terms, of course.

 Agreed.

 > Alright, I think I can work with this and write some more code. That
 won't happen today, but I'll try to do this next week.

 thank you!

--
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] #23918 [Applications/Tor Browser]: tor button and tor browser home page says "not connected to network"

[Tor Bug Tracker & Wiki]

#23918: tor button and tor browser home page says "not connected to network"
--+---
 Reporter:  tortracfree   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-torbutton |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by tortracfree):

 Replying to [comment:3 gk]:
 > Could you add additional logs in case this happens again?
 Do you mean right now or when it happens again?

--
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] #23918 [Applications/Tor Browser]: tor button and tor browser home page says "not connected to network"

[Tor Bug Tracker & Wiki]

#23918: tor button and tor browser home page says "not connected to network"
--+---
 Reporter:  tortracfree   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-torbutton |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by gk):

 Could you add additional logs in case this happens again?

--
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] #23919 [Applications/Tor Browser Sandbox]: Pull in the Tor Browser MAR signing key.

[Tor Bug Tracker & Wiki]

#23919: Pull in the Tor Browser MAR signing key.
--+-
 Reporter:  yawning   |  Owner:  yawning
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser Sandbox  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 It looks like the browser developers are wanting to rotate the MAR signing
 key again (#23916).

 The sandbox maintains internal hard codes copies of these as it
 independently verifies update signatures, and thus needs to pull in the
 new key when it is 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] #23918 [Applications/Tor Browser]: tor button and tor browser home page says "not connected to network"

[Tor Bug Tracker & Wiki]

#23918: tor button and tor browser home page says "not connected to network"
--+---
 Reporter:  tortracfree   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-torbutton |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by tortracfree):

 Replying to [comment:1 gk]:
 > Hm. Does this happen on every Tor Browser start?

 It happens only time to time for the last 2 weeks appxoximatly

--
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] #23716 [Metrics/Website]: Rename Operation section to Services

[Tor Bug Tracker & Wiki]

#23716: Rename Operation section to Services
-+---
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by karsten):

 Thanks, linda, for your feedback! I agree with your conclusion that we
 should try renaming to "Services".

 irl, let's talk more about your suggestion regarding "swapping out the
 secondary-nav depending on the section at the top of the page and adding
 an Analysis section for the things currently on the home page." Do you
 mean adding "Analysis" as new first category next to "News", with "Users",
 "Servers", etc. as subitems under "Analysis" and a separate (possibly
 empty) set of subitems under "News", "Sources", etc.? Happy to talk about
 that, but let's move to a new ticket, as it's somewhat unrelated to the
 renaming question here. Note that we'll likely want to talk to a/our web
 designer and that we might want to wait and see what the main Tor website
 redesign produces.

 So, regarding the renaming question, I suggest that we:
  - rename Operations to Services on the website,
  - keep the cogs icon,
  - move operation.html to services.html, and
  - put a manual redirect page on operation.html.

 Anything else? Should we do it, like, in the next few days before we put
 out our roadmap which uses these categories, too?

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

Re: [tor-bugs] #20773 [Applications/Tor Browser Sandbox]: Stop mounting `/proc` in the various containers once this is feasable.

[Tor Bug Tracker & Wiki]

#20773: Stop mounting `/proc` in the various containers once this is feasable.
--+-
 Reporter:  yawning   |  Owner:  yawning
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser Sandbox  |Version:
 Severity:  Normal| Resolution:
 Keywords:  sandbox-security  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by yawning):

 #23915 is more fallout from this, that needs to be accounted for in the
 future.

--
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] #23915 [Applications/Tor Browser Sandbox]: 7.0.7 and later fails to work without `SECCOMP_FILTER_FLAG_TSYNC`.

[Tor Bug Tracker & Wiki]

#23915: 7.0.7 and later fails to work without `SECCOMP_FILTER_FLAG_TSYNC`.
--+-
 Reporter:  yawning   |  Owner:  yawning
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser Sandbox  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by yawning):

 In an ideal world the workaround here will be selectively enabled base on
 support for `SECCOMP_FILTER_FLAG_TSYNC`.  I am opting to defer doing the
 "better" thing for now because:

  * Solving the "bad" case completely is likely intractable on old kernels,
 without going back to having `/proc` mounted.

  * Firefox detects support for the flag at runtime, and will always use it
 when available, so the "correct" thing happens regardless of what I do.

  * I'm feeling lazy.

--
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] #23918 [Applications/Tor Browser]: tor button and tor browser home page says "not connected to network"

[Tor Bug Tracker & Wiki]

#23918: tor button and tor browser home page says "not connected to network"
--+---
 Reporter:  tortracfree   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-torbutton |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by gk):

 * owner:  (none) => tbb-team
 * status:  new => needs_information
 * component:  - Select a component => Applications/Tor Browser
 * keywords:   => tbb-torbutton


Comment:

 Hm. Does this happen on every Tor Browser start?

--
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] #23442 [Applications/Tor Browser]: Error building firefox for Windows 64 in security/pkix/lib/pkixnames.cpp

[Tor Bug Tracker & Wiki]

#23442: Error building firefox for Windows 64 in security/pkix/lib/pkixnames.cpp
--+--
 Reporter:  boklm |  Owner:  tbb-team
 Type:  task  | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  TorBrowserTeam201710R |  Actual Points:
Parent ID:  #23229| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

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


Comment:

 Cherry-picked onto `tor-browser-52.4.1.esr-7.5-1` (commit
 e6cd07862cf0de06b9cc7c091f9d2dd32cd76280), 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

[tor-bugs] #23918 [- Select a component]: tor button and tor browser home page says "not connected to network"

[Tor Bug Tracker & Wiki]

#23918: tor button and tor browser home page says "not connected to network"
--+
 Reporter:  tortracfree   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Hello,

 When starting tor browser, the browser home page displays onion crossed
 red saying that there was a problem and that I a not connected to tor
 network. Tor button also displays onion crossed red. However when visiting
 tor check page, it says that I am connected to tor network.

 is it a bug?

 thanks


 tor logs :

 20/10/2017 07:51:46.900 [NOTICE] Bootstrapped 90%: Establishing a Tor
 circuit
 20/10/2017 07:51:48.700 [NOTICE] Tor has successfully opened a circuit.
 Looks like client functionality is working.
 20/10/2017 07:51:48.700 [NOTICE] Bootstrapped 100%: Done
 20/10/2017 07:52:02.100 [NOTICE] New control connection opened from
 127.0.0.1.
 20/10/2017 07:52:02.100 [NOTICE] New control connection opened from
 127.0.0.1.
 20/10/2017 08:06:03.000 [NOTICE] Our IP address has changed.  Rotating
 keys...

--
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] #23917 [Webpages/Website]: Update signing keys for gk on website

[Tor Bug Tracker & Wiki]

#23917: Update signing keys for gk on website
--+--
 Reporter:  gk|  Owner:  hiro
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * status:  assigned => 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] #23917 [Webpages/Website]: Update signing keys for gk on website

[Tor Bug Tracker & Wiki]

#23917: Update signing keys for gk on website
--+--
 Reporter:  gk|  Owner:  hiro
 Type:  enhancement   | Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * status:  needs_review => assigned
 * owner:  (none) => hiro


--
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] #23917 [Webpages/Website]: Update signing keys for gk on website

[Tor Bug Tracker & Wiki]

#23917: Update signing keys for gk on website
--+--
 Reporter:  gk|  Owner:  (none)
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * status:  new => needs_review


Comment:

 `bug_23917`
 
(https://gitweb.torproject.org/user/gk/webwml.git/commit/?h=bug_23917=db7742fb1fd89a07e86d2cb3f67bb86b74bfb18f)
 in my public `webwml` repo has the patch for 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

[tor-bugs] #23917 [Webpages/Website]: Update signing keys for gk on website

[Tor Bug Tracker & Wiki]

#23917: Update signing keys for gk on website
--+
 Reporter:  gk|  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 I created new sub keys a while ago. We should update the website with
 them.

--
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] #23916 [Applications/Tor Browser]: Create a new MAR signing key for Tor Browser

[Tor Bug Tracker & Wiki]

#23916: Create a new MAR signing key for Tor Browser
-+-
 Reporter:  gk   |  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  TorBrowserTeam201711,
 Severity:  Normal   |  GeorgKoppen201711
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Similar to #20589 we want to have a new signing key for our MAR files and
 bake it into Tor Browser so we can rotate the keys later on.

--
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] #23915 [Applications/Tor Browser Sandbox]: 7.0.7 and later fails to work without `SECCOMP_FILTER_FLAG_TSYNC`.

[Tor Bug Tracker & Wiki]

#23915: 7.0.7 and later fails to work without `SECCOMP_FILTER_FLAG_TSYNC`.
--+-
 Reporter:  yawning   |  Owner:  yawning
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser Sandbox  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by yawning):

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


Comment:

 https://gitweb.torproject.org/tor-browser/sandboxed-tor-
 browser.git/commit/?id=6a43d8fd4765f0e795d281c9ac328b853f0cef4c

--
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] #10394 [Applications/Tor Browser]: Torbrowser's updater updates HTTPS-everywhere

[Tor Bug Tracker & Wiki]

#10394: Torbrowser's updater updates HTTPS-everywhere
--+--
 Reporter:  StrangeCharm  |  Owner:  tbb-team
 Type:  task  | Status:  reopened
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-security  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 +1, as #23772.

--
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] #23915 [Applications/Tor Browser Sandbox]: 7.0.7 and later fails to work without `SECCOMP_FILTER_FLAG_TSYNC`.

[Tor Bug Tracker & Wiki]

#23915: 7.0.7 and later fails to work without `SECCOMP_FILTER_FLAG_TSYNC`.
--+-
 Reporter:  yawning   |  Owner:  yawning
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser Sandbox  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 {{{
 2017/10/20 03:16:42 firefox: Sandbox: opendir /proc/self/task: No such
 file or directory
 2017/10/20 03:16:42 firefox: [Parent 3] WARNING: pipe error (59):
 Connection reset by peer: file /home/debian/build/tor-
 browser/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 322
 2017/10/20 03:16:42 firefox: [Parent 3] WARNING: pipe error (57):
 Connection reset by peer: file /home/debian/build/tor-
 browser/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 322
 2017/10/20 03:16:42 firefox: ###!!! [Parent][RunMessage] Error: Channel
 error: cannot send/recv
 2017/10/20 03:16:42 firefox: ###!!! [Parent][MessageChannel] Error:
 (msgtype=0x2C0086,name=PBrowser::Msg_Destroy) Channel error: cannot
 send/recv
 }}}

 This only affects systems running kernels that pre-date 3.17, which
 annoyingly enough currently includes Debian oldstable.  It's an artifact
 of "the sandbox doesn't mount `/proc`", and "firefox wants to use
 `/proc/self/task` to see if a process has threads or not".  The need for
 the latter goes away with the `seccomp()` flag, which is why I never saw
 the 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

Re: [tor-bugs] #23913 [Metrics/Onionoo]: Allow parameters and qualified search terms to be specified more than once

[Tor Bug Tracker & Wiki]

#23913: Allow parameters and qualified search terms to be specified more than 
once
-+--
 Reporter:  nusenu   |  Owner:  karsten
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * status:  new => accepted
 * owner:  metrics-team => karsten


Comment:

 Sounds 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] #21366 [Metrics/Onionoo]: Support whitespace in search term (as does Onionoo)

[Tor Bug Tracker & Wiki]

#21366: Support whitespace in search term (as does Onionoo)
-+--
 Reporter:  cypherpunks  |  Owner:  karsten
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2018 |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Replying to [comment:21 nusenu]:
 > Thank you Karsten for your comprehensive summary!
 >
 > >  1. Allow parameters and qualified search terms to be specified more
 than once. [...]  Let's move this to a new ticket
 >
 > I created #23913 now.

 Thanks!

 > > 2. [...] We might document this change by saying: "Qualified search
 terms have the form 'key:value' or 'key:"value"' (both without surrounding
 single quotes) with "key" being one of the parameters [...]". I'm inclined
 to say that this requires just a minor protocol version bump, because
 we're currently returning a 400 status code for this newly introduced
 syntax. Let me know what you think!
 >
 > I agree that this does not need a major version bump - because it is
 unlikely to break existing use-cases. How should users escape the quote
 sign? (\")

 Ah, good question about escaping. Yes, I think `\"` would be good as
 escaped quote sign. The current branch does not support that yet, but that
 shouldn't be too hard to implement. (Famous last words?...)

 > >  4. Add an extended search form to Atlas with inputs for other
 parameters than Onionoo's search parameter.
 >
 > I made a ticket for that not all to long ago: #23782
 >
 > I agree that this is a documentation issue but the search form would
 make the power of atlas/onionoo more accessible, visible and usable to a
 broader audience.
 >
 > >  5. Extend Onionoo's search parameter to also look at contact line
 parts when processing unqualified search terms. That would mean not only
 looking at nicknames, fingerprints, IP addresses, etc., but also at
 contact line parts. I'm opposed to that idea.
 >
 > I'm opposing as well.
 >
 > > So, my suggestion is to create a new ticket for 1, get 2 reviewed and
 merged, and possibly create another ticket for 4. Thoughts?
 >
 > Looking forward to that new feature! :)

 Great! I'll have to do other things first today, but I hope that I can
 write some more Onionoo code next week.

--
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] #23914 [Metrics/Onionoo]: Extend flag parameter to support comma-separated list of flags

[Tor Bug Tracker & Wiki]

#23914: Extend flag parameter to support comma-separated list of flags
-+--
 Reporter:  nusenu   |  Owner:  karsten
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * owner:  metrics-team => karsten
 * status:  new => accepted


Comment:

 Sounds good to me. We might consider doing #23913 to support queries like
 `search=flag:exit flag:guard` rather than `search=flag:exit,guard`. But we
 might also support both. I don't feel strongly, even though that might
 change when I start implementing this. Let's see.

--
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] #23829 [Metrics/Onionoo]: Add support for search term negation

[Tor Bug Tracker & Wiki]

#23829: Add support for search term negation
-+--
 Reporter:  cypherpunks  |  Owner:  karsten
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * owner:  metrics-team => karsten
 * status:  needs_review => 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] #23829 [Metrics/Onionoo]: Add support for search term negation

[Tor Bug Tracker & Wiki]

#23829: Add support for search term negation
-+--
 Reporter:  cypherpunks  |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Replying to [comment:4 nusenu]:
 > Replying to [comment:3 karsten]:
 > > Mind opening one if you think that would be a useful feature?
 >
 > #23914

 Thanks!

 > > Regarding the other parameters that you suggest that should support
 negation, that list sounds reasonable. What it does not mention is the
 "search" parameter itself, which means unqualified search terms for which
 you give use cases further down below.
 >
 > Since I realized that nickname and IP are mutually exclusive (nickname
 can not contain dots, IPs can not contain chars) it makes sense to add
 them as well even without specific IP: nickname: parameters.

 Ah! Well, you're right that nicknames and IPs are mutually exclusive. But
 other unqualified search terms are not. For example, `` could be the
 beginning of a hex-encoded fingerprint, any 4 hex character block in the
 middle of a space-separated fingerprint, the beginning of a base64-encoded
 fingerprint, the beginning of an IPv6 address, the beginning of a
 nickname, and maybe even something else I didn't think of right now. It
 would probably be very confusing to look at the results of `search=!`
 and guess which relays were excluded and why. Hmm.

 > > Before I go write more code, can you answer the following usability
 questions (numbered for easier reference, not to indicate priority)?
 > >  1. Is `!` the best character we can find to indicate negation? Or
 should we instead pick `-`? Or something else?
 >
 > `!` is IMHO the most intuitive and most common character for this use-
 case. This would be my first try before reading any documentation.

 Sounds good. I'll leave this question open here for a few more days to
 hear if somebody strongly disagrees. Otherwise it's going to be `!`.

 > >  2. We'll have to extend the various parameters to support `!` as part
 of the parameter value as in `search=flag:!exit`, and we'll have to allow
 unqualified search terms starting with `!` as in `search=!default`. But
 should we also allow qualified search terms starting with `!` as in
 `search=!flag:exit` which would be equivalent to `search=flag:!exit`? Note
 that if we do, `search=!flag:!exit` would be a valid parameter, as would
 `search=!flag:exit,guard` or `search=!flag:!exit,guard` if we extend the
 "flag" parameter as mentioned in my first paragraph. It would be up to the
 user to interpret what that might possibly mean. But maybe they're to
 blame if they write such a complex query rather than us for accepting it.
 ;)
 >
 > All use-cases can be formed with the `!` sign being used in the value
 part only, right?

 Yes.

 > `!flag:!guard,exit == flag:guard,!exit` ?

 Unfortunately, no:

 `NOT (NOT guard AND exit) == guard OR NOT exit != guard AND NOT exit`

 I'm inclined to take back the suggestion to negate search terms. If we
 limit negation to parameters like "flag", "as", and so on, that might be
 more intuitive. And we could always extend it to the "search" parameter
 later on in a backward-compatible if we change our minds. But I think we
 should start without the "search" parameter, except for values of
 qualified search terms, of course.

 Alright, I think I can work with this and write some more code. That won't
 happen today, but I'll try to do this next week.

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