Re: [tor-bugs] #23831 [Metrics/Website]: Provide a Vagrantfile that is able get a development environment up and running

[Tor Bug Tracker & Wiki]

#23831: Provide a Vagrantfile that is able get a development environment up and
running
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  task | Status:  closed
 Priority:  Low  |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 If the setup process is easy, then the Vagrantfile would likely be
 redundant, I agree. This is OK.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23831 [Metrics/Website]: Provide a Vagrantfile that is able get a development environment up and running

[Tor Bug Tracker & Wiki]

#23831: Provide a Vagrantfile that is able get a development environment up and
running
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  task | Status:  closed
 Priority:  Low  |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

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


Comment:

 In the long run we have the plan to make metrics-web more manageable as
 for example Onionoo or CollecTor, i.e. with its own embedded jetty and no
 scripts etc. (there are several tickets about that).
 The setup process should be designed in order to be easy and complexities
 should rather be untangled instead of hidden away by providing a setup
 image or the like.

 Thus, providing a vagrant file or similar are not in scope currently.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23830 [Metrics/Website]: Update README to get a development environment for metrics-web going

[Tor Bug Tracker & Wiki]

#23830: Update README to get a development environment for metrics-web going
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 The packages might refer to older debian names or contain typos and need
 an update, that's true.

 Please post more of your findings or questions.

 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] #23830 [Metrics/Website]: Update README to get a development environment for metrics-web going (was: Update README to get a development environment for metrics-lib going)

[Tor Bug Tracker & Wiki]

#23830: Update README to get a development environment for metrics-web going
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * type:  task => enhancement


Comment:

 Corrected title.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23822 [Core Tor/Tor]: tor router not working

[Tor Bug Tracker & Wiki]

#23822: tor router not working
--+---
 Reporter:  y.net |  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.2.5.12
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by teor):

 * keywords:  not working =>
 * priority:  High => Medium
 * status:  reopened => needs_information
 * type:  project => defect
 * milestone:  Tor: 0.2.5.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] #23822 [Core Tor/Tor]: tor router not working

[Tor Bug Tracker & Wiki]

#23822: tor router not working
--+
 Reporter:  y.net |  Owner:  (none)
 Type:  project   | Status:  reopened
 Priority:  High  |  Milestone:  Tor: 0.2.5.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.2.5.12
 Severity:  Normal| Resolution:
 Keywords:  not working   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by teor):

 You might have a version of OpenSSL that is too old or incompatible with
 your tor version.

 Your version of tor is very old, and does not log enough information for
 us to know the SSL library version.

 Please upgrade to Tor 0.2.9 or later, and launch tor 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] #23832 [Internal Services/Tor Sysadmin Team]: Please make ldap account for kat

[Tor Bug Tracker & Wiki]

#23832: Please make ldap account for kat
-+-
 Reporter:  arma |  Owner:  tpa
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 {{{
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256


 Kat has been helping with community coordination and relay operators.
 Today she volunteered to help with webwml fixes. We should give her an
 ldap account so she can follow through on this offer (plus all the other
 great things she does and will do :).

 First name: Kat
 Last name: Hanna
 Desired uid: kat
 Forwarding address: k...@sigstop.org

 $ gpg --fingerprint 9B75D16D879517DA
 pub   4096R/9B75D16D879517DA 2017-09-04
   Key fingerprint = 1AF8 EC77 B4B2 A3A5 A48B  4887 9B75 D16D 8795 17DA
 uid  Kat at sigstop 
 sub   4096R/6B5AF58FD5011A42 2017-09-04

 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1

 iQIcBAEBCAAGBQJZ3tDsAAoJEMIYUlgZ94RRyRkP/ji0eby/G2cA+y5zrfQY88C4
 J+jbOqVXRQOB75WPRm6Sl2CkMitQpZyp7aLP7zGBxSpIGi8BEMB0whq/br/uKfmV
 e+wSI/VbHU5CvsUkts2X5Lxdi8wnLCpmCKcZPiKUw9yMhDFMK6XkTwfGbQqPmLYH
 HllpNnHmmF+cCJlnuDmIlN10CgCCEe+3Vk6bhLCgGBcl0FwkfcTMuorU7YHt2/q+
 ohiegGiJQPNULQKB0mFXicWnS93s24gSBeeqfWF5vTyGoE37mgOfUwEncD1GKq9g
 FYuACAnKgSaq7cj2czSkgFhN98G2mqxHysEE6rZxHa4yfdl7yot5d03JKPcKNu1j
 LSSmzw8n9Z3rsm0fMeKVr3jt9/ygdb7C/PtFma7IEG/1jpzdGSN8D6aakf3+yuWH
 r3sLwBCOmFR7dboDZrjX4EWsKvy1ESB/+TPLvlnKkq5vd7e7waHAE0i3VlcSN/9t
 sAPRiVWhEI4TFkWF5/LK4YOXUrWvNhk+eVe69plW/wL9lcgpBcbGRcc2Ka/0gjIx
 i2ZwTPHHGseybjQmaMZY14ma/DWiUvT3nuSOM/5PWUKVxHVdG8D7x4RP3lg9Fm0E
 i5ZLXUQ3lEARYOFu2SDYHGnUmbx4fsw+xQwkZRfxi5csjGdB4hrRP6nQVZ4Vyc2r
 chlePCZ7WNXzHD9JlUeV
 =qsHM
 -END PGP SIGNATURE-
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23831 [Metrics/Website]: Provide a Vagrantfile that is able get a development environment up and running

[Tor Bug Tracker & Wiki]

#23831: Provide a Vagrantfile that is able get a development environment up and
running
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  task | Status:  new
 Priority:  Low  |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by irl):

 * type:  defect => task


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23831 [Metrics/Website]: Provide a Vagrantfile that is able get a development environment up and running

[Tor Bug Tracker & Wiki]

#23831: Provide a Vagrantfile that is able get a development environment up and
running
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  defect   | Status:  new
 Priority:  Low  |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 It would be awesome to be able to just run "vagrant up" to get a metrics-
 web development environment running. A shell script, Ansible playbook or
 Saltstack would all be good options for provisioning the environment.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23830 [Metrics/Website]: Update README to get a development environment for metrics-lib going

[Tor Bug Tracker & Wiki]

#23830: Update README to get a development environment for metrics-lib going
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 Attempting to set up a development environment for metrics-web is not
 easy.

 There is a reference to Debian packages that don't appear to exist, for
 example I think r-cran-java should be r-cran-rjava maybe?

 It would be good to have a knowledgable person go over the whole thing and
 double check 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] #23822 [Core Tor/Tor]: tor router not working

[Tor Bug Tracker & Wiki]

#23822: tor router not working
--+
 Reporter:  y.net |  Owner:  (none)
 Type:  project   | Status:  reopened
 Priority:  High  |  Milestone:  Tor: 0.2.5.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.2.5.12
 Severity:  Normal| Resolution:
 Keywords:  not working   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by y.net):

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


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

