Re: [tor-bugs] #27130 [Core Tor/Tor]: rust dependency updating instructions don't work

[Tor Bug Tracker & Wiki]

#27130: rust dependency updating instructions don't work
-+-
 Reporter:  cyberpunks   |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.9
 Severity:  Normal   | Resolution:
 Keywords:  rust, doc, 032-backport, |  Actual Points:
  033-backport, 034-backport |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  rust,doc => rust, doc, 032-backport, 033-backport,
   034-backport
 * status:  new => needs_review
 * milestone:   => Tor: 0.3.5.x-final


Comment:

 Hi, thanks for this patch.

 Did you just test on master?
 Do you think we need to backport this patch to previous releases?
 (Rust support was introduced in 0.3.1, and we still support 0.3.2 and
 later.)

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

Re: [tor-bugs] #23588 [Core Tor/Tor]: Write fascist_firewall_choose_address_ls() and use it in hs_get_extend_info_from_lspecs()

[Tor Bug Tracker & Wiki]

#23588: Write fascist_firewall_choose_address_ls() and use it in
hs_get_extend_info_from_lspecs()
-+-
 Reporter:  teor |  Owner:  neel
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs, single-onion,   |  Actual Points:
  ipv6, 034-triage-20180328, |
  034-removed-20180328   |
Parent ID:  #23493   | Points:  1
 Reviewer:  teor |Sponsor:
-+-

Comment (by teor):

 > I do have a question: where should I put the BUG() warning when there's
 no reachable address?

 hs_get_extend_info_from_lspecs() is a good place to check if the address
 and port returned by fascist_firewall_choose_address_ls() are valid. (You
 can use tor_addr_port_is_valid() to check ap.)

 In future, when we make other functions call
 hs_get_extend_info_from_lspecs(), they might want to do different checks.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27133 [Applications/Quality Assurance and Testing]: tbb-testsuite: update useragent string in fp_navigator, useragent and settings tests

[Tor Bug Tracker & Wiki]

#27133: tbb-testsuite: update useragent string in fp_navigator, useragent and
settings tests
-+-
 Reporter:  boklm|  Owner:  boklm
 Type:  task | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:   |Version:
  Applications/Quality Assurance |
  and Testing|   Keywords:  boklm201808,
 Severity:  Normal   |  TorBrowserTeam201808, tbb-testsuite
Actual Points:   |  Parent ID:  #27105
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 We need to update the useragent string in the `fp_navigator`, `useragent`
 and `settings` tests for Tor Browser 8.0.

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

Re: [tor-bugs] #26189 [Applications/Tor Browser]: Remove our content policy hack for #8725

[Tor Bug Tracker & Wiki]

#26189: Remove our content policy hack for #8725
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_revision
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff60-esr, tbb-torbutton, |  Actual Points:
  TorBrowserTeam201808   |
Parent ID:  #26544   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * status:  needs_review => needs_revision
 * keywords:  ff60-esr, tbb-torbutton, TorBrowserTeam201808R => ff60-esr,
 tbb-torbutton, TorBrowserTeam201808


Comment:

 Thanks, just one nit:

 I think
 {{{
 pref("extensions.torbutton.resource_and_chrome_uri_fingerprinting",false);
 }}}
 should go now as well (still available in `preferences.js`in your patch).

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

Re: [tor-bugs] #9809 [Applications/Tor Browser]: Re-disable Ctypes in TBB 7.0

[Tor Bug Tracker & Wiki]

#9809: Re-disable Ctypes in TBB 7.0
+--
 Reporter:  mikeperry   |  Owner:  tbb-team
 Type:  enhancement | Status:  new
 Priority:  High|  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-3.0, tbb-firefox-patch  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by gk):

 That's for WebExtensions, yes, but the blocker here is actually #10317 and
 I am not aware that Firefox does work now without ctypes enabled, but
 would be happy to be proven wrong (ideally with links to Mozilla bugs that
 fixed this).

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

[tor-bugs] #27134 [- Select a component]: connect issue

[Tor Bug Tracker & Wiki]

#27134: connect issue
--+--
 Reporter:  ElecLib   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:  Tor: unspecified
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 8/14/2018 9:03:13 AM.000 [NOTICE] Bootstrapped 10%: Finishing handshake
 with directory server
 8/14/2018 9:03:13 AM.000 [NOTICE] Bootstrapped 15%: Establishing an
 encrypted directory connection
 8/14/2018 9:03:13 AM.000 [NOTICE] Bootstrapped 20%: Asking for
 networkstatus consensus
 8/14/2018 9:03:13 AM.000 [NOTICE] Bootstrapped 25%: Loading networkstatus
 consensus
 8/14/2018 9:03:15 AM.600 [WARN] Our clock is 56 minutes, 47 seconds behind
 the time published in the consensus network status document (2018-08-14
 08:00:00 UTC).  Tor needs an accurate clock to work correctly. Please
 check your time and date settings!
 8/14/2018 9:03:15 AM.600 [WARN] Received microdesc flavor consensus with
 skewed time (CONSENSUS): It seems that our clock is behind by 56 minutes,
 47 seconds, or that theirs is ahead. Tor requires an accurate clock to
 work: please check your time, timezone, and date settings.
 8/14/2018 9:03:15 AM.600 [WARN] Problem bootstrapping. Stuck at 25%:
 Loading networkstatus consensus. (Clock skew -3407 in microdesc flavor
 consensus from CONSENSUS; CLOCK_SKEW; count 1; recommendation warn; host ?
 at ?)
 8/14/2018 9:03:15 AM.600 [NOTICE] I learned some more directory
 information, but not enough to build a circuit: We have no recent usable
 consensus.
 8/14/2018 9:03:15 AM.600 [NOTICE] Closing no-longer-configured Socks
 listener on 127.0.0.1:9150
 8/14/2018 9:03:15 AM.600 [NOTICE] DisableNetwork is set. Tor will not make
 or accept non-control network connections. Shutting down all existing
 connections.
 8/14/2018 9:03:15 AM.600 [NOTICE] Closing old Socks listener on
 127.0.0.1:9150
 8/14/2018 9:03:16 AM.600 [NOTICE] Delaying directory fetches:
 DisableNetwork is set.

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

Re: [tor-bugs] #26650 [Applications/Tor Browser]: Update d3dcompiler_47.dll to latest version in Tor Browser (10.0.15063.675)

[Tor Bug Tracker & Wiki]

#26650: Update d3dcompiler_47.dll to latest version in Tor Browser 
(10.0.15063.675)
--+---
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff60-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by ge):

 Replying to [ticket:26650 gk]:
 Hint: you no longer need to ship Microsoft libraries ;)

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

Re: [tor-bugs] #26650 [Applications/Tor Browser]: Update d3dcompiler_47.dll to latest version in Tor Browser (10.0.15063.675)

[Tor Bug Tracker & Wiki]

#26650: Update d3dcompiler_47.dll to latest version in Tor Browser 
(10.0.15063.675)
--+---
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff60-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by gk):

 Replying to [comment:5 ge]:
 > Replying to [ticket:26650 gk]:
 > Hint: you no longer need to ship Microsoft libraries ;)

 How so? What did suddenly change?

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

Re: [tor-bugs] #26650 [Applications/Tor Browser]: Update d3dcompiler_47.dll to latest version in Tor Browser (10.0.15063.675)

[Tor Bug Tracker & Wiki]

#26650: Update d3dcompiler_47.dll to latest version in Tor Browser 
(10.0.15063.675)
--+---
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff60-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by ge):

 Replying to [comment:6 gk]:
 > Replying to [comment:5 ge]:
 > > Replying to [ticket:26650 gk]:
 > > Hint: you no longer need to ship Microsoft libraries ;)
 >
 > How so? What did suddenly change?
 :) min reqs ;) - up-to-date Win 7+

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

Re: [tor-bugs] #27124 [Metrics/Onionoo]: Reading node statuses pointlessly initialises first seen millis as last seen millis

[Tor Bug Tracker & Wiki]

#27124: Reading node statuses pointlessly initialises first seen millis as last
seen millis
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Sure, those two lines can be merged into a single one.

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

Re: [tor-bugs] #26650 [Applications/Tor Browser]: Update d3dcompiler_47.dll to latest version in Tor Browser (10.0.15063.675)

[Tor Bug Tracker & Wiki]

#26650: Update d3dcompiler_47.dll to latest version in Tor Browser 
(10.0.15063.675)
--+---
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff60-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by ge):

 Long story short: due to Microsoft stupidity, they had to add the needed
 libraries as Windows components via Windows Update to all Win 7+
 distributions.

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

Re: [tor-bugs] #27133 [Applications/Quality Assurance and Testing]: tbb-testsuite: update useragent string in fp_navigator, useragent and settings tests

[Tor Bug Tracker & Wiki]

#27133: tbb-testsuite: update useragent string in fp_navigator, useragent and
settings tests
-+-
 Reporter:  boklm|  Owner:  boklm
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Quality Assurance and   |Version:
  Testing|
 Severity:  Normal   | Resolution:  fixed
 Keywords:  boklm201808, TorBrowserTeam201808,   |  Actual Points:
  tbb-testsuite  |
Parent ID:  #27105   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by boklm):

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


Comment:

 This is done with commits `d284c7987633de7a6e96f0bd41c452ccf0d9f48c`,
 `e27a9843e9d928438e15ca5885577d3b7eb0551a` and
 `b7a0a9c2eeace321bdb3e8fa6ed4936c0554898e`.

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

Re: [tor-bugs] #27121 [Metrics/ExoneraTor]: Release ExoneraTor 3.0.0

[Tor Bug Tracker & Wiki]

#27121: Release ExoneraTor 3.0.0
+--
 Reporter:  karsten |  Owner:  karsten
 Type:  task| Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  irl |Sponsor:
+--
Changes (by irl):

 * reviewer:   => irl


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

