Re: [tor-bugs] #30245 [Applications/Tor Browser]: Tor will not connect

[Tor Bug Tracker & Wiki]

#30245: Tor will not connect
--+--
 Reporter:  peterm|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by peterm):

 Yes Tor browser and currently 8.0.8 but have tried many down to 6.  I am
 using Windows 10.  The attachment shows the details.

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

Re: [tor-bugs] #20116 [Applications/GetTor]: Get @get_tor twitter account verified

[Tor Bug Tracker & Wiki]

#20116: Get @get_tor twitter account verified
-+---
 Reporter:  mrphs|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/GetTor  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  gettor-roadmap   |  Actual Points:
Parent ID:  #28231   | Points:
 Reviewer:   |Sponsor:  Sponsor19
-+---
Changes (by arma):

 * status:  assigned => new


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

Re: [tor-bugs] #29338 [Core Tor/Tor]: restore HiddenServiceAuthorizeClient in v3

[Tor Bug Tracker & Wiki]

#29338: restore HiddenServiceAuthorizeClient in v3
+--
 Reporter:  Alan|  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:  Tor:
|  0.4.1.x-final
Component:  Core Tor/Tor|Version:  Tor:
|  0.3.5.7
 Severity:  Normal  | Resolution:
 Keywords:  tor-hs, hs-auth, client-auth, hsv3  |  Actual Points:
Parent ID:  #27544  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by ageisp0lis):

 Any progress here? #20742

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

Re: [tor-bugs] #30245 [Applications/Tor Browser]: Tor will not connect

[Tor Bug Tracker & Wiki]

#30245: Tor will not connect
--+--
 Reporter:  peterm|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by arma):

 * owner:  (none) => tbb-team
 * component:  Core Tor/Tor => Applications/Tor Browser


Comment:

 I am guessing by "Tor" you mean Tor Browser?

 If so, which version of Tor Browser?

 And what operating system are you using?

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

Re: [tor-bugs] #29291 [Core Tor/sbws]: Work out a better way to choose the data size to download

[Tor Bug Tracker & Wiki]

#29291: Work out a better way to choose the data size to download
-+-
 Reporter:  juga |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  sbws:
 |  unspecified
Component:  Core Tor/sbws|Version:  sbws:
 |  1.0.2
 Severity:  Normal   | Resolution:
 Keywords:  changes-version-patch, sbws-11x- |  Actual Points:
  final-removed-20190312, scanner|
Parent ID:  #29954   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by juga):

 I tried https://gist.github.com/juga0/4e29abef25c393e747e0a528749c11ba
 some months ago, but could not come out with a good way to check when the
 connection has been "stabilized".

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

Re: [tor-bugs] #30196 [Core Tor/sbws]: Add the tor version to the sbws bandwidth file header

[Tor Bug Tracker & Wiki]

#30196: Add the tor version to the sbws bandwidth file header
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  sbws: 1.2.x-final
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:
---+---

Comment (by juga):

 Reminder to myself: i've implemented the operating system, ssl_version and
 tor_version in branch https://github.com/juga0/sbws/tree/ticket30196

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

Re: [tor-bugs] #30227 [Core Tor/sbws]: Work out why recent_measurements_excluded_few_count=733

[Tor Bug Tracker & Wiki]

#30227: Work out why recent_measurements_excluded_few_count=733
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  sbws: unspecified
Component:  Core Tor/sbws  |Version:  sbws: unspecified
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #29710 | Points:
 Reviewer: |Sponsor:
---+---

Comment (by juga):

 Replying to [comment:2 juga]:
 > These tickets looks good to improve scanner performance, but maybe we
 could reduce complexity by implementing what proposed in
 https://trac.torproject.org/projects/tor/ticket/29291#comment:4 that could
 be useful for onionperf too.

 i just don't know how much would change the bandwidth values to create a
 request and wait it stabilizes, or to make different requests with "keep-
 alive" connection.

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

Re: [tor-bugs] #30227 [Core Tor/sbws]: Work out why recent_measurements_excluded_few_count=733

[Tor Bug Tracker & Wiki]

#30227: Work out why recent_measurements_excluded_few_count=733
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  sbws: unspecified
Component:  Core Tor/sbws  |Version:  sbws: unspecified
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #29710 | Points:
 Reviewer: |Sponsor:
---+---

Comment (by juga):

 These tickets looks good to improve scanner performance, but maybe we
 could reduce complexity by implementing what proposed in
 https://trac.torproject.org/projects/tor/ticket/29291#comment:4 that could
 be useful for onionperf too.

 #29720 could also reduce the number of measurements required.

 #29719 may or may not improve performance, but it'd reduce complexity on
 understanding why some relays get more measurements than others and the
 monitoring KeyValues associated to the priority loops and the time it
 takes to measure all the network.

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

Re: [tor-bugs] #30229 [Core Tor/sbws]: Automatically set the scanner country using Tor's GeoIP

[Tor Bug Tracker & Wiki]

#30229: Automatically set the scanner country using Tor's GeoIP
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  sbws: unspecified
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by juga):

 This adds more complexity to the code. Irl proposed to add the ASN in
 #30196.
 Another issue is that in debian stable there is python3-geoip2 (i think
 the one that ooni uses), but it uses Maxmind files, not tor-geoip. I don't
 think we have a python script for tor-geoip?.

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