Re: [tor-bugs] #23822 [Core Tor/Tor]: tor router not working

[Tor Bug Tracker & Wiki]

#23822: tor router not working
--+
 Reporter:  y.net |  Owner:  (none)
 Type:  project   | Status:  closed
 Priority:  High  |  Milestone:  Tor: 0.2.5.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.2.5.12
 Severity:  Normal| Resolution:  not a bug
 Keywords:  not working   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by y.net):

 Replying to [comment:2 teor]:


 > You have multiple instances of tor running, or your OS keeps ports for a
 long time after they're used. Try restarting the OS.
 >
 > And please post a notice-level log next time, it contains all the
 information we need.
 > The debug log is too long, and doesn't contain any relevant failures.
 >
 >
 > it's the same problem after restarting OS
 > the notices log is uploded

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23822 [Core Tor/Tor]: tor router not working

[Tor Bug Tracker & Wiki]

#23822: tor router not working
--+
 Reporter:  y.net |  Owner:  (none)
 Type:  project   | Status:  closed
 Priority:  High  |  Milestone:  Tor: 0.2.5.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.2.5.12
 Severity:  Normal| Resolution:  not a bug
 Keywords:  not working   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by y.net):

 * Attachment "notices.log" added.

 notices log

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23819 [Core Tor/Tor]: Support IPv6 link-local interface addresses

[Tor Bug Tracker & Wiki]

#23819: Support IPv6 link-local interface addresses
-+--
 Reporter:  Zakhar   |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor |Version:  Tor: unspecified
 Severity:  Normal   | Resolution:
 Keywords:  ipv6 link-local  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by Zakhar):

 Sorry I can confirm it is a '''BUG'''.

 
 ''Function names and lines below from the source downloaded from repo:''
 `apt-get source tor` ''(Running Ubuntu 16.04x64)''
 ---


 The bug happens in the '''file''': `src/common/address.c`

 '''function''': `tor_addr_lookup()` [line 239]

 From there we go down `#ifdef HAVE_GETADDRINFO`

 ...since we are in Linux an we have that function.

 [line 273] getaddrinfo (in fact sandbox_getaddrinfo) correctly parses the
 ipv6 address''' including the additional interface''' with the standard
 notation.

 As you can see in this StackOverflow report:
 https://stackoverflow.com/questions/2455762/why-cant-i-bind-ipv6-socket-
 to-a-linklocal-address

 The field: `sin6_scope_id` of the struct sockaddr_in6 is correctly filled
 with this call.

 In my case (debugged through nemiver), it happens this 32bits value is 3.

 After that, the function is happy to have gotten an ipv6 address and calls
 `tor_addr_from_in6` [line 298]... which '''(BUG)''' saves only the 16 bits
 of the ipv6 address and '''completely drops the field `sin6_scope_id` from
 the sockaddr structure'''.

 Since the structure returned by getaddrinfo is correctly freed at [line
 302] by freeaddrinfo, we have now lost this essential `sin6_scope_id`!

 A little bit later during the initialisation process, we will try to bind
 what we have read from the configuration file.

 That happens in the file: `src/or/connection.c` in the function
 `connection_listener_new`

 In this function at line [line 1214] we are now binding.
 When we try binding our link-local interface, since we haven't save the
 `sin6_scope_id` that we correctly got before, obviously the bind fails.

 I have proven that, again with nemiver, I set a breakpoint on this line
 1214 where we bind, and when we were binding our ipv6 link-local, I just
 added the value of the `sin6_scope_id` [value =3] by changing the memory
 buffer directly from nemiver.

 Surprise... it works perfectly!

 So the next thing now is to check on you last version (from your git) if
 that was fixed or if the bug is still there.

 If the bug is still there, I'll propose on patch against 0.2.9-11 ...
 which hopefully will work on the last version.

 ''Sorry for the initial post, my addresses I correct, it is only the
 syntax of this wiki that tricked me into mixing things up! ''

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23804 [Internal Services/Service - jenkins]: Create ci job for newsletter

[Tor Bug Tracker & Wiki]

#23804: Create ci job for newsletter
-+
 Reporter:  hiro |  Owner:  weasel
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - jenkins  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #23096   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by hiro):

 * owner:  tpa => weasel
 * component:  Internal Services/Tor Sysadmin Team => Internal
 Services/Service - jenkins


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23724 [Applications/Tor Browser]: NoScript restartless update breaks Security Slider and its icon disappears

[Tor Bug Tracker & Wiki]