Re: [tor-bugs] #27122 [Applications/Quality Assurance and Testing]: tbb-testsuite: fix the slider_settings tests for esr60

[Tor Bug Tracker & Wiki]

#27122: tbb-testsuite: fix the slider_settings tests for esr60
-+-
 Reporter:  boklm|  Owner:  boklm
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Quality Assurance and   |Version:
  Testing|
 Severity:  Normal   | Resolution:  fixed
 Keywords:  boklm201808, TorBrowserTeam201808,   |  Actual Points:
  tbb-testsuite  |
Parent ID:  #27105   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by boklm):

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


Comment:

 This is done with commit `c65fe6fe87d878ad04ae206031b96aa634bcee49`.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27135 [Core Tor/sbws]: Write descriptor bandwidths average in raw results

[Tor Bug Tracker & Wiki]

#27135: Write descriptor bandwidths average in raw results
---+-
 Reporter:  juga   |  Owner:  juga
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  sbws 1.0 (MVP must)
Component:  Core Tor/sbws  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:  #27108
   Points: |   Reviewer:
  Sponsor: |
---+-
 Since generating bandwidth files in the way that Torflow does, implies
 using the average of the descriptors bandwidths over the time it performs
 measurements.
 sbws only obtain the descriptor bandwidth once, as commented in
 https://github.com/pastly/simple-bw-
 scanner/issues/182#issuecomment-412845969

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27136 [Applications/Quality Assurance and Testing]: tbb-testsuite: fix dom-objects-enumeration-worker test for esr60

[Tor Bug Tracker & Wiki]

#27136: tbb-testsuite: fix dom-objects-enumeration-worker test for esr60
-+-
 Reporter:  boklm|  Owner:  boklm
 Type:  task | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:   |Version:
  Applications/Quality Assurance |
  and Testing|   Keywords:  boklm201808,
 Severity:  Normal   |  TorBrowserTeam201808, tbb-testsuite
Actual Points:   |  Parent ID:  #27105
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 We need to fix the dom-objects-enumeration-worker test for the esr60
 changes.

 The test currently fails because the following DOM objects are now exposed
 in the Worker context:
 {{{
 AbortController
 AbortSignal
 CloseEvent
 ErrorEvent
 EventSource
 FileList
 PerformanceObserver
 PerformanceObserverEntryList
 PerformanceResourceTiming
 ProgressEvent
 StorageManager
 WebAssembly
 name
 onmessageerror
 origin
 }}}

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

Re: [tor-bugs] #27135 [Core Tor/sbws]: Write descriptor bandwidths average in raw results

[Tor Bug Tracker & Wiki]

#27135: Write descriptor bandwidths average in raw results
---+-
 Reporter:  juga   |  Owner:  juga
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  sbws 1.0 (MVP must)
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #27108 | Points:
 Reviewer: |Sponsor:
---+-

Comment (by pastly):

 Ahh great :/

 So we need to get all the relays' descriptors every hour and save (at
 least) the bandwidth lines in them? This is doable, and probably isn't
 that hard honestly. It's just probably going to have to be an entire
 separate thread that `sbws scanner` runs that does this work periodically.
 It doesn't make sense to me to put this data in the results files.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27137 [Applications/Quality Assurance and Testing]: tbb-testsuite: fix the navigation-timing test

[Tor Bug Tracker & Wiki]

#27137: tbb-testsuite: fix the navigation-timing test
-+-
 Reporter:  boklm|  Owner:  boklm
 Type:  task | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:   |Version:
  Applications/Quality Assurance |
  and Testing|   Keywords:  boklm201808,
 Severity:  Normal   |  TorBrowserTeam201808, tbb-testsuite
Actual Points:   |  Parent ID:  #27105
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 The navigation-timing test is currently failing with the following error:
 {{{
 test_navigation-timing.py test_navigation-
 timing.Test.test_navigation_timing
 SUITE-END | took 0s
 Using workspace for temporary data: "/home/user/tbb-
 testsuite/reports/r/aXFkPjw0CG/results-tor-browser-linux64-8.0a9_es-
 ES.tar.xz/navigation-timing_ws"
 mozversion application_buildid: 20180204020101
 mozversion application_display_name: Tor Browser
 mozversion application_id: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
 mozversion application_name: Firefox
 mozversion application_remotingname: firefox
 mozversion application_vendor: Mozilla
 mozversion application_version: 60.1.0
 mozversion platform_buildid: 20180204020101
 mozversion platform_version: 60.1.0
 Application command: /home/user/tbb-testsuite/tmp/w2gSJZPwUj/tor-
 browser_es-ES/Browser/ff_wrapper -no-remote -marionette -profile
 /home/user/tbb-testsuite/reports/r/aXFkPjw0CG/results-tor-browser-
 linux64-8.0a9_es-ES.tar.xz/navigation-timing_ws/profile.default-1534249749
 Profile path is /home/user/tbb-testsuite/reports/r/aXFkPjw0CG/results-tor-
 browser-linux64-8.0a9_es-ES.tar.xz/navigation-
 timing_ws/profile.default-1534249749
 Starting fixture servers
 Fixture server listening on http://127.0.0.1:35413/
 Fixture server listening on https://127.0.0.1:32829/
 e10s is enabled
 mozversion application_buildid: 20180204020101
 mozversion application_display_name: Tor Browser
 mozversion application_id: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
 mozversion application_name: Firefox
 mozversion application_remotingname: firefox
 mozversion application_vendor: Mozilla
 mozversion application_version: 60.1.0
 mozversion platform_buildid: 20180204020101
 mozversion platform_version: 60.1.0
 SUITE-START | Running 1 tests
 TEST-START | test_navigation-timing.py Test.test_navigation_timing
 Failed to gather test failure debug:
 stacktrace:
 WebDriverError@chrome://marionette/content/error.js:178:5
 UnexpectedAlertOpenError@chrome://marionette/content/error.js:507:5
 assert.that/<@chrome://marionette/content/assert.js:405:13
 assert.noUserPrompt@chrome://marionette/content/assert.js:178:3
 
GeckoDriver.prototype._assertAndDismissModal@chrome://marionette/content/driver.js:3203:5
 
GeckoDriver.prototype.getPageSource@chrome://marionette/content/driver.js:1154:3
 despatch@chrome://marionette/content/server.js:293:20
 execute@chrome://marionette/content/server.js:267:11
 onPacket/<@chrome://marionette/content/server.js:242:15
 onPacket@chrome://marionette/content/server.js:241:8
 _onJSONObjectReady/<@chrome://marionette/content/transport.js:500:9
 openModalWindow@jar:file:///home/user/tbb-testsuite/tmp/w2gSJZPwUj
 /tor-browser_es-ES/Browser/omni.ja!/components/nsPrompter.js:353:5
 openPrompt@jar:file:///home/user/tbb-testsuite/tmp/w2gSJZPwUj/tor-
 browser_es-ES/Browser/omni.ja!/components/nsPrompter.js:563:9
 confirmEx@jar:file:///home/user/tbb-testsuite/tmp/w2gSJZPwUj/tor-
 browser_es-ES/Browser/omni.ja!/components/nsPrompter.js:704:9
 confirmEx@jar:file:///home/user/tbb-testsuite/tmp/w2gSJZPwUj/tor-
 browser_es-ES/Browser/omni.ja!/components/nsPrompter.js:74:16
 _promptForLanguagePreference@resource://gre/modules/LanguagePrompt.jsm:177:20
 _handleHttpOnModifyRequest@resource://gre/modules/LanguagePrompt.jsm:156:5
 observe@resource://gre/modules/LanguagePrompt.jsm:47:9

 TEST-UNEXPECTED-FAIL | test_navigation-timing.py
 Test.test_navigation_timing | AssertionError: secureConnectionStart !=
 None
 Traceback (most recent call last):
   File "/home/user/tbb-testsuite/virtualenv-
 marionette-4.3.0/local/lib/python2.7/site-
 
packages/marionette_harness-4.3.0-py2.7.egg/marionette_harness/marionette_test/testcases.py",
 line 156, in run
 testMethod()
   File "/home/user/tbb-testsuite/marionette/tor_browser_tests
 /test_navigation-timing.py", line 52, in test_navigation_timing
 script_args=[name, val]), msg=err_msg)
 TEST-INFO took 451ms

 SUMMARY
 ---
 passed: 0
 failed: 1
 todo: 0

 FAILED TESTS
 ---
 test_navigation-timing.py test_navigation-
 timing.Test.test_navigation_timing
 SUITE-END | took 0s
 }}}

--
Ticket URL: 

[tor-bugs] #27138 [Metrics/Relay Search]: display timestamp and version information on page with no results

[Tor Bug Tracker & Wiki]

#27138: display timestamp and version information on page with no results
--+--
 Reporter:  nusenu|  Owner:  metrics-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 "
 Information for relays was published: 2018-08-14 11:00:00 UTC.
 Information for bridges was published: 2018-08-14 10:42:38 UTC.

 Onionoo version: 6.2/7d73a0c
 "

 this information is not displayed on the page if no result is found, but
 especially in that cases it would be important to know

 https://metrics.torproject.org/rs.html#search/NOTEXISTING

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

Re: [tor-bugs] #27138 [Metrics/Relay Search]: display timestamp and version information on page with no results

[Tor Bug Tracker & Wiki]

#27138: display timestamp and version information on page with no results
--+--
 Reporter:  nusenu|  Owner:  irl
 Type:  enhancement   | Status:  accepted
 Priority:  Medium|  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by irl):

 * owner:  metrics-team => irl
 * 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] #26863 [Metrics/Relay Search]: display onionoo and RS version on RS pages

[Tor Bug Tracker & Wiki]

#26863: display onionoo and RS version on RS pages
--+--
 Reporter:  nusenu|  Owner:  metrics-team
 Type:  enhancement   | Status:  reopened
 Priority:  Medium|  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #27064| Points:
 Reviewer:|Sponsor:
--+--
Changes (by nusenu):

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


Comment:

 the RS version is not shown on the page, is 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] #21787 [Applications/Tor Browser]: Make sure exposing the calendar information does not leak the locale

[Tor Bug Tracker & Wiki]

#21787: Make sure exposing the calendar information does not leak the locale
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_revision
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-fingerprinting, ff60-esr |  Actual Points:
  TorBrowserTeam201808   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-fingerprinting, ff60-esr TorBrowserTeam201808R => tbb-
 fingerprinting, ff60-esr TorBrowserTeam201808
 * status:  needs_review => needs_revision


Comment:

 Replying to [comment:7 arthuredelstein]:
 > This API remains chrome-only. I think there's no intention to expose it
 to content. So I would suggest closing this ticket.

 Ugh, that took me quite some time... What do you mean with "chrome-only"?
 It seems content might be able to get a user to trigger the API via the
 `` element, no? See  https://blog.nightly.mozilla.org/2017/06/12
 /datetime-inputs-enabled-on-nightly/ for some examples: there is
 definitely a localization component that is exposed to content. Not sure
 if JS can made to access that directly but I bet that at least the
 resulting rendering differences might give a hint about a possible used
 locale. This is "no issue" for the Tor Browser alpha but only as our
 content policy hack breaks this feature. We are about to remove it,
 though.

 See: https://bugzilla.mozilla.org/show_bug.cgi?id=1283384 and
 https://bugzilla.mozilla.org/show_bug.cgi?id=1329589 for some context.

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

Re: [tor-bugs] #27135 [Core Tor/sbws]: Write descriptor bandwidths average in raw results

[Tor Bug Tracker & Wiki]

#27135: Write descriptor bandwidths average in raw results
---+-
 Reporter:  juga   |  Owner:  juga
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  sbws 1.0 (MVP must)
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #27108 | Points:
 Reviewer: |Sponsor:
---+-

Comment (by juga):

 i'm not sure we should get it every hour, i haven't find yet how
 frequently torflow does.
 Teor, do you know it?, i found when it reads it
 https://gitweb.torproject.org/pytorctl.git/tree/SQLSupport.py#n421, but
 not when it stores it.

 If we need to obtain the descriptor bws more frequently that once/day, i
 do would store them in the results files, as a list for relay, to keep the
 same logic we're doing with the rest of values and to avoid to have to
 read/write yet another file with its locks and so.
 Would not be possible to just obtained from somewhere as
 https://github.com/pastly/simple-bw-
 scanner/blob/master/sbws/core/scanner.py#L248?.

 Actually, i don't know right now why relay doesn't have the updated
 descriptor there. Because we called both `Relay` in resultdump and
 relaylist, i'm not sure where https://github.com/pastly/simple-bw-
 scanner/blob/master/sbws/lib/relaylist.py#L206 is being called.

 Maybe it's enough to store once per file, but for some reason i haven't
 figure yet, all days have the same descriptor bw.

 As an example, this are the descriptor bws from 4 files from 2 relays:
 relay 1: [9216000, 9216000, 9216000]
 relay 2: [1073741824, 1073741824, 1073741824]

 Since you know better this part of the code, would you feel like to check
 why is 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] #27135 [Core Tor/sbws]: Write descriptor bandwidths average in raw results

[Tor Bug Tracker & Wiki]

#27135: Write descriptor bandwidths average in raw results
---+-
 Reporter:  juga   |  Owner:  juga
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  sbws 1.0 (MVP must)
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #27108 | Points:
 Reviewer: |Sponsor:
---+-

Comment (by juga):

 If you think you can implement this fast and feel like, feel free to
 reassign it to you and work on it, since i might be afk tomorrow.

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

Re: [tor-bugs] #26863 [Metrics/Relay Search]: display onionoo and RS version on RS pages

[Tor Bug Tracker & Wiki]

#26863: display onionoo and RS version on RS pages
--+--
 Reporter:  nusenu|  Owner:  metrics-team
 Type:  enhancement   | Status:  reopened
 Priority:  Medium|  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #27064| Points:
 Reviewer:|Sponsor:
--+--

Comment (by irl):

 RS doesn't have versions.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27139 [Core Tor/Tor]: macOS i386 fails time unit testa

[Tor Bug Tracker & Wiki]

#27139: macOS i386 fails time unit testa
--+-
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  regression, macos, i386
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 {{{
 circuitmux/compute_ticks: [forking]
   FAIL src/test/test_circuitmux.c:109: assert(rem OP_LT .15001):
 0.1505 vs 0.15
   [compute_ticks FAILED]
 }}}

 {{{
 mainloop/update_time_jumps: [forking]
   FAIL src/test/test_mainloop.c:115: expected log to not contain entries
 Captured logs:
 1. notice: "Your system clock just jumped 1800 seconds forward;
 assuming established circuits no longer work.\n"

   [update_time_jumps FAILED]
 }}}

 Should we set up macOS i386 CI to detect issues like this?
 Or should we remove macOS i386 from our supported platforms?
 (Apple won't support i386 in the next macOS, so in ~3 years time, we won't
 need to support 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] #27124 [Metrics/Onionoo]: Reading node statuses pointlessly initialises first seen millis as last seen millis

[Tor Bug Tracker & Wiki]

#27124: Reading node statuses pointlessly initialises first seen millis as last
seen millis
-+--
 Reporter:  irl  |  Owner:  irl
 Type:  defect   | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by irl):

 * owner:  metrics-team => irl
 * cc: metrics-team (added)
 * 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] #27124 [Metrics/Onionoo]: Reading node statuses pointlessly initialises first seen millis as last seen millis

[Tor Bug Tracker & Wiki]

#27124: Reading node statuses pointlessly initialises first seen millis as last
seen millis
-+--
 Reporter:  irl  |  Owner:  irl
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by irl):

 * status:  accepted => needs_review


Comment:

 Please review
 
[[https://gitweb.torproject.org/user/irl/onionoo.git/commit/?h=task/27124&id=6c94482adbd651d787ecc3c32d5d1d79395db7af|trivial
 commit 6c94482 in my task/27124 branch]].

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

Re: [tor-bugs] #27050 [Metrics/Onionoo]: Reverse DNS lookups are still slow

[Tor Bug Tracker & Wiki]

#27050: Reverse DNS lookups are still slow
-+--
 Reporter:  irl  |  Owner:  irl
 Type:  defect   | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 Please review the 2 commits in my
 
[[https://gitweb.torproject.org/user/irl/onionoo.git/log/?h=task/27050|task/27050]]
 branch.

 Checks and tests pass, and I have tested on a real status directory.

 This change removes the "host_name" field from details documents and so
 should be deployed along with Onionoo protocol version 7.0.

 If these changes are ok, set back to needs_review anyway for me to write a
 changelog entry.

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

Re: [tor-bugs] #27050 [Metrics/Onionoo]: Reverse DNS lookups are still slow

[Tor Bug Tracker & Wiki]

#27050: Reverse DNS lookups are still slow
-+--
 Reporter:  irl  |  Owner:  irl
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by irl):

 * 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] #24056 [Applications/Tor Browser]: UI locale is detectable by button width

[Tor Bug Tracker & Wiki]

#24056: UI locale is detectable by button width
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  tbb-fingerprinting,  |  Actual Points:
  TorBrowserTeam201808R  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 Replying to [comment:6 arthuredelstein]:
 > Here's the revised patch:
 > https://github.com/arthuredelstein/tor-browser/commit/24056+1

 It seems we don't need to potentially adjust `aFile` in
 {{{
 nsresult nsContentUtils::FormatLocalizedString(
   PropertiesFile aFile,
   const char* aKey,
   const nsTArray&
 aParamArray,
   nsAString& aResult)
 }}}
 as it does not get touched in it but rather gets passed on.

 I guess we are safe regarding `GetLocalizedEllipsis()`? At least I hope
 so, assuming the localization folks adhered to Mozilla's advice to use
 `\u2026` for 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] #24056 [Applications/Tor Browser]: UI locale is detectable by button width

[Tor Bug Tracker & Wiki]

#24056: UI locale is detectable by button width
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_revision
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  tbb-fingerprinting,  |  Actual Points:
  TorBrowserTeam201808   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * status:  needs_review => needs_revision
 * keywords:  tbb-fingerprinting, TorBrowserTeam201808R => tbb-
 fingerprinting, TorBrowserTeam201808


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

Re: [tor-bugs] #10507 [Applications/Tor Browser]: firefox 24.0 in tbb 3.5 is leaking referring page data

[Tor Bug Tracker & Wiki]

#10507: firefox 24.0 in tbb 3.5 is leaking referring page data
+--
 Reporter:  unclejed613 |  Owner:  tbb-team
 Type:  defect  | Status:
|  needs_information
 Priority:  Very High   |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-3.0, tbb-firefox-patch  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by traumschule):

 * status:  new => needs_information


Comment:

 is this reproducible with a current TBB?

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

Re: [tor-bugs] #10506 [Applications/Orbot]: Unable to start Tor: Unable to start Tor

[Tor Bug Tracker & Wiki]

#10506: Unable to start Tor: Unable to start Tor
+
 Reporter:  jack80  |  Owner:  n8fr8
 Type:  defect  | Status:  needs_information
 Priority:  Very High   |  Milestone:
Component:  Applications/Orbot  |Version:  Tor: 0.2.3.7-alpha
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+
Changes (by traumschule):

 * status:  new => needs_information


Comment:

 if this is not reproducible and the user is gone, closing?

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

Re: [tor-bugs] #25488 [Webpages/Styleguide]: Add an example for navigation within the site

[Tor Bug Tracker & Wiki]