Re: [tor-bugs] #30196 [Core Tor/sbws]: Add the tor version to the sbws bandwidth file header

[Tor Bug Tracker & Wiki]

#30196: Add the tor version to the sbws bandwidth file header
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  sbws: 1.2.x-final
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:
---+---

Comment (by juga):

 Summarizing the metadata proposed:

 Replying to [comment:3 irl]:
 >
 > * The need for the inline contact information becomes evident when we
 look at how much trouble we've had tracking down who runs the default
 bridges in Tor Browser #30121

 Do we need contact information having an identifier (see
 https://trac.torproject.org/projects/tor/ticket/30217#comment:2) and
 initially knowing who runs the scanners (usually the same dirauth)?.

 > * The need for AS as well as country allows us to correlate BGP events
 with bandwidth changes. Ideally we can know both the AS of the scanner and
 the target. Tor Metrics already knows the AS of the relay.

 When we decided to include the country (#29299) i remember arma commenting
 in irc to just add it in the configuration to don't make the code more
 complicated. I'm commenting more on this in (#30229)

 > * In some cases, the target is on a CDN, which means the AS may not be
 known in advance. In these cases we might choose to omit the AS number and
 instead use a user-assigned country code for the target.

 Do we currently have more than one CDN?. I only know one, though would be
 great to have more.

 > * We could assign QM-QZ (user-assigned codes not used elsewhere in Tor
 to my knowledge) to CDN providers but each new provider used would require
 a spec change, and external researchers would end up using whatever value
 and not being able to interop their data with ours if we clash.
 > * We could use the OO escape code and build codes like "OOFastly" which
 is probably the more maintainable solution, but would require that parsers
 do not panic when they see >2 characters (I know the standard is known as
 alpha-2 but it isn't actually limited to 2 characters!)
 > * We could use Tor's geoip database to resolve the IP address resolved
 via the same circuit of the CDN into a country/IP address to add to the
 measurements, but this may prove to be unreliable especially in the longer
 term as IPv4 exhaustion causes more and more IP address swapping about.

 Not convinced on any of the options for CDNs, but can't think of other
 solution.

 Replying to [comment:4 teor]:
 > * we wanted to know the tor version to recommend tor upgrades to
 bandwidth authority operators (#30184)

 easy.

 > * we might be interested in OpenSSL and NSS versions in future, because
 they have both had different bugs that stop relays connecting to each
 other

 Is there a way to ask this to Tor? `GETINFO` only returns Tor version. Is
 it possible that python `ssl.OPENSSL_VERSION` might be different to the
 one being used by the running Tor?.

 > * we have asked authority operators about operating systems before

 What in concrete we would like to know about the operating system?, see
 options in https://docs.python.org/3/library/platform.html

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

Re: [tor-bugs] #30217 [Metrics/CollecTor]: Extend CollecTor filesystem protocol for bandwidth files

[Tor Bug Tracker & Wiki]

#30217: Extend CollecTor filesystem protocol for bandwidth files
-+-
 Reporter:  irl  |  Owner:
 |  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/CollecTor|Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-bwauth,tor-dirauth,metrics-  |  Actual Points:
  roadmap-2019-q2|
Parent ID:  #21378   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by juga):

 Replying to [comment:1 teor]:

 > We thought about adding a scanner name. And now I can't remember why we
 didn't. Maybe juga knows?

 I think i didn't included just because i don't remember talking about
 that.
 I realized that some identifier would be useful in #29355.
 So, there are 2 options to identify the scanner:
 - 1. Include the nickname. The scanner does not run when some options have
 not been edited, but it's not the case of the nickname. I could change the
 configuration parser to force editing a nickname. It's human readable.
 Since we would only have ~10 scanners (unless we start having more than 1
 scanner per dirauth), should be unique.
 - 2. Include the UUID (#29355). It gets created automatically the first
 time and it's unique but not human readable.

 Which one would we prefer?, both?.

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

Re: [tor-bugs] #30216 [Metrics/Library]: Add bandwidth file parser to metrics-lib

[Tor Bug Tracker & Wiki]

#30216: Add bandwidth file parser to metrics-lib
-+-
 Reporter:  irl  |  Owner:  karsten
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-bwauth,tor-dirauth,metrics-  |  Actual Points:
  roadmap-2019-q2|
Parent ID:  #21378   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by karsten):

 * priority:  Medium => High
 * status:  accepted => needs_review


Comment:

 Okay, it turned out to be faster to just parse all fields than to figure
 out what fields we can add in a later step.

 Please review [https://gitweb.torproject.org/user/karsten/metrics-
 lib.git/commit/?h=task-30216=75f50f3776e2308decd6530673f0ad33fd54fa35
 commit 75f50f3 in my task-30216 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] #30245 [Core Tor/Tor]: Tor will not connect

[Tor Bug Tracker & Wiki]

#30245: Tor will not connect
--+
 Reporter:  peterm|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by peterm):

 Firefox works perfectly.

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

Re: [tor-bugs] #3780 [Obfuscation/BridgeDB]: GetTor and BridgeDB should share email processing code

[Tor Bug Tracker & Wiki]

#3780: GetTor and BridgeDB should share email processing code
--+
 Reporter:  kaner |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Obfuscation/BridgeDB  |Version:
 Severity:  Normal| Resolution:
 Keywords:  bridgedb  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by arma):

 * status:  assigned => new


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