#23724: NoScript restartless update breaks Security Slider and its icon 
disappears
--+
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  needs_revision
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  noscript  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by cypherpunks):

 Replying to [comment:28 ma1]:
 > Replying to [comment:27 cypherpunks]:
 >
 >
 > > Replying to [comment:26 ma1]:
 > > Hi, Giorgio.
 > > Unfortunately, not all issues with the Security Slider were resolved.
 The last one is that `NoScript preferences backup on the WebExtension
 side` doesn't happen right after updating NoScript settings by the
 Torbutton.
 >
 > It does on startup, shutdown and every type the NoScript Service's
 savePrefs() method is called.
 >
 > It's meant to just backup the configuration, and should have no visible
 impact on how NoScript 5.x actually behaves. So, no "weird effects" from
 this are plausible.
 >
 > > This has weird effects, e.g. videos play automatically on Low, but
 under the rectangle of blocked video, and NoScript icon and menu show that
 the video was blocked (left from the previously selected Medium level).
 >
 > See above. Please file a separate bug if you can consistently reproduce.
 Hmm. Then it could be a restartless update issue (Set Security Slider to
 Medium before update).
 > > >
 > > {{{
 > > 17:21:54.970 1507742514900addons.xpiERROR
 Failed to remove file C:\Tor
 
Browser\Browser\TorBrowser\Data\Browser\profile.default\extensions\trash\{73a6fe31
 -595d-460b-a920-fcc0f8843232}.xpi: [Exception... "Component returned
 failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.remove]"
 nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"  location: "JS frame
 :: resource://gre/modules/addons/XPIProvider.jsm :: recursiveRemove ::
 line 2005"  data: no] ![...]
 > > This is an `ERROR` exactly and should be fixed.
 >
 > If you think it actually is, you should file a bug in Mozilla's Bugzilla
 tracker, Toolkit>Add-ons Manager component.
 Mozilla thinks. And we are not happy with a leftover in trash on disk.
 > > Addons should wait until manifest is registered by Firefox. This is
 critical.
 >
 > Or, it might just be something not expecting NoScript to be uninstalled
 without a browser restart. Can you point out actual user-affecting issues
 directly caused by to this? If so, please file separate bugs.
 If random icon disappearing is not enough, then...
 >
 > > > {{{
 > > 1507747660900addons.xpiDEBUGCalling bootstrap
 method startup on {73a6fe31-595d-460b-a920-fcc0f8843232} version 5.1.2rc5
 > > 1507747661000DeferredSave.extensions.jsonDEBUG
 Starting timer
 > > 1507747661000addons.xpiDEBUG
 removeTemporaryFile: https://addons.mozilla.org/firefox/downloads/latest-
 beta/noscript/addon-722-latest.xpi?src=search removing temp file
 C:\Users\X\AppData\Local\Temp\tmp-2sv.xpi
 > > No matching message handler for the given recipient.
 MessageChannel.jsm:621
 > > }}}
 > > So, this happens in exact place during addon's startup.
 >
 > "This" what?
 This error in MessageChannel.jsm
 > > Now we have
 > > {{{
 > > 1507740751000addons.webextension.WARN
 Loading extension 'null': Reading manifest: Error processing
 permissions.1: Unknown permission "privacy"
 > > 1507740751000addons.webextension.WARN
 Loading extension 'null': Reading manifest: Error processing
 permissions.4: Unknown permission "unlimitedStorage"
 > > 1507740751800addons.webextension.{73a6fe31-595d-
 460b-a920-fcc0f8843232}WARNLoading extension '{73a6fe31
 -595d-460b-a920-fcc0f8843232}': Reading manifest: Error processing
 permissions.1: Unknown permission "privacy"
 > > 1507740751800addons.webextension.{73a6fe31-595d-
 460b-a920-fcc0f8843232}WARNLoading extension '{73a6fe31
 -595d-460b-a920-fcc0f8843232}': Reading manifest: Error processing
 permissions.4: Unknown permission "unlimitedStorage"
 > > }}}
 > > and
 > > {{{
 > > noscript-tbb not found!
 > > [10-11 17:02:22] Torbutton INFO: New window
 > > }}}
 > > which is an exclamation about the obvious thing :)
 >
 > ... none of which is a bug, despite the exclamation mark.
 The exclamation is not a bug. NoScript's `extension 'null'` - it's not so
 obvious.
 > >
 > > Update: it seems `[System+Principal]` doesn't work.
 >
 > Work at what? The message about [System Principal] just takes note that
 there was a window where scripts could not be blocked because it had
 chrome privileges. It's 

[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:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 Currently you can search for things like
 give me all exits in FI running 0.3.1

 https://atlas.torproject.org/#search/country:fi%20flag:exit%20version:0.3.1

 you can not:
 give me all relays by operator with contact foo that do not have the guard
 flag

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #17835 [Core Tor/Tor]: Make ClientPreferIPv6ORPort smarter (was: Make ClientPreferIPv6ORPort/DirPort smarter)

[Tor Bug Tracker & Wiki]

#17835: Make ClientPreferIPv6ORPort smarter
-+--
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-client ipv6  |  Actual Points:
Parent ID:  #17811   | Points:  medium/large
 Reviewer:   |Sponsor:
-+--

Comment (by teor):

 There are no IPv6 DirPorts (any more).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23828 [Core Tor/Tor]: Remove IPv6 addresses from microdescriptors

[Tor Bug Tracker & Wiki]

#23828: Remove IPv6 addresses from microdescriptors
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.6.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  ipv6
Actual Points:|  Parent ID:  #20916
   Points:|   Reviewer:
  Sponsor:|
--+
 When #23826 is locked in, we should remove IPv6 addresses from microdescs.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23827 [Core Tor/Tor]: Clients/Relays: Use IPv6 Addresses from microdesc consensus

[Tor Bug Tracker & Wiki]

#23827: Clients/Relays: Use IPv6 Addresses from microdesc consensus
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  ipv6, regression
Actual Points:|  Parent ID:  #20916
   Points:|   Reviewer:
  Sponsor:|
--+
 Client/Relay Implementation for #20916.

 We need to use the IPv6 addresses from consensuses with versions that
 implement #23826, and ignore microdesc IPv6 addresses.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23826 [Core Tor/Tor]: Authorities: Put Relay IPv6 addresses in the microdesc consensus

[Tor Bug Tracker & Wiki]

#23826: Authorities: Put Relay IPv6 addresses in the microdesc consensus
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  ipv6
Actual Points:|  Parent ID:  #20916
   Points:|   Reviewer:
  Sponsor:|
--+
 Authority Implementation for #20916

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20916 [Core Tor/Tor]: Proposal: Put Relay IPv6 Addresses in the microdesc consensus (was: Inconsistent IPv6 address between consensus and microdescriptor)

[Tor Bug Tracker & Wiki]

#20916: Proposal: Put Relay IPv6 Addresses in the microdesc consensus
--+
 Reporter:  teor  |  Owner:  teor
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  Tor:
  |  0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  needs-proposal, ipv6, regression  |  Actual Points:
Parent ID:| Points:  1
 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] #23812 [Applications/Tor Browser]: json: cannot unmarshal array into Go struct field Process.capabilities of type specs.LinuxCapabilities

[Tor Bug Tracker & Wiki]

#23812: json: cannot unmarshal array into Go struct field Process.capabilities 
of
type specs.LinuxCapabilities
+--
 Reporter:  kkuehl@…|  Owner:  tbb-team
 Type:  defect  | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201710R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by boklm):

 * status:  new => needs_review
 * keywords:  tbb-rbm => tbb-rbm, TorBrowserTeam201710R


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #7481 [Core Tor/Tor]: There should be some way to indicate [2001:...].foo.exit

[Tor Bug Tracker & Wiki]

#7481: There should be some way to indicate [2001:...].foo.exit
-+-
 Reporter:  nickm|  Owner:  (none)
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:  tor-client, ipv6 needs-spec needs-   |  Actual Points:
  design |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

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


Comment:

 `.exit` has been deprecated, we won't implement this feature.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23825 [Applications/Tor Browser]: File SHA512SUMS-52.4.0esr-build1 is not signed with a valid key

[Tor Bug Tracker & Wiki]

#23825: File SHA512SUMS-52.4.0esr-build1 is not signed with a valid key
--+--
 Reporter:  kkuehl@…  |  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:|