#25488: Add an example for navigation within the site
-+--
 Reporter:  cypherpunks  |  Owner:  hiro
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Webpages/Styleguide  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25404   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 A mock up with the second-level navigation can be seen
 [[https://marvelapp.com/4471ig9/screen/38745637|here]].

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

Re: [tor-bugs] #26961 [Applications/Tor Browser]: implement new user onboarding

[Tor Bug Tracker & Wiki]

#26961: implement new user onboarding
--+--
 Reporter:  mcs   |  Owner:  mcs
 Type:  defect| Status:  needs_review
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201808R |  Actual Points:
Parent ID:  #25695| Points:
 Reviewer:|Sponsor:
--+--

Comment (by mcs):

 Replying to [comment:7 antonela]:
 > Replying to [comment:5 mcs]:
 > > Here are a few notes for the UX Team / Antonela:
 >
 > > * The onboarding requires a window that is at least 960 pixels wide;
 otherwise, it is not shown. Hopefully most of our users have a display
 that is wide enough.
 >
 > Is this a Firefox's media query break up? What happens with smaller
 screens? We could think in a responsive version for next iteration :)

 With smaller screens the onboarding icon and prompt are not displayed. I
 think this is just a limitation of the Firefox 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] #27135 [Core Tor/sbws]: Write descriptor bandwidths average in raw results

[Tor Bug Tracker & Wiki]

#27135: Write descriptor bandwidths average in raw results
---+-
 Reporter:  juga   |  Owner:  juga
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  sbws 1.0 (MVP must)
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #27108 | Points:
 Reviewer: |Sponsor:
---+-

Comment (by juga):

 Replying to [comment:2 juga]:
 > i'm not sure we should get it every hour, i haven't find yet how
 frequently torflow does.

 though it would make sense if torflow is getting them every hour.

 > Would not be possible to just obtained from somewhere as
 https://github.com/pastly/simple-bw-
 scanner/blob/master/sbws/core/scanner.py#L248?.

 hmm, it seems to be correctly getting it from there, but we still only
 measure the relay around once/day

 > Actually, i don't know right now why relay doesn't have the updated
 descriptor there. Because we called both `Relay` in resultdump and
 relaylist, i'm not sure where https://github.com/pastly/simple-bw-
 scanner/blob/master/sbws/lib/relaylist.py#L206 is being called.

 Maybe it's just coincidence that descriptor bws were the same for all the
 relays measured here, at the time the were measured.

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

Re: [tor-bugs] #27139 [Core Tor/Tor]: macOS i386 fails time unit testa

[Tor Bug Tracker & Wiki]

#27139: macOS i386 fails time unit testa
-+
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  regression, macos, i386  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by nickm):

 Are these intermittent or consistent?

 I'd be okay with or without OSX i386 CI.

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

Re: [tor-bugs] #26961 [Applications/Tor Browser]: implement new user onboarding

[Tor Bug Tracker & Wiki]

#26961: implement new user onboarding
--+--
 Reporter:  mcs   |  Owner:  mcs
 Type:  defect| Status:  needs_review
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201808R |  Actual Points:
Parent ID:  #25695| Points:
 Reviewer:|Sponsor:
--+--

Comment (by mcs):

 We made a few small improvements and also incorporated the final
 onboarding artwork. Here are the commits to review:

 One Torbutton patch:
 
​https://gitweb.torproject.org/user/brade/torbutton.git/commit/?h=bug26961-01&id=4c69fedc9a0a927aea5d29e5060acb0df7016fef

 and two tor-browser patches:
 https://gitweb.torproject.org/user/brade/tor-
 browser.git/commit/?h=bug26961-02&id=e10e27a50893c473ed905a50715f35824185a87e

 https://gitweb.torproject.org/user/brade/tor-
 browser.git/commit/?h=bug26961-02&id=b8dca4037d4dba3bbc27ee9989a09928446085f1

 (the tor-browser patches are on a branch named bug26961-02 which also
 contain the commits for #27082).

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

Re: [tor-bugs] #25490 [Webpages/Styleguide]: Give clear guidelines for the page footer

[Tor Bug Tracker & Wiki]

#25490: Give clear guidelines for the page footer
-+--
 Reporter:  cypherpunks  |  Owner:  hiro
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Webpages/Styleguide  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25404   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 The current footer used on support portal will be used across all portals.
 This should be added as an example (possibly cleaned up) to the styleguide
 and then this ticket can be closed. Probably we should warn people against
 using this exact footer unless they are Tor Project people, as most of the
 rest of the styleguide is easily reused by others.

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

Re: [tor-bugs] #25641 [Webpages/Website]: content for torproject.org

[Tor Bug Tracker & Wiki]

#25641: content for torproject.org
--+--
 Reporter:  isabela   |  Owner:  isabela
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  website redesign
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team,  |  Actual Points:
Parent ID:  #24131| Points:
 Reviewer:|Sponsor:
--+--
Changes (by antonela):

 * cc: stephw (added)


Old description:

> This ticket is to track the work to create content and review content
> related to the new torproject.org site

New description:

 This ticket is to track the work to create content and review content
 related to the new torproject.org site


 https://storm.torproject.org/shared/wyGr33d_9LtKwtleVpg5kOvP_XM2S2Zm01UpHgrWYna

--

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

Re: [tor-bugs] #26863 [Metrics/Relay Search]: display onionoo and RS version on RS pages

[Tor Bug Tracker & Wiki]

#26863: display onionoo and RS version on RS pages
--+--
 Reporter:  nusenu|  Owner:  metrics-team
 Type:  enhancement   | Status:  reopened
 Priority:  Medium|  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #27064| Points:
 Reviewer:|Sponsor:
--+--

Comment (by nusenu):

 how about displaying the git commit id?

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

Re: [tor-bugs] #25641 [Webpages/Website]: content for torproject.org

[Tor Bug Tracker & Wiki]

#25641: content for torproject.org
--+--
 Reporter:  isabela   |  Owner:  isabela
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  website redesign
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team,  |  Actual Points:
Parent ID:  #24131| Points:
 Reviewer:|Sponsor:
--+--
Changes (by antonela):

 * cc: stephw (removed)
 * cc: steph (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] #26973 [Core Tor/Tor]: Privcount blinding and encryption: add rustfmt CI check

[Tor Bug Tracker & Wiki]

#26973: Privcount blinding and encryption: add rustfmt CI check
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  privcount, 035-roadmap-master, 035   |  Actual Points:
  -triaged-in-20180711, rust |
Parent ID:  #25669   | Points:
 Reviewer:  nickm|Sponsor:
-+-
Changes (by nickm):

 * status:  needs_review => merge_ready


Comment:

 This looks okay, except for the fact that the rustfmt commit itself will
 have conflicts with my patch series currently under review.

 So my current plan here is that, once that other patch series is merged,
 we should cherry-pick everything from this branch except for the rustfmt
 commit (`bdc2db60153ef9c3044b72309cc1b35f45f85618`), and then re-run
 rustfmt separately.

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

Re: [tor-bugs] #27139 [Core Tor/Tor]: macOS i386 fails time unit tests (was: macOS i386 fails time unit testa)

[Tor Bug Tracker & Wiki]

#27139: macOS i386 fails time unit tests
-+
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  regression, macos, i386  |  Actual Points:
Parent ID:   | 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] #9809 [Applications/Tor Browser]: Re-disable Ctypes in TBB 7.0

[Tor Bug Tracker & Wiki]

#9809: Re-disable Ctypes in TBB 7.0
+--
 Reporter:  mikeperry   |  Owner:  tbb-team
 Type:  enhancement | Status:  new
 Priority:  High|  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-3.0, tbb-firefox-patch  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by ct):

 Replying to [comment:7 gk]:
 > That's for WebExtensions, yes, but the blocker here is actually #10137
 and I am not aware that Firefox does work now without ctypes enabled, but
 would be happy to be proven wrong (ideally with links to Mozilla bugs that
 fixed this).
 Mozilla removed `--disable-ctypes` in https://hg.mozilla.org/mozilla-
 central/rev/2938c8a38f2b and support for anything other than WebExtensions
 in Firefox 57. So, this ticket and #6152 (despite its name), created to
 prevent arbitrary code execution in add-ons, look obsolete 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] #27109 [Core Tor/Tor]: Tor 0.3.5.0-alpha-dev: [warn] connection_mark_unattached_ap_(): Bug: stream (marked at ../src/core/or/connection_edge.c:2605) sending two socks replies?

[Tor Bug Tracker & Wiki]

#27109: Tor 0.3.5.0-alpha-dev: [warn] connection_mark_unattached_ap_(): Bug: 
stream
(marked at ../src/core/or/connection_edge.c:2605) sending two socks
replies?
--+
 Reporter:  traumschule   |  Owner:  rl1987
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by rl1987):

 How are using tor when you're getting these log messages? Are you sure
 you're not trying to use it as HTTP proxy?

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

Re: [tor-bugs] #27109 [Core Tor/Tor]: Tor 0.3.5.0-alpha-dev: [warn] connection_mark_unattached_ap_(): Bug: stream (marked at ../src/core/or/connection_edge.c:2605) sending two socks replies?

[Tor Bug Tracker & Wiki]

#27109: Tor 0.3.5.0-alpha-dev: [warn] connection_mark_unattached_ap_(): Bug: 
stream
(marked at ../src/core/or/connection_edge.c:2605) sending two socks
replies?
--+
 Reporter:  traumschule   |  Owner:  rl1987
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by rl1987):

 * 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] #26514 [Applications/Tor Browser]: intermittent updater failures on Win64 (Error 19)

[Tor Bug Tracker & Wiki]

#26514: intermittent updater failures on Win64 (Error 19)
--+--
 Reporter:  mcs   |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201808R |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by mcs):

 * status:  new => needs_review
 * keywords:  TorBrowserTeam201808 => TorBrowserTeam201808R