--+--
 Building project firefox-langpacks - firefox-langpacks-52.4.0esr-build1
 -linux-x86_64-130d9e
 Error: File SHA512SUMS-52.4.0esr-build1 is not signed with a valid key
 Makefile:69: recipe for target 'testbuild-linux-x86_64' failed
 make: *** [testbuild-linux-x86_64] Error 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] #23812 [Applications/Tor Browser]: json: cannot unmarshal array into Go struct field Process.capabilities of type specs.LinuxCapabilities

[Tor Bug Tracker & Wiki]

#23812: json: cannot unmarshal array into Go struct field Process.capabilities 
of
type specs.LinuxCapabilities
--+--
 Reporter:  kkuehl@…  |  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 kkuehl@…):

 Everything worked but at the end I received
 Error: File SHA512SUMS-52.4.0esr-build1 is not signed with a valid key
 Makefile:69: recipe for target 'testbuild-linux-x86_64' failed
 make: *** [testbuild-linux-x86_64] Error 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

[tor-bugs] #23824 [Core Tor/Tor]: Make IPv6-only bridges work

[Tor Bug Tracker & Wiki]

#23824: Make IPv6-only bridges work
--+--
 Reporter:  teor  |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  ipv6, tor-bridge
Actual Points:|  Parent ID:  #4847
   Points:|   Reviewer:
  Sponsor:|
--+--
 This needs bridge guards (#7144 - so the bridge can connect via a dual-
 stack bridge guard to whatever guard the client has selected), and it
 needs IPv6 bridges to work in general (#4847).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #4847 [Core Tor/Tor]: Fix IPv6 bridges with a private/dynamic IPv4 address (was: Bridges binding only to an IPv6 address doesn't work)

[Tor Bug Tracker & Wiki]

#4847: Fix IPv6 bridges with a private/dynamic IPv4 address
--+-
 Reporter:  ln5   |  Owner:  ln5
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.2.3.10-alpha
 Severity:  Normal| Resolution:
 Keywords:  ipv6, tor-bridge  |  Actual Points:
Parent ID:  #5788 | Points:
 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] #23724 [Applications/Tor Browser]: NoScript restartless update breaks Security Slider and its icon disappears

[Tor Bug Tracker & Wiki]

#23724: NoScript restartless update breaks Security Slider and its icon 
disappears
--+
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  needs_revision
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  noscript  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by ma1):

 Replying to [comment:27 cypherpunks]:


 > Replying to [comment:26 ma1]:
 > Hi, Giorgio.
 > Unfortunately, not all issues with the Security Slider were resolved.
 The last one is that `NoScript preferences backup on the WebExtension
 side` doesn't happen right after updating NoScript settings by the
 Torbutton.

 It does on startup, shutdown and every type the NoScript Service's
 savePrefs() method is called.

 It's meant to just backup the configuration, and should have no visible
 impact on how NoScript 5.x actually behaves. So, no "weird effects" from
 this are plausible.

 > This has weird effects, e.g. videos play automatically on Low, but under
 the rectangle of blocked video, and NoScript icon and menu show that the
 video was blocked (left from the previously selected Medium level).

 See above. Please file a separate bug if you can consistently reproduce.

 > >
 > {{{
 > 17:21:54.970 1507742514900addons.xpiERRORFailed
 to remove file C:\Tor
 
Browser\Browser\TorBrowser\Data\Browser\profile.default\extensions\trash\{73a6fe31
 -595d-460b-a920-fcc0f8843232}.xpi: [Exception... "Component returned
 failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.remove]"
 nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"  location: "JS frame
 :: resource://gre/modules/addons/XPIProvider.jsm :: recursiveRemove ::
 line 2005"  data: no] ![...]
 > This is an `ERROR` exactly and should be fixed.

 If you think it actually is, you should file a bug in Mozilla's Bugzilla
 tracker, Toolkit>Add-ons Manager component.

 > Addons should wait until manifest is registered by Firefox. This is
 critical.

 Or, it might just be something not expecting NoScript to be uninstalled
 without a browser restart. Can you point out actual user-affecting issues
 directly caused by to this? If so, please file separate bugs.


 > > {{{
 > 1507747660900addons.xpiDEBUGCalling bootstrap
 method startup on {73a6fe31-595d-460b-a920-fcc0f8843232} version 5.1.2rc5
 > 1507747661000DeferredSave.extensions.jsonDEBUG
 Starting timer
 > 1507747661000addons.xpiDEBUGremoveTemporaryFile:
 https://addons.mozilla.org/firefox/downloads/latest-
 beta/noscript/addon-722-latest.xpi?src=search removing temp file
 C:\Users\X\AppData\Local\Temp\tmp-2sv.xpi
 > No matching message handler for the given recipient.
 MessageChannel.jsm:621
 > }}}
 > So, this happens in exact place during addon's startup.

 "This" what?

 > Now we have
 > {{{
 > 1507740751000addons.webextension.WARN
 Loading extension 'null': Reading manifest: Error processing
 permissions.1: Unknown permission "privacy"
 > 1507740751000addons.webextension.WARN
 Loading extension 'null': Reading manifest: Error processing
 permissions.4: Unknown permission "unlimitedStorage"
 > 1507740751800addons.webextension.{73a6fe31-595d-
 460b-a920-fcc0f8843232}WARNLoading extension '{73a6fe31
 -595d-460b-a920-fcc0f8843232}': Reading manifest: Error processing
 permissions.1: Unknown permission "privacy"
 > 1507740751800addons.webextension.{73a6fe31-595d-
 460b-a920-fcc0f8843232}WARNLoading extension '{73a6fe31
 -595d-460b-a920-fcc0f8843232}': Reading manifest: Error processing
 permissions.4: Unknown permission "unlimitedStorage"
 > }}}
 > and
 > {{{
 > noscript-tbb not found!
 > [10-11 17:02:22] Torbutton INFO: New window
 > }}}
 > which is an exclamation about the obvious thing :)

 ... none of which is a bug, despite the exclamation mark.

 >
 > Update: it seems `[System+Principal]` doesn't work.

 Work at what? The message about [System Principal] just takes note that
 there was a window where scripts could not be blocked because it had
 chrome privileges. It's normal, and nothing that needs to be "fixed".

 Suggestion: please set the "noscript.consoleDump" preference to 0. If
 anything '''actually''' abnormal happens, you'll get messages in the
 browser console anyway.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list

Re: [tor-bugs] #23812 [Applications/Tor Browser]: json: cannot unmarshal array into Go struct field Process.capabilities of type specs.LinuxCapabilities

[Tor Bug Tracker & Wiki]

#23812: json: cannot unmarshal array into Go struct field Process.capabilities 
of
type specs.LinuxCapabilities
--+--
 Reporter:  kkuehl@…  |  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 kkuehl@…):

 Your patch does in fact print 1
 ./rbm/rbm showconf tor var_p/runc_spec100
 1

 make testbuild-linux-x86_64
 is starting to work, I think this fixes the issue.
 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] #21969 [Core Tor/Tor]: We're missing descriptors for some of our primary entry guards

[Tor Bug Tracker & Wiki]

#21969: We're missing descriptors for some of our primary entry guards
---+---
 Reporter:  asn|  Owner:  asn
 Type:  defect | Status:
   |  needs_information
 Priority:  Immediate  |  Milestone:  Tor:
   |  0.3.2.x-final
Component:  Core Tor/Tor   |Version:  Tor:
   |  0.3.0.6
 Severity:  Blocker| Resolution:
 Keywords:  tor-guard, tor-bridge, tor-client  |  Actual Points:
Parent ID: | Points:  1.5
 Reviewer: |Sponsor:  SponsorU
---+---

Comment (by asn):

 '''Announcement to people who encounter this bug:''' If this destroys your
 Tor experience, please downgrade to Tor-0.2.9 for now. We are working on
 this issue and hope to have fixes ASAP. 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] #23819 [Core Tor/Tor]: Support IPv6 link-local interface addresses (was: Tor doesn't bind to link-local (ipv6) addresses)

[Tor Bug Tracker & Wiki]

#23819: Support IPv6 link-local interface addresses
-+--
 Reporter:  Zakhar   |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor |Version:  Tor: unspecified
 Severity:  Normal   | Resolution:
 Keywords:  ipv6 link-local  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by teor):

 * version:  Tor: 0.2.9.11 => Tor: unspecified
 * type:  defect => enhancement
 * milestone:   => Tor: unspecified