Comment:

 Replying to [comment:19 jacek]:
 > As a less radical solution could be using fseek64 and ftello64. Those
 are much thinner wrappers in mingw-64 around msvcrt.dll. You could try
 that by changing defines in mar_private.h

 Thank you for your analysis and for this suggestion. It appears to solve
 the problem nicely. After reading the other code (ftelli64 and _fseeki64),
 it is difficult to say where the problem is but some aspects seem to rely
 on internal Microsoft flags, etc. and certainly there is complexity there
 (as you said). Anyway, here is a patch that works for Kathy and me:
 https://gitweb.torproject.org/user/brade/tor-
 browser.git/commit/?h=bug26514-01&id=c2720b2274e51eb76b91e5f6a5f2a82bdfaf8013

 We tested on an up-to-date Windows 10 system. 200 incremental updates and
 200 complete updates all completed without any signature verification
 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] #27135 [Core Tor/sbws]: Write descriptor bandwidths average in raw results

[Tor Bug Tracker & Wiki]

#27135: Write descriptor bandwidths average in raw results
---+-
 Reporter:  juga   |  Owner:  juga
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  sbws 1.0 (MVP must)
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #27108 | Points:
 Reviewer: |Sponsor:
---+-

Comment (by pastly):

 Replying to [comment:2 juga]:
 > As an example, this are the descriptor bws from 4 files from 2 relays:
 > relay 1: [9216000, 9216000, 9216000]
 > relay 2: [1073741824, 1073741824, 1073741824]
 >
 > Since you know better this part of the code, would you feel like to
 check why is that?

 I downloaded your sbws datadir and wrote a little script to print how
 often a relay has a list of saved `relay_average_bandwidth` containing
 more than one unique element.

 It found that 1868/7999 relays had `relay_average_bandwidth` values that
 weren't all the same (118/7326 if you only look at success results). I'm
 guessing relays don't update this value in their descriptors very often.

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

Re: [tor-bugs] #27135 [Core Tor/sbws]: Write descriptor bandwidths average in raw results

[Tor Bug Tracker & Wiki]

#27135: Write descriptor bandwidths average in raw results
---+-
 Reporter:  juga   |  Owner:  juga
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  sbws 1.0 (MVP must)
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #27108 | Points:
 Reviewer: |Sponsor:
---+-
Changes (by pastly):

 * Attachment "toy.py" 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] #25152 [Core Tor/Tor]: Try to call less circuitmux_find_map_entry()

[Tor Bug Tracker & Wiki]

#25152: Try to call less circuitmux_find_map_entry()
-+-
 Reporter:  dgoulet  |  Owner:  neel
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  performance, tor-relay,  |  Actual Points:
  034-triage-20180328, 034-removed-20180328  |
Parent ID:   | Points:
 Reviewer:  mikeperry|Sponsor:
-+-

Comment (by nickm):

 I've left a review on the PR; Mike is planning to do so as well.

 In general, I think that the approach is a good start, but that a more
 thorough approach might be called for in order to keep the code clean.
 I'm not sure it's a good idea to proliferate these "hashent" usages
 throughout our codebase, I'd like to take a step back.

 Before we optimize too much we should ask ourselves, "Is this hashtable
 really necessary?"  After all, there are at most two of these hash entries
 for each circuit, and we are looking them up _from_ the circuit. Perhaps a
 better solution would be to give each circuit a couple of pointers to this
 information, to make lookup into an O(1) operation.  Maybe after we were
 done, we might find that the hashtable wasn't necessary at all.

 Of course, we would need to manage lifetime issues carefully here.

 I am not taking a position about whether the change I suggest above should
 be done ''instead of'' or ''after'' this change; I would like a second
 opinion from mike about that -- and ideally from dgoulet too, once he is
 back online.

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

Re: [tor-bugs] #26398 [Core Tor/Tor]: feature gate testing C code from Rust for now

[Tor Bug Tracker & Wiki]

#26398: feature gate testing C code from Rust for now
--+
 Reporter:  isis  |  Owner:  isis
 Type:  defect| Status:
  |  needs_information
 Priority:  Very High |  Milestone:  Tor:
  |  0.3.5.x-final
Component:  Core Tor/Tor  |Version:  Tor:
  |  0.3.3.1-alpha
 Severity:  Normal| Resolution:
 Keywords:  rust, tor-test, fast-fix, tor-ci  |  Actual Points:
Parent ID:| Points:  1
 Reviewer:  nickm |Sponsor:
  |  Sponsor8-can
--+

Comment (by chelseakomlo):

 As an update from https://trac.torproject.org/projects/tor/ticket/25386,
 it looks like only doctests and compiling with sanitizers are not working
 as expected.

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

Re: [tor-bugs] #27109 [Core Tor/Tor]: Tor 0.3.5.0-alpha-dev: [warn] connection_mark_unattached_ap_(): Bug: stream (marked at ../src/core/or/connection_edge.c:2605) sending two socks replies?

[Tor Bug Tracker & Wiki]

#27109: Tor 0.3.5.0-alpha-dev: [warn] connection_mark_unattached_ap_(): Bug: 
stream
(marked at ../src/core/or/connection_edge.c:2605) sending two socks
replies?
--+
 Reporter:  traumschule   |  Owner:  rl1987
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by traumschule):

 thanks for looking into this!

 I am able to reproduce it with firefox using following proxy settings:
 {{{
 HTTP Proxy: 127.0.0.1:9099
 SSL Proxy: 127.0.0.1:9099
 FTP Proxy: 127.0.0.1:9099
 SOCKS Host: 127.0.0.1:9050
 }}}
 /etc/tor/torrc
 {{{
 SocksPort 9050
 HTTPTunnelPort 9099
 }}}
 I noticed the helpful message by tor using the SOCKS port for TLS ("SSL
 Proxy: 127.0.0.1:9050"):
 {{{
 [warn] Socks version 67 not recognized. (This port is not an HTTP proxy;
 did you want to use
 HTTPTunnelPort?)
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27140 [Applications/Tor Browser]: TBA: Bump Target SDK Version to 26

[Tor Bug Tracker & Wiki]

#27140: TBA: Bump Target SDK Version to 26
--+
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-mobile
Actual Points:|  Parent ID:  #5709
   Points:|   Reviewer:
  Sponsor:|
--+
 Mozilla already landed this in bug
 [https://bugzilla.mozilla.org/show_bug.cgi?id=1352015 1352015]. We should
 backport these patches.

 https://hg.mozilla.org/mozilla-central/rev/60e83456adb9
 https://hg.mozilla.org/mozilla-central/rev/2e9ace719b06

 We should merge these before the second alpha release.

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

Re: [tor-bugs] #26863 [Metrics/Relay Search]: display onionoo and RS version on RS pages

[Tor Bug Tracker & Wiki]

#26863: display onionoo and RS version on RS pages
--+--
 Reporter:  nusenu|  Owner:  metrics-team
 Type:  enhancement   | Status:  reopened
 Priority:  Medium|  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #27064| Points:
 Reviewer:|Sponsor:
--+--

Comment (by irl):

 This would force us to build metrics-web from git, but we distribute
 tarballs without the git information and expect the build to be
 reproducible using this. We would break our reproducible builds if
 different things happened building for the tarball vs from git. Knowing
 the date and time of the request should be enough for a member of the
 metrics team to identify what version of the code was running at the time.

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

Re: [tor-bugs] #27121 [Metrics/ExoneraTor]: Release ExoneraTor 3.0.0

[Tor Bug Tracker & Wiki]

#27121: Release ExoneraTor 3.0.0
+-
 Reporter:  karsten |  Owner:  karsten
 Type:  task| Status:  merge_ready
 Priority:  Medium  |  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  irl |Sponsor:
+-
Changes (by irl):

 * status:  needs_review => merge_ready


Comment:

 Looks good to me.

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

Re: [tor-bugs] #27129 [Applications/Tor Browser]: Add ca, ga, id, is, nb locales for Tor Browser (was: Add ca, ga, id, nb, pt locales for Tor Browser)

[Tor Bug Tracker & Wiki]

#27129: Add ca, ga, id, is, nb locales for Tor Browser
--+--
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-localization  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by arthuredelstein):

 We have 7 that are at 100% or 99% translated: bn-BD, ca, ga, id, is, nb,
 pt.

 bn-BD has a strange bug, and pt is lower priority because we already have
 pt-BR. So I'd propose for our next batch of new locales we add `ca, ga,
 id, is, nb`.

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

Re: [tor-bugs] #27129 [Applications/Tor Browser]: Add ca, ga, id, is, nb locales for Tor Browser

[Tor Bug Tracker & Wiki]

#27129: Add ca, ga, id, is, nb locales for Tor Browser
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-localization,|  Actual Points:
  TorBrowserTeam2018R|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by arthuredelstein):

 * keywords:  tbb-localization => tbb-localization, TorBrowserTeam2018R
 * status:  new => needs_review


Comment:

 Here are patches for review:

 https://github.com/arthuredelstein/torbutton/commit/27129
 https://github.com/arthuredelstein/tor-launcher/commit/27129
 https://github.com/arthuredelstein/tor-browser-build/commit/27129

 I'm still awaiting the results of a build, but I did a manual test with
 langpacks and all 5 locales worked.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27141 [Applications/Tor Browser]: Backport TLS1.3 patches

[Tor Bug Tracker & Wiki]

#27141: Backport TLS1.3 patches
-+-
 Reporter:  sysrqb   |  Owner:  tbb-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  tbb-performance,
 Severity:  Normal   |  ff60-esr
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Consider backporting TLS 1.3 patches for NSS and Firefox (after they
 land). It seems like almost all the patches are within NSS.

 https://bugzilla.mozilla.org/show_bug.cgi?id=1057463

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27142 [- Select a component]: Unable to clear history / history remains after closing browser

[Tor Bug Tracker & Wiki]

#27142: Unable to clear history / history remains after closing browser
--+--
 Reporter:  AppleCrisp|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:  browsing_history
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Normally Tor records no browsing history whatsoever upon close but the
 website Gelbooru.com permanently added this to my browsing history.  Only
 removing and reinstalling Tor fixed the problem.

 
https://pt.trafficjunky.net/pt_click?ad_id=-1_537849_0&req=-1&rot=537849&zone=0&prod=681&lp=https%3A%2F%2Fwww.nutaku.net%2Fsignup%2Flanding
 %2Fnaughty-
 
kingdom%2F1%2F%3Fats%3DeyJhIjo3MSwiYyI6NTYxMDQ2NDEsIm4iOjEsInMiOjEsImUiOjg1MDMsInAiOjR9%26utm_source%3DGelbooru_adtool%26utm_medium%3D852605%26utm_campaign%3DNutaku_Gelbooru_Popunder_NK_LP1_852605&onlyseed=1&impid=--

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

Re: [tor-bugs] #18361 [Applications/Tor Browser]: Issues with corporate censorship and mass surveillance

[Tor Bug Tracker & Wiki]

#18361: Issues with corporate censorship and mass surveillance
--+--
 Reporter:  ioerror   |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:  1000 light years
 Reviewer:|Sponsor:
--+--

Comment (by traumschule):

 I noticed that this ticket contrary to others never stops loading. Looking
 at the network log it requests following external resources:

 https://i.imgur.com/qQH09pz.png
 https://i.imgur.com/zWhSuTg.png
 https://pbs.twimg.com/media/CcGst-OUkAA0qxc.jpg:large
 https://3j3j5hyf44hgggod.onion/bbo8ui6i.png
 https://www.crimeflare.com/gifs/daddy5.jpg
 https://bitland.net/recaptcha-001.jpg

 Trac seems to reload them for the preview. But even without typing
 anything the tab keeps loading.

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

Re: [tor-bugs] #27044 [Core Tor/Tor]: be more strict in parsing HiddenServicePort

[Tor Bug Tracker & Wiki]

#27044: be more strict in parsing HiddenServicePort
--+--
 Reporter:  toralf|  Owner:  (none)
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by rl1987):

 * status:  new => needs_review


Comment:

 https://github.com/torproject/tor/pull/274

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

Re: [tor-bugs] #27139 [Core Tor/Tor]: macOS i386 fails time unit tests

[Tor Bug Tracker & Wiki]

#27139: macOS i386 fails time unit tests
-+
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  regression, macos, i386  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by rl1987):

 * cc: rl1987 (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] #27141 [Applications/Tor Browser]: Backport TLS1.3 patches

[Tor Bug Tracker & Wiki]

#27141: Backport TLS1.3 patches
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-security  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by sysrqb):

 * keywords:  tbb-performance, ff60-esr => tbb-security


Old description:

> Consider backporting TLS 1.3 patches for NSS and Firefox (after they
> land). It seems like almost all the patches are within NSS.
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=1057463

New description:

 Consider backporting TLS 1.3 patches for NSS and Firefox (after they land)
 onto Tor Browser 8 (ESR60). It seems like almost all the patches are
 within NSS.

 https://bugzilla.mozilla.org/show_bug.cgi?id=1057463

--

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

Re: [tor-bugs] #18820 [Applications/Tor Browser]: Integrate code signing into the release process

[Tor Bug Tracker & Wiki]

#18820: Integrate code signing into the release process
-+-
 Reporter:  gk   |  Owner:  gk
 Type:  task | Status:
 |  assigned
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  tbb-6.0a5, TorBrowserTeam201702, |  Actual Points:
  GeorgKoppen201702  |
Parent ID:  #3893| Points:
 Reviewer:   |Sponsor:
-+-
Changes (by traumschule):

 * parent:   => #3893


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27143 [Core Tor/Tor]: Look for parts of code that relies on non-trunnel code for binary wire format handling

[Tor Bug Tracker & Wiki]

#27143: Look for parts of code that relies on non-trunnel code for binary wire
format handling
-+-
 Reporter:  rl1987   |  Owner:  (none)
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:  Tor: unspecified
Component:  Core |Version:
  Tor/Tor|   Keywords:  trunnel wireformat heartbleed-
 Severity:  Normal   |  safety security parsing
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Open a new ticket for each, so that it could be reworked one at a time.

 We really should do this for Tor cell handling.

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

Re: [tor-bugs] #26863 [Metrics/Relay Search]: display onionoo and RS version on RS pages

[Tor Bug Tracker & Wiki]

#26863: display onionoo and RS version on RS pages
--+--
 Reporter:  nusenu|  Owner:  metrics-team
 Type:  enhancement   | Status:  reopened
 Priority:  Medium|  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #27064| Points:
 Reviewer:|Sponsor:
--+--

Comment (by nusenu):

 Replying to [comment:8 irl]:
 > This would force us to build metrics-web from git, but we distribute
 tarballs without the git information

 that could be solved by writing the git commit id into a text file when
 you create the tarball?

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

Re: [tor-bugs] #27044 [Core Tor/Tor]: be more strict in parsing HiddenServicePort

[Tor Bug Tracker & Wiki]

#27044: be more strict in parsing HiddenServicePort
--+
 Reporter:  toralf|  Owner:  (none)
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * milestone:  Tor: unspecified => Tor: 0.3.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] #26863 [Metrics/Relay Search]: display onionoo and RS version on RS pages

[Tor Bug Tracker & Wiki]

#26863: display onionoo and RS version on RS pages
--+--
 Reporter:  nusenu|  Owner:  metrics-team
 Type:  enhancement   | Status:  reopened
 Priority:  Medium|  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #27064| Points:
 Reviewer:|Sponsor:
--+--

Comment (by irl):

 Our release process is quite manual, adding more steps at the moment would
 probably just lead to errors later on. Perhaps if someone wanted to write
 an ant patch we would merge it. In the future we want to have more
 automation in our releases and deployment, and then probably we would
 revisit this. Until then, we're not going to have meaningful version
 numbers for relay search.

 Probably it is best to close this ticket for now, and file a ticket on
 metrics-web for looking at adding the git commit reference there during
 the build and release processes.

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

Re: [tor-bugs] #18361 [Applications/Tor Browser]: Issues with corporate censorship and mass surveillance

[Tor Bug Tracker & Wiki]

#18361: Issues with corporate censorship and mass surveillance
--+--
 Reporter:  ioerror   |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:  1000 light years
 Reviewer:|Sponsor:
--+--

Comment (by traumschule):

 fine with [https://addons.mozilla.org/en-US/firefox/addon/requestblock/
 requestblock addon]

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

Re: [tor-bugs] #23818 [Core Tor/Tor]: Make v3 single onion services retry failed connections with a 3-hop path

[Tor Bug Tracker & Wiki]

#23818: Make v3 single onion services retry failed connections with a 3-hop path
-+-
 Reporter:  teor |  Owner:  neel
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs, single-onion,   |  Actual Points:
  ipv6, 034-triage-20180328, |
  034-removed-20180328   |
Parent ID:  #23493   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by neel):

 * cc: neel@… (added)
 * owner:  (none) => neel
 * status:  new => assigned


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

Re: [tor-bugs] #23588 [Core Tor/Tor]: Write fascist_firewall_choose_address_ls() and use it in hs_get_extend_info_from_lspecs()

[Tor Bug Tracker & Wiki]

#23588: Write fascist_firewall_choose_address_ls() and use it in
hs_get_extend_info_from_lspecs()
-+-
 Reporter:  teor |  Owner:  neel
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs, single-onion,   |  Actual Points:
  ipv6, 034-triage-20180328, |
  034-removed-20180328   |
Parent ID:  #23493   | Points:  1
 Reviewer:  teor |Sponsor:
-+-

Comment (by neel):

 I tried using `BUG()` here:

 {{{
 neel@kat:~/tor/tor % git diff
 diff --git a/src/feature/hs/hs_common.c b/src/feature/hs/hs_common.c
 index df43d5cde..35e5d9ac1 100644
 --- a/src/feature/hs/hs_common.c
 +++ b/src/feature/hs/hs_common.c
 @@ -1724,7 +1724,7 @@ hs_get_extend_info_from_lspecs(const smartlist_t
 *lspecs,
fascist_firewall_choose_address_ls(lspecs, 0, &ap, direct_conn);

/* Legacy ID is mandatory, and we require an IP address. */
 -  if (!tor_addr_port_is_valid_ap(&ap, 0) || !have_legacy_id) {
 +  if (BUG(!tor_addr_port_is_valid_ap(&ap, 0)) || !have_legacy_id) {
  /* If we're missing the legacy ID or the IP address, return NULL. */
  goto done;
}
 neel@kat:~/tor/tor %
 }}}

 I compiled the code and ran `make test-network-all` and got this:

 {{{
 neel@kat:~/tor/tor % make test-network-all
 mkdir -p ./test_network_log
 ping6 ::1 or ping ::1 succeeded, running IPv6 flavors: bridges+ipv6-min
 ipv6-exi
 t-min hs-v23-ipv6-md  single-onion-ipv6-md.
 tor-stable not found, skipping mixed flavors: mixed+hs-v23.
 SKIP: mixed+hs-v23
 PASS: basic-min
 FAIL: bridges-min
 PASS: hs-v2-min
 PASS: hs-v3-min
 PASS: single-onion-v23
 FAIL: bridges+ipv6-min
 PASS: ipv6-exit-min
 FAIL: hs-v23-ipv6-md
 Detail: chutney/tools/warnings.sh
 /usr/home/neel/tor/chutney//net/nodes.1534250$
 96
 Warning: Bug: 0x107a055 <_start+0xa5> at
 /usr/home/neel/tor/tor/src/app/tor
 (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number: 29
 Warning: Bug: 0x107a249  at
 /usr/home/neel/tor/tor/src/app/tor ($
 n Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number: 29
 Warning: Bug: 0x107a3ac  at
 /usr/home/neel/tor/tor/src/app/t$
 r (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number: 29
 Warning: Bug: 0x107a6b4  at
 /usr/home/neel/tor/to
 r/src/app/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number: 5
 Warning: Bug: 0x107d1e1  at
 /usr/home/neel/tor/tor/src/a
 pp/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number: 29
 Warning: Bug: 0x107ef90  at
 /usr/home/neel/tor/tor/src/ap
 p/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number: 29
 Warning: Bug: 0x10a580b 
 at /u
 sr/home/neel/tor/tor/src/app/tor (on Tor 0.3.5.0-alpha-dev
 b4b67c5fb5205e9a) Num
 ber: 24
 Warning: Bug: 0x10a6168 
 at /u
 sr/home/neel/tor/tor/src/app/tor (on Tor 0.3.5.0-alpha-dev
 b4b67c5fb5205e9a) Num
 ber: 24
 Warning: Bug: 0x10a799f  at
 /usr/home/neel/tor/t
 or/src/app/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number: 1
 Warning: Bug: 0x10ab0ea  at
 /usr/home/nee
 l/tor/tor/src/app/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number:
 24
 Warning: Bug: 0x10b0c72  at
 /usr/home/nee
 l/tor/tor/src/app/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number:
 1
 Warning: Bug: 0x10c0059  at
 /usr/home/neel
 /tor/tor/src/app/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number: 1
 Warning: Bug: 0x10c05c2  at
 /usr/home/neel
 /tor/tor/src/app/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number: 1
 Warning: Bug: 0x10f4b3e  at
 /usr/home/neel/
 tor/tor/src/app/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number: 4
 Warning: Bug: 0x10f6ce8  at
 /usr/home/nee
 l/tor/tor/src/app/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number:
 4
 Warning: Bug: 0x110a125  at
 /usr/home/neel/
 tor/tor/src/app/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number: 1
 Warning: Bug: 0x110e0a1 
 at /usr
 /home/neel/tor/tor/src/app/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a)
 Numbe
 r: 24
 Warning: Bug: 0x110ed8e  at
 /usr/home/neel/
 tor/tor/src/app/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number: 4
 Warning: Bug: 0xcfc  at
 /usr/home/
 neel/tor/tor/src/app/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a)
 Number: 25
 Warning: Bug: 0x1118cac  at
 /usr/home/ne
 el/tor/tor/src/app/tor (on Tor 0.3.5.0-alpha-dev b4b67c5fb5205e9a) Number:
 1
 Warning: Bug: 0x11222b4  at
 /usr/
 home/neel/tor/tor/src/app/tor (on Tor 0.3.5.0-

Re: [tor-bugs] #26062 [Core Tor/Tor]: client: ControlPort set doesn't mean you're a client

[Tor Bug Tracker & Wiki]

#26062: client: ControlPort set doesn't mean you're a client
-+-
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  034-roadmap-subtask, tor-client  |  Actual Points:
  tor-httptunnel |
Parent ID:  #25500   | Points:
 Reviewer:  nickm|Sponsor:
-+-
Changes (by traumschule):

 * keywords:  034-roadmap-subtask, tor-client => 034-roadmap-subtask, tor-
 client tor-httptunnel


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

Re: [tor-bugs] #25786 [Core Tor/Tor]: Policies for HTTPTunnelPort

[Tor Bug Tracker & Wiki]

#25786: Policies for HTTPTunnelPort
+--
 Reporter:  pyhedgehog  |  Owner:  (none)
 Type:  enhancement | Status:  new
 Priority:  Medium  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-httptunnel  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by traumschule):

 * keywords:   => tor-httptunnel


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

Re: [tor-bugs] #24897 [Core Tor/Tor]: Tor seems to malfunction on FreeBSD

[Tor Bug Tracker & Wiki]

#24897: Tor seems to malfunction on FreeBSD
-+-
 Reporter:  yurivict271  |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-httptunnel,  |  Actual Points:
  033-triage-20180320, 033-removed-20180320  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by traumschule):

 * keywords:  033-triage-20180320, 033-removed-20180320 => tor-httptunnel,
 033-triage-20180320, 033-removed-20180320


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

Re: [tor-bugs] #26647 [Core Tor/Tor]: defect: Spec for net/listeners/* doesn't covers HTTPTunnelPort directive or ExtORPort

[Tor Bug Tracker & Wiki]

#26647: defect: Spec for net/listeners/* doesn't covers HTTPTunnelPort 
directive or
ExtORPort
-+-
 Reporter:  pyhedgehog   |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Minor| Resolution:
 Keywords:  tor-spec, controller, easy, intro,   |  implemented
  fast-fix, 032-backport, 033-backport,  |  Actual Points:
  034-backport, 035-triaged-in-20180711, tor-|
  httptunnel |
Parent ID:   | Points:
 Reviewer:  teor |Sponsor:
-+-
Changes (by traumschule):

 * keywords:
 tor-spec, controller, easy, intro, fast-fix, 032-backport,
 033-backport, 034-backport, 035-triaged-in-20180711
 =>
 tor-spec, controller, easy, intro, fast-fix, 032-backport,
 033-backport, 034-backport, 035-triaged-in-20180711, tor-httptunnel


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

Re: [tor-bugs] #23588 [Core Tor/Tor]: Write fascist_firewall_choose_address_ls() and use it in hs_get_extend_info_from_lspecs()

[Tor Bug Tracker & Wiki]

#23588: Write fascist_firewall_choose_address_ls() and use it in
hs_get_extend_info_from_lspecs()
-+-
 Reporter:  teor |  Owner:  neel
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, tor-hs, single-onion,   |  Actual Points:
  ipv6, 034-triage-20180328, |
  034-removed-20180328   |
Parent ID:  #23493   | Points:  1
 Reviewer:  teor |Sponsor:
-+-

Comment (by neel):

 Also, when this code crashes, does it mean the connection wants to fall
 back to a 3-hop circuit but can't (and therefore crashes)?

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

Re: [tor-bugs] #27121 [Metrics/ExoneraTor]: Release ExoneraTor 3.0.0

[Tor Bug Tracker & Wiki]

#27121: Release ExoneraTor 3.0.0
+-
 Reporter:  karsten |  Owner:  karsten
 Type:  task| Status:  merge_ready
 Priority:  Medium  |  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  irl |Sponsor:
+-

Comment (by karsten):

 Great, thanks for checking! Released:
 https://dist.torproject.org/exonerator/3.0.0/ . Let's wait with the
 announcement until Tor Metrics has its own ExoneraTor page.

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

Re: [tor-bugs] #26514 [Applications/Tor Browser]: intermittent updater failures on Win64 (Error 19)

[Tor Bug Tracker & Wiki]

#26514: intermittent updater failures on Win64 (Error 19)
--+--
 Reporter:  mcs   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  TorBrowserTeam201808R |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

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


Comment:

 Great! Looks good to me. Applied to `tor-browser-60.1.0esr-8.0-1` (commit
 c2720b2274e51eb76b91e5f6a5f2a82bdfaf8013).

 I think it is okay to be conservative and apply the fix to 32bit Windows
 as well, not knowing where exactly the bug lies. We should test the 32bit
 case however, making sure we did not regress here.

 Jacek: big thanks for your help!

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

Re: [tor-bugs] #27109 [Core Tor/Tor]: Tor 0.3.5.0-alpha-dev: [warn] connection_mark_unattached_ap_(): Bug: stream (marked at ../src/core/or/connection_edge.c:2605) sending two socks replies?

[Tor Bug Tracker & Wiki]

#27109: Tor 0.3.5.0-alpha-dev: [warn] connection_mark_unattached_ap_(): Bug: 
stream
(marked at ../src/core/or/connection_edge.c:2605) sending two socks
replies?
+
 Reporter:  traumschule |  Owner:  rl1987
 Type:  defect  | Status:  needs_information
 Priority:  Medium  |  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor|Version:  Tor: unspecified
 Severity:  Normal  | Resolution:
 Keywords:  tor-httptunnel  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+
Changes (by traumschule):

 * keywords:   => tor-httptunnel


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

Re: [tor-bugs] #22842 [Webpages/Website]: Create a knowledge base that's more in-depth than FAQs

[Tor Bug Tracker & Wiki]

#22842: Create a knowledge base that's more in-depth than FAQs
--+---
 Reporter:  catalyst  |  Owner:  hiro
 Type:  task  | Status:  accepted
 Priority:  Medium|  Milestone:  WebsiteV3
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:  #23266| Points:
 Reviewer:|Sponsor:
--+---

Comment (by traumschule):

 I'd choose the wiki approach, similar to
 [http://mywiki.wooledge.org/BashFAQ BashFAQ] and protect FAQ/* pages to be
 editable only by selected curators (maybe per topic). This way we could
 easily reuse existing wikis and clean harmfully outdated stuff. Count me
 in if that becomes an official project.

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

Re: [tor-bugs] #27121 [Metrics/ExoneraTor]: Release ExoneraTor 3.0.0

[Tor Bug Tracker & Wiki]

#27121: Release ExoneraTor 3.0.0
+-
 Reporter:  karsten |  Owner:  karsten
 Type:  task| Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:  implemented
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  irl |Sponsor:
+-
Changes (by karsten):

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


Comment:

 Deployed and [https://lists.torproject.org/pipermail/tor-
 relays/2018-August/015885.html announced]. Closing.

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

Re: [tor-bugs] #23549 [Metrics/Website]: Move ExoneraTorServlet to metrics-web

[Tor Bug Tracker & Wiki]

#23549: Move ExoneraTorServlet to metrics-web
-+-
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:  implemented
 Keywords:  metrics-2018 |  Actual Points:
Parent ID:   | Points:
 Reviewer:  irl  |Sponsor:
-+-
Changes (by karsten):

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


Comment:

 Cool! 3.0.0 is released, amended metrics-web patch is merged and deployed,
 3.0.0 is deployed, change is announced. I guess this concludes this
 ticket/effort. Yay! Closing. 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] #27050 [Metrics/Onionoo]: Reverse DNS lookups are still slow

[Tor Bug Tracker & Wiki]

#27050: Reverse DNS lookups are still slow
-+--
 Reporter:  irl  |  Owner:  irl
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  karsten  |Sponsor:
-+--
Changes (by karsten):

 * reviewer:   => karsten


Comment:

 Will take a look tomorrow.

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

Re: [tor-bugs] #27124 [Metrics/Onionoo]: Reading node statuses pointlessly initialises first seen millis as last seen millis

[Tor Bug Tracker & Wiki]

#27124: Reading node statuses pointlessly initialises first seen millis as last
seen millis
-+
 Reporter:  irl  |  Owner:  irl
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by karsten):

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


Comment:

 Looks good, merged. Closing. 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] #27135 [Core Tor/sbws]: Write descriptor bandwidths average in raw results

[Tor Bug Tracker & Wiki]

#27135: Write descriptor bandwidths average in raw results
---+-
 Reporter:  juga   |  Owner:  juga
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  sbws 1.0 (MVP must)
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #27108 | Points:
 Reviewer: |Sponsor:
---+-

Comment (by starlight):

 descriptor updates arrive via control channel NS events

 https://gitweb.torproject.org/pytorctl.git/tree/TorCtl.py#n1243

 https://gitweb.torproject.org/pytorctl.git/tree/TorCtl.py#n121

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

Re: [tor-bugs] #27053 [Core Tor/Stem]: Check controller's event error handling

[Tor Bug Tracker & Wiki]

#27053: Check controller's event error handling
---+--
 Reporter:  atagar |  Owner:  atagar
 Type:  defect | Status:  reopened
 Priority:  Very High  |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Major  | Resolution:
 Keywords:  controller |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by atagar):

 Hi Dave. Good news, bad news time. The good news is that I figured out the
 python3 mock issue you found. Turns out there's a difference between PyPI
 and Python3's mock modules. Fixed...

 https://gitweb.torproject.org/stem.git/commit/?id=e75cf25

 Bad news is that this doesn't fix the transient test failures. I was able
 to repro those a few times, but once I started digging in the tests once
 again began passing reliably. Frustrating...

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27144 [Applications/Tor Launcher]: When I try to request a bridge from torproject.org using Tor network settings

[Tor Bug Tracker & Wiki]

#27144: When I try to request a bridge from torproject.org using Tor network
settings
---+---
 Reporter:  Dbryrtfbcbhgf  |  Owner:  brade
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+---
 When I try to request a bridge from torproject.org using Tor network
 settings, the browser will open behind Tor networks settings and it will
 not load anything.
 1. Delete {{{TorBrowser-Data}}}
 2. Open TorBrowser and try to request a bridge from torproject.org using
 Tor network settings and the bug should occur.

 TorBrowser 8a9

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

Re: [tor-bugs] #27144 [Applications/Tor Launcher]: When I try to request a bridge from torproject.org using Tor network settings

[Tor Bug Tracker & Wiki]

#27144: When I try to request a bridge from torproject.org using Tor network
settings
---+---
 Reporter:  Dbryrtfbcbhgf  |  Owner:  brade
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by Dbryrtfbcbhgf):

 Photo showing the bug.
 
[[Image(https://s33.postimg.cc/twp8h7r4v/Screen_Shot_2018-08-14_at_1.35.33_PM.png)]]

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

Re: [tor-bugs] #27129 [Applications/Tor Browser]: Add ca, ga, id, is, nb locales for Tor Browser

[Tor Bug Tracker & Wiki]

#27129: Add ca, ga, id, is, nb locales for Tor Browser
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-localization,|  Actual Points:
  TorBrowserTeam2018R|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by arthuredelstein):

 I built all 5 locales for linux-x86_64 and confirmed the browsers all work
 and the text is rendered in their respective languages.

 (After merging these patches for torbutton and tor-launcher we'll need to
 run ./import-translations.sh again and commit the results to make sure the
 translation strings for those locales are properly imported.)

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

Re: [tor-bugs] #27129 [Applications/Tor Browser]: Add ca, ga, id, is, nb locales for Tor Browser

[Tor Bug Tracker & Wiki]

#27129: Add ca, ga, id, is, nb locales for Tor Browser
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-localization,|  Actual Points:
  TorBrowserTeam201808R, ff60-esr|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by arthuredelstein):

 * keywords:  tbb-localization, TorBrowserTeam2018R => tbb-localization,
 TorBrowserTeam201808R, ff60-esr


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27145 [- Select a component]: help.tpo accounts is not clear enough

[Tor Bug Tracker & Wiki]

#27145: help.tpo accounts is not clear enough
--+
 Reporter:  juga  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Quoting https://help.torproject.org/tsa/doc/accounts/:

 > Most of the time when people want access to a specific host, what they
 really want is getting added to a particular group

 does "people" need to know how ldap works or how the different
 services/machines are configured to know which "group" they want to be
 added to?
 i suspect no

 > If you want to get added to some unix group, you will have to find an
 existing member of that group.

 awesome explanation, what if a new group is needed?

 > They should then request on trac –

 ok, the person in the group, not the person that "want" the "access".

 > ideally in a PGP signed message (as above in the new account creation
 section) – that you be added to their group.

 it seems this means that the *OpenPGP*-signed messaged should be in the
 trac ticket, but gives confusion to whether it should be a email, and
 whether it should be PGP-signed.

 And i could not find the component where to include 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] #27146 [Core Tor/Tor]: Mismatched digest in 0.3.3.9 and master mixed chutney network

[Tor Bug Tracker & Wiki]

#27146: Mismatched digest in 0.3.3.9 and master mixed chutney network
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.5.x-final
Component:  Core |Version:
  Tor/Tor|   Keywords:  regression, tor-dirauth, macOS,
 Severity:  Normal   |  035-must
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 When I run master i386 and Tor 0.3.3.9 x68_64 in a mixed chutney network,
 I see the following error:
 {{{
 Detail: chutney/tools/warnings.sh
 /Users/USER/tor/chutney/tools/../net/nodes.1534263100
 Warning: Unable to add signatures to consensus: Mismatched digest. Number:
 102
 Exit 255
 }}}

 master x86_64 and Tor 0.3.3.9 x68_64 in a mixed chutney network also get
 the same error:
 {{{
 Detail: chutney/tools/warnings.sh
 /Users/USER/tor/chutney/tools/../net/nodes.1534285790
 Warning: Unable to add signatures to consensus: Mismatched digest. Number:
 102
 Exit 255
 }}}

 We should fix this issue if it affects Linux and BSD. If it doesn't, maybe
 we should downgrade our support for authorities on macOS.

 If we want to diagnose this issue, implementing #20625 and #4593 would
 help.

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

Re: [tor-bugs] #27146 [Core Tor/Tor]: Mismatched digest in 0.3.3.9 and master mixed chutney network

[Tor Bug Tracker & Wiki]

#27146: Mismatched digest in 0.3.3.9 and master mixed chutney network
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  regression, tor-dirauth, macOS,  |  Actual Points:
  035-must   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * Attachment "nodes.1534263100.zip" added.

 macOS i386 chutney nodes directory

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

Re: [tor-bugs] #27146 [Core Tor/Tor]: Mismatched digest in 0.3.3.9 and master mixed chutney network

[Tor Bug Tracker & Wiki]

#27146: Mismatched digest in 0.3.3.9 and master mixed chutney network
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  regression, tor-dirauth, macOS,  |  Actual Points:
  035-must   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * Attachment "nodes.1534285790.zip" added.

 macOS x86_64 chutney nodes directory

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

Re: [tor-bugs] #27139 [Core Tor/Tor]: macOS i386 fails time unit tests

[Tor Bug Tracker & Wiki]

#27139: macOS i386 fails time unit tests
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  regression, macos, 035-must, |  Actual Points:
  034-must, 035-roadmap-proposed |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  regression, macos, i386 => regression, macos, 035-must,
 034-must, 035-roadmap-proposed


Comment:

 We must check if this issue affects Linux and BSD on 0.3.4 before
 releasing 0.3.4.

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

Re: [tor-bugs] #27139 [Core Tor/Tor]: macOS i386 fails time unit tests

[Tor Bug Tracker & Wiki]

#27139: macOS i386 fails time unit tests
-+
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  regression, macos, i386  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by teor):

 * keywords:  regression, macos, 035-must, 034-must, 035-roadmap-proposed =>
 regression, macos, i386


Comment:

 Oops, wrong ticket for that comment.

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

Re: [tor-bugs] #27146 [Core Tor/Tor]: Mismatched digest in 0.3.3.9 and master mixed chutney network

[Tor Bug Tracker & Wiki]

#27146: Mismatched digest in 0.3.3.9 and master mixed chutney network
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  regression, tor-dirauth, macOS,  |  Actual Points:
  035-must, 035-roadmap-proposed, 034-must   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  regression, tor-dirauth, macOS, 035-must =>
 regression, tor-dirauth, macOS, 035-must, 035-roadmap-proposed,
 034-must


Comment:

 We must check if this issue affects Linux and BSD on 0.3.4 before
 releasing 0.3.4.

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

Re: [tor-bugs] #27139 [Core Tor/Tor]: macOS i386 fails time unit tests

[Tor Bug Tracker & Wiki]

#27139: macOS i386 fails time unit tests
-+
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  regression, macos, i386  |  Actual Points:
Parent ID:  #26987   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by teor):

 * parent:   => #26987


Comment:

 Replying to [comment:1 nickm]:
 > Are these intermittent or consistent?

 Consistent, with exactly those numbers in the tests every time.

 I don't see the same failures on macOS x86_64, but I do occasionally see
 odd time jumps after sleep on x86_64, see #26987. Maybe they are the same
 bug.

 > I'd be okay with or without OSX i386 CI.

 Same here. Tor Browser doesn't distribute i386 builds on macOS, and
 Homebrew only supports 64-bit. (MacPorts still builds 320bit tor, though.)

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