Comment:

 Hi! Thanks for this bug report.

 Tor documents that IPv6 address syntax that is does support:
 [:::].

 It does not support additional IPv6 syntax, including specifying
 interfaces using the % syntax.

 The parsing of these kinds of addresses also looks like a bug - it should
 not parse ` fe80::1` as a separate part of the address:
 {{{
 Oct 10 21:34:28.386 [warn] Could not bind to
 fe80::1[c9a:c3ff:fec8:7768:9040 c9a:c3ff:fec8:7768:9040]: Invalid argument
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23724 [Applications/Tor Browser]: NoScript restartless update breaks Security Slider and its icon disappears

[Tor Bug Tracker & Wiki]

#23724: NoScript restartless update breaks Security Slider and its icon 
disappears
--+
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  needs_revision
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  noscript  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by cypherpunks):

 Replying to [comment:26 ma1]:
 Hi, Giorgio.
 Unfortunately, not all issues with the Security Slider were resolved. The
 last one is that `NoScript preferences backup on the WebExtension side`
 doesn't happen right after updating NoScript settings by the Torbutton.
 This has weird effects, e.g. videos play automatically on Low, but under
 the rectangle of blocked video, and NoScript icon and menu show that the
 video was blocked (left from the previously selected Medium level).
 > A lot of scary stuff spit by the console is unrelated to NoScript
 specifically (may apply to any hybrid / restatless extension) and/or
 cannot be fixed "from the inside" of the add-on: case in point, from the
 browser being unable to delete temporary files
 {{{
 17:21:54.970 1507742514900  addons.xpi  ERROR   Failed to remove
 file C:\Tor
 
Browser\Browser\TorBrowser\Data\Browser\profile.default\extensions\trash\{73a6fe31
 -595d-460b-a920-fcc0f8843232}.xpi: [Exception... "Component returned
 failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIFile.remove]"
 nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"  location: "JS frame
 :: resource://gre/modules/addons/XPIProvider.jsm :: recursiveRemove ::
 line 2005"  data: no] Stack trace:
 recursiveRemove()@resource://gre/modules/addons/XPIProvider.jsm:2005 <
 recursiveRemove()@resource://gre/modules/addons/XPIProvider.jsm:2020 <
 .installAddon()@resource://gre/modules/addons/XPIProvider.jsm:8600 <
 startInstall/<()@resource://gre/modules/addons/XPIProvider.jsm:5951 <
 TaskImpl_run()@resource://gre/modules/Task.jsm:319 <
 Handler.prototype.process()@resource://gre/modules/Promise.jsm ->
 resource://gre/modules/Promise-backend.js:932 <
 this.PromiseWalker.walkerLoop()@resource://gre/modules/Promise.jsm ->
 resource://gre/modules/Promise-backend.js:813 <
 this.PromiseWalker.scheduleWalkerLoop/<()@resource://gre/modules/Promise.jsm
 -> resource://gre/modules/Promise-backend.js:747 1 Log.jsm:753
 App_append resource://gre/modules/Log.jsm:753:9
 Logger.prototype.log resource://gre/modules/Log.jsm:389:7
 Logger.prototype.error resource://gre/modules/Log.jsm:397:5
 recursiveRemove
 resource://gre/modules/addons/XPIProvider.jsm:2010:7
 forEach self-hosted:251:13
 recursiveRemove
 resource://gre/modules/addons/XPIProvider.jsm:2020:3
 .installAddon resource://gre/modules/addons/XPIProvider.jsm:8600:9
 startInstall/<
 resource://gre/modules/addons/XPIProvider.jsm:5951:20
 next self-hosted:1120:9
 TaskImpl_run resource://gre/modules/Task.jsm:319:42
 bound TaskImpl_run self-hosted:957:17
 Handler.prototype.process resource://gre/modules/Promise-
 backend.js:932:23
 this.PromiseWalker.walkerLoop resource://gre/modules/Promise-
 backend.js:813:7
 bound  self-hosted:913:17
 bound bound  self-hosted:913:17
 this.PromiseWalker.scheduleWalkerLoop/< resource://gre/modules
 /Promise-backend.js:747:11
 1507742514900   addons.xpi  WARNFailed to remove trash directory
 when installing {73a6fe31-595d-460b-a920-fcc0f8843232}: [Exception...
 "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)
 [nsIFile.remove]"  nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"
 location: "JS frame :: resource://gre/modules/addons/XPIProvider.jsm ::
 recursiveRemove :: line 2005"  data: no] Stack trace:
 recursiveRemove()@resource://gre/modules/addons/XPIProvider.jsm:2005 <
 recursiveRemove()@resource://gre/modules/addons/XPIProvider.jsm:2020 <
 .installAddon()@resource://gre/modules/addons/XPIProvider.jsm:8600 <
 startInstall/<()@resource://gre/modules/addons/XPIProvider.jsm:5951 <
 TaskImpl_run()@resource://gre/modules/Task.jsm:319 <
 Handler.prototype.process()@resource://gre/modules/Promise.jsm ->
 resource://gre/modules/Promise-backend.js:932 <
 this.PromiseWalker.walkerLoop()@resource://gre/modules/Promise.jsm ->
 resource://gre/modules/Promise-backend.js:813 <
 this.PromiseWalker.scheduleWalkerLoop/<()@resource://gre/modules/Promise.jsm
 -> resource://gre/modules/Promise-backend.js:747
 }}}
 This is an `ERROR` exactly and should be fixed.
 > or to register chrome packages at the right time.
 Addons should wait until manifest is 

Re: [tor-bugs] #23812 [Applications/Tor Browser]: json: cannot unmarshal array into Go struct field Process.capabilities of type specs.LinuxCapabilities

[Tor Bug Tracker & Wiki]

#23812: json: cannot unmarshal array into Go struct field Process.capabilities 
of
type specs.LinuxCapabilities
--+--
 Reporter:  kkuehl@…  |  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 boklm):

 I created a new version of the patch in branch `bug_23812_v2`:
 https://gitweb.torproject.org/user/boklm/tor-browser-
 build.git/commit/?h=bug_23812_v2=0b698f41ac88ef08b33d070a576c9f5649238af6

 With this version of the patch, `./rbm/rbm showconf tor
 var_p/runc_spec100` should print `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] #23822 [Core Tor/Tor]: tor router not working

[Tor Bug Tracker & Wiki]

#23822: tor router not working
--+
 Reporter:  y.net |  Owner:  (none)
 Type:  project   | Status:  closed
 Priority:  High  |  Milestone:  Tor: 0.2.5.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.2.5.12
 Severity:  Normal| Resolution:  not a bug
 Keywords:  not working   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

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


Comment:

 You have multiple instances of tor running, or your OS keeps ports for a
 long time after they're used. Try restarting the OS.

 And please post a notice-level log next time, it contains all the
 information we need.
 The debug log is too long, and doesn't contain any relevant failures.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21969 [Core Tor/Tor]: We're missing descriptors for some of our primary entry guards

[Tor Bug Tracker & Wiki]

#21969: We're missing descriptors for some of our primary entry guards
---+---
 Reporter:  asn|  Owner:  asn
 Type:  defect | Status:
   |  needs_information
 Priority:  Immediate  |  Milestone:  Tor:
   |  0.3.2.x-final
Component:  Core Tor/Tor   |Version:  Tor:
   |  0.3.0.6
 Severity:  Blocker| Resolution:
 Keywords:  tor-guard, tor-bridge, tor-client  |  Actual Points:
Parent ID: | Points:  1.5
 Reviewer: |Sponsor:  SponsorU
---+---
Changes (by dgoulet):

 * priority:  High => Immediate
 * severity:  Normal => Blocker


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

Re: [tor-bugs] #22768 [Internal Services/Service - jenkins]: Add building Tor with Rust support to Jenkins

[Tor Bug Tracker & Wiki]

#22768: Add building Tor with Rust support to Jenkins
-+
 Reporter:  isis |  Owner:  weasel
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - jenkins  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, tor-ci |  Actual Points:
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+

Comment (by isis):

 We talked about this a bit at the meeting.  We need to up the priority of
 this ticket since we're now discussing a future where Rust is ''required''
 to build tor, and having early feedback on breakage would be better while
 Rust is still optional.

 For an update, every time I've tried to build debian-tor using the
 following (with multiple versions between 0.3.1.x and 0.3.2.x) with
 `--enable-rust` has failed:

 {{{
 user@build-tor:~$ cat code/torproject/tor/build-tor.sh
 #!/bin/bash

 tag=tor-0.3.1.6-rc
 debian_tag=debian-tor-0.3.1.6-rc

 if test $# -lt 2 ; then
 printf "Usage: %s TOR_TAG DEBIAN_TOR_TAG\n\n" "$(basename $0)"
 printf "Need tag numbers for tor and debian, e.g. '%s' '%s' \n" "$tag"
 "$debian_tag"
 exit 1
 else
 tag=$1
 debian_tag=$2
 fi

 sudo apt-get update
 sudo apt-get install -y dpkg dpkg-dev libevent-dev libssl-dev asciidoc
 quilt dh-apparmor libseccomp-dev dh-systemd libsystemd-dev pkg-config dh-
 autoreconf libfakeroot zlib1g zlib1g-dev automake liblzma-dev libzstd-dev

 git checkout $tag

 # Fetch the newest debian packaging and checkout the tag
 cd ../debian-new &&
 git fetch origin &&
 git checkout $debian_tag

 # Move the new packaging into the tor source tree
 cp -R ./debian ../debian-old
 cp -R ../debian-new/debian ./

 rm -rf debian/patches/improve-geoip-warning
 echo > debian/patches/series

 printf "Please remove the --with-quilt line!\n"
 sleep 5

 emacs -nw debian/rules

 make distclean
 ./configure \
 --enable-fatal-warnings
 --enable-rust --enable-cargo-online-mode
 dh_auto_build
 dpkg-buildpackage -rfakeroot
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21145 [Metrics/ExoneraTor]: Adapt ExoneraTor to using metrics-base

[Tor Bug Tracker & Wiki]

#21145: Adapt ExoneraTor to using metrics-base
+--
 Reporter:  iwakeh  |  Owner:  iwakeh
 Type:  enhancement | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2017|  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by iwakeh):

 * status:  accepted => needs_review


Comment:

 Please review
 [https://gitweb.torproject.org/user/iwakeh/exonerator.git/commit/?h=task-21145
 these changes], which are optimistically based on the patch for #19624
 (two commits for checkstyle fixes and using commons-lang3).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23724 [Applications/Tor Browser]: NoScript restartless update breaks Security Slider and its icon disappears

[Tor Bug Tracker & Wiki]

#23724: NoScript restartless update breaks Security Slider and its icon 
disappears
--+
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  needs_revision
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  noscript  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by ma1):

 Replying to [comment:25 cypherpunks]:


 > It seems Giorgio doesn't talk with anonymous :)

 A lot of scary stuff spit by the console is unrelated to NoScript
 specifically (may apply to any hybrid / restatless extension) and/or
 cannot be fixed "from the inside" of the add-on: case in point, from the
 browser being unable to delete temporary files or to register chrome
 packages at the right time.

 >
 >
 > {{{
 > No chrome package registered for
 chrome://noscript/locale/about.properties
 > 08:26:39.787 No matching message handler for the given recipient. 1
 MessageChannel.jsm:621
 > _handleMessage/ }}}

 ... or this, which might happen whenever any WebExtension is uninstalled /
 disabled if there were pending messages.

 > and comment:22.

 This should be fixed ('''in most cases''', at least) by
 [https://noscript.net/getit#devel rc5] (about to become a release) and was
 cosmetic anyway.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19624 [Metrics/ExoneraTor]: Comply to Metrics Java style guide

[Tor Bug Tracker & Wiki]

#19624: Comply to Metrics Java style guide
+--
 Reporter:  iwakeh  |  Owner:  iwakeh
 Type:  task| Status:  needs_review
 Priority:  Medium  |  Milestone:  ExoneraTor 1.0.0
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2017|  Actual Points:
Parent ID:  #19611  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by iwakeh):

 Please find another commit on the
 [https://gitweb.torproject.org/user/iwakeh/exonerator.git/log/?h=task-19624
 above branch] that replaces the legacy commons lang version (catering to
 java 1.2) by lang3 (designed for Java 7 and up).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21145 [Metrics/ExoneraTor]: Adapt ExoneraTor to using metrics-base

[Tor Bug Tracker & Wiki]

#21145: Adapt ExoneraTor to using metrics-base
+--
 Reporter:  iwakeh  |  Owner:  iwakeh
 Type:  enhancement | Status:  accepted
 Priority:  Medium  |  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2017|  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by iwakeh):

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


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19624 [Metrics/ExoneraTor]: Comply to Metrics Java style guide

[Tor Bug Tracker & Wiki]

#19624: Comply to Metrics Java style guide
+--
 Reporter:  iwakeh  |  Owner:  iwakeh
 Type:  task| Status:  needs_review
 Priority:  Medium  |  Milestone:  ExoneraTor 1.0.0
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2017|  Actual Points:
Parent ID:  #19611  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by iwakeh):

 * status:  assigned => needs_review


Comment:

 Please review
 [https://gitweb.torproject.org/user/iwakeh/exonerator.git/commit/?h=task-19624
 these checkstyle fixes].

 Once this is merged the ticket should be closed, because all else will be
 part of ticket #21145.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23597 [Metrics/Library]: Correct links in metrics-lib overview page.

[Tor Bug Tracker & Wiki]

#23597: Correct links in metrics-lib overview page.
-+---
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  metrics-lib 2.2.0
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  metrics-2017 |  Actual Points:
Parent ID:   | Points:
 Reviewer:  karsten  |Sponsor:
-+---

Comment (by iwakeh):

 This actually got shipped already in version 2.1.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] #15618 [Core Tor/Tor]: Tried to establish rendezvous on non-OR circuit with purpose Acting as rendevous (pending)

[Tor Bug Tracker & Wiki]

#15618: Tried to establish rendezvous on non-OR circuit with purpose Acting as
rendevous (pending)
-+-
 Reporter:  asn  |  Owner:  dgoulet
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs needs-insight needs-  |  Actual Points:
  diagnosis  |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by Jaym):

 Could this be related?: https://metrics.torproject.org/torperf-
 
failures.html?start=2017-04-01=2017-10-11=all=public=50kb

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23724 [Applications/Tor Browser]: NoScript restartless update breaks Security Slider and its icon disappears

[Tor Bug Tracker & Wiki]

#23724: NoScript restartless update breaks Security Slider and its icon 
disappears
--+
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  needs_revision
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  noscript  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by cypherpunks):

 It seems Giorgio doesn't talk with anonymous :)
 But, nevertheless, let's summarize the results of rc4:

 Clean install:
 {{{
 No chrome package registered for chrome://noscript/skin/icon32.png
 1507707555800 addons.xpi WARN Failed to remove temporary file
 C:\Users\X\AppData\Local\Temp\tmp-04t.xpi for addon
 https://addons.mozilla.org/firefox/downloads/latest-
 beta/noscript/addon-722-latest.xpi?src=ss: [Exception... "Component
 returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)
 [nsIFile.remove]"  nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"
 location: "JS frame :: resource://gre/modules/addons/XPIProvider.jsm ::
 removeTemporaryFile :: line 5598"  data: no] Stack trace:
 removeTemporaryFile()@resource://gre/modules/addons/XPIProvider.jsm:5598 <
 startInstall/<()@resource://gre/modules/addons/XPIProvider.jsm:6027 <
 Handler.prototype.process()@resource://gre/modules/Promise.jsm ->
 resource://gre/modules/Promise-backend.js:932 <
 this.PromiseWalker.walkerLoop()@resource://gre/modules/Promise.jsm ->
 resource://gre/modules/Promise-backend.js:813 <
 this.PromiseWalker.scheduleWalkerLoop/<()@resource://gre/modules/Promise.jsm
 -> resource://gre/modules/Promise-backend.js:747
 [10-11 07:39:15] Torbutton NOTE: Failed to update NoScript status for
 security setings: TypeError: win.noscriptOverlay is undefined
 1507707556000 addons.webextension.{73a6fe31-595d-460b-a920-fcc0f8843232}
 WARN Loading extension '{73a6fe31-595d-460b-a920-fcc0f8843232}': Reading
 manifest: Error processing permissions.1: Unknown permission "privacy"
 }}}
 The first error (two similar, actually) leads to NoScript's two icons in
 Customize menu don't show. TBB doesn't use them, though.
 gk: the second error is `tbb-disk-leak`.

 Restartless update:
 {{{
 No chrome package registered for chrome://noscript/locale/about.properties
 08:26:39.787 No matching message handler for the given recipient. 1
 MessageChannel.jsm:621
 _handleMessage/https://trac.torproject.org/projects/tor/ticket/23724#comment:25>
Tor Bug Tracker & Wiki 
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] #23823 [Obfuscation/BridgeDB]: Prepopulate ipv6 checkbox if ipv6 bridges are available for the transport.

[Tor Bug Tracker & Wiki]

#23823: Prepopulate ipv6 checkbox if ipv6 bridges are available for the 
transport.
--+
 Reporter:  cypherpunks   |  Owner:  isis
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Obfuscation/BridgeDB  |Version:
 Severity:  Normal|   Keywords:  bridgedb-reportbug
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 No JavaScript, please. This can be done purely in HTML and CSS. The server
 generates an  for all the variants, hides all by
 default using css and shows the needed checkbox based on selected element.
 A bit ugly, but it is the solution.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #17064 [Core Tor/Torflow]: scanner.9 in torflow/bwauth failing

[Tor Bug Tracker & Wiki]

#17064: scanner.9 in torflow/bwauth failing
--+
 Reporter:  tom   |  Owner:  aagbsn
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Torflow  |Version:
 Severity:  Blocker   | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by tom):

 Okay, I have this error currently:

 {{{
 WARN[Wed Oct 11 02:35:14 2017]:Error building circ: ('552 No such router
 "0456CEE48AF23B95610645D037D385F35679A1E2"',)
 }}}

 The first occurrence is
 {{{
 WARN[Wed Oct 04 23:23:09 2017]:Error building circ: ('552 No such router
 "0456CEE48AF23B95610645D037D385F35679A1E2"',)
 }}}

 I can't find this relay in the consensus at https://consensus-
 health.torproject.org/consensus-
 health-2017-10-04-23-00.html#0456CEE48AF23B95610645D037D385F35679A1E2 or
 for the next 7 hours.

 The tor log has:

  - 33911 instances of the following line between Aug 8th and current
   - [notice] Tried for 120 seconds to get a connection to
 130.242.60.21:443. Giving up. (waiting for controller)
  - Nothing unusual (at the notice level) except the connection give up
 around that time. A few control connections, a heartbeat, and the above
 notice.

 There is nothing about NEWCONSENSUS in scanner.9/bw.log prior to the first
 mention of 0456CEE48AF23B95610645D037D385F35679A1E2 (which is the no such
 router error).

 Before that error it's ~ 2 days of
 {{{
 WARN[Wed Oct 04 23:16:24 2017]:No circuit for 2157208 circ: 0
 NOTICE[Wed Oct 04 23:16:24 2017]:Stream 2157208 CLOSED with TIMEOUT
 NOTICE[Wed Oct 04 23:18:24 2017]:Tor timed out our SOCKS stream request.
 WARN[Wed Oct 04 23:18:26 2017]:Not enough streams yet. 0 < 17.875
 WARN[Wed Oct 04 23:18:26 2017]:No circuit for 2157272 circ: 0
 NOTICE[Wed Oct 04 23:18:26 2017]:Stream 2157272 FAILED with TIMEOUT
 WARN[Wed Oct 04 23:18:26 2017]:No circuit for 2157272 circ: 0
 NOTICE[Wed Oct 04 23:18:26 2017]:Stream 2157272 CLOSED with TIMEOUT
 NOTICE[Wed Oct 04 23:20:26 2017]:Tor timed out our SOCKS stream request.
 WARN[Wed Oct 04 23:20:28 2017]:Not enough streams yet. 0 < 17.875
 NOTICE[Wed Oct 04 23:20:28 2017]:Stream 2157339 FAILED with TIMEOUT
 }}}

 Then right before that it's

 {{{
 WARN[Mon Oct 02 23:15:23 2017]:Not enough streams yet. 62 < 79.625
 WARN[Mon Oct 02 23:15:35 2017]:Not enough streams yet. 63 < 79.625
 WARN[Mon Oct 02 23:15:42 2017]:Not enough streams yet. 64 < 79.625
 NOTICE[Mon Oct 02 23:17:42 2017]:Tor timed out our SOCKS stream request.
 WARN[Mon Oct 02 23:17:42 2017]:Not enough streams yet. 64 < 79.625
 NOTICE[Mon Oct 02 23:17:42 2017]:Stream 2054350 FAILED with TIMEOUT
 NOTICE[Mon Oct 02 23:17:42 2017]:Stream 2054350 CLOSED with TIMEOUT
 WARN[Mon Oct 02 23:17:50 2017]:Not enough streams yet. 65 < 79.625
 NOTICE[Mon Oct 02 23:19:50 2017]:Tor timed out our SOCKS stream request.
 WARN[Mon Oct 02 23:19:50 2017]:Not enough streams yet. 65 < 79.625
 NOTICE[Mon Oct 02 23:19:50 2017]:Stream 2054397 FAILED with TIMEOUT
 NOTICE[Mon Oct 02 23:19:50 2017]:Stream 2054397 CLOSED with TIMEOUT
 NOTICE[Mon Oct 02 23:21:50 2017]:Tor timed out our SOCKS stream request.
 WARN[Mon Oct 02 23:21:50 2017]:Not enough streams yet. 65 < 79.625
 NOTICE[Mon Oct 02 23:21:50 2017]:Stream 2054447 FAILED with TIMEOUT
 NOTICE[Mon Oct 02 23:21:50 2017]:Stream 2054447 CLOSED with TIMEOUT
 WARN[Mon Oct 02 23:23:16 2017]:Not enough streams yet. 66 < 79.625
 WARN[Mon Oct 02 23:23:23 2017]:Not enough streams yet. 67 < 79.625
 NOTICE[Mon Oct 02 23:29:23 2017]:Wedged Tor stream. Closing all streams
 WARN[Mon Oct 02 23:29:24 2017]:Timer exceeded limit: 360.298864841

 WARN[Mon Oct 02 23:29:24 2017]:Not enough streams yet. 68 < 79.625
 WARN[Mon Oct 02 23:29:27 2017]:Not enough streams yet. 69 < 79.625
 WARN[Mon Oct 02 23:29:45 2017]:Not enough streams yet. 70 < 79.625
 WARN[Mon Oct 02 23:30:26 2017]:Not enough streams yet. 71 < 79.625
 WARN[Mon Oct 02 23:31:21 2017]:Not enough streams yet. 72 < 79.625
 NOTICE[Mon Oct 02 23:33:22 2017]:Tor timed out our SOCKS stream request.
 WARN[Mon Oct 02 23:33:22 2017]:Not enough streams yet. 72 < 79.625
 NOTICE[Mon Oct 02 23:33:22 2017]:Stream 2054746 FAILED with TIMEOUT
 NOTICE[Mon Oct 02 23:33:22 2017]:Stream 2054746 CLOSED with TIMEOUT
 WARN[Mon Oct 02 23:33:29 2017]:Not enough streams yet. 73 < 79.625
 WARN[Mon Oct 02 23:34:22 2017]:Not enough streams yet. 74 < 79.625
 NOTICE[Mon Oct 02 23:36:23 2017]:Tor timed out our SOCKS stream request.
 WARN[Mon Oct 02 23:36:23 2017]:Not enough streams yet. 74 < 79.625
 NOTICE[Mon Oct 02 23:36:23 2017]:Stream 2054817 FAILED with TIMEOUT
 NOTICE[Mon Oct 02 23:36:23 2017]:Stream 2054817 CLOSED with TIMEOUT
 WARN[Mon Oct 02 23:36:46 2017]:Not enough streams yet. 75 < 79.625
 NOTICE[Mon Oct 02 23:38:46 2017]:Tor timed out our