[tor-bugs] #24416 [Applications/Tor Browser]: Can't login to any website which use Google Recaptcha - HELP!

[Tor Bug Tracker & Wiki]

#24416: Can't login to any website which use Google Recaptcha - HELP!
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  |   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Try again later
 Your computer or network may be sending automated queries. To protect our
 users, we can't process your request right now. For more details visit our
 help page

 Tried new identity already. I can't login anymore!!

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

Re: [tor-bugs] #22906 [Core Tor/Tor]: We might not want to commit Cargo.lock files

[Tor Bug Tracker & Wiki]

#22906: We might not want to commit Cargo.lock files
-+--
 Reporter:  isis |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  rust, tor-build  |  Actual Points:
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:  SponsorZ
-+--
Changes (by chelseakomlo):

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


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

Re: [tor-bugs] #22906 [Core Tor/Tor]: We might not want to commit Cargo.lock files

[Tor Bug Tracker & Wiki]

#22906: We might not want to commit Cargo.lock files
-+--
 Reporter:  isis |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, tor-build  |  Actual Points:
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:  SponsorZ
-+--

Comment (by chelseakomlo):

 Closing as this appears to be resolved- feel free to re-open if there are
 other pending questions. Agree with committing a lockfile for the tor
 binary.

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

Re: [tor-bugs] #23878 [Core Tor/Tor]: Attempt rewriting buffers.c in Rust

[Tor Bug Tracker & Wiki]

#23878: Attempt rewriting buffers.c in Rust
-+-
 Reporter:  isis |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust-pilot, rust, datatypes  |  Actual Points:
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:  Sponsor8-can
-+-
Changes (by chelseakomlo):

 * cc: chelseakomlo (added)


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

[tor-bugs] #24415 [Applications/Tor Browser]: Tor crashes when opening new tab, reason unknown

[Tor Bug Tracker & Wiki]

#24415: Tor crashes when opening new tab, reason unknown
--+
 Reporter:  kouwei32  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor: unspecified
 Severity:  Normal|   Keywords:  tor crashes tab
  |  unknown
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Tor stops working when opening new tab. I don't know why, but I have the
 debug report from Visual Studio: Unhandled exception at 0x6850687D
 (d2d1.dll) in firefox.exe: 0xC005: Access violation writing location
 0x6DCAC3F0.
 The first tab is still completely usable, and other features are
 accessible too.
 Version is the latest at the time of ticket creation but number is unknown
 because unable to open settings.

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

Re: [tor-bugs] #24394 [Core Tor/Tor]: add ipv6 dirauth address

[Tor Bug Tracker & Wiki]

#24394: add ipv6 dirauth address
-+-
 Reporter:  stefani  |  Owner:  (none)
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, tor-dirauth, 028-backport, |  Actual Points:
  029-backport, 030-backport, 031-backport   |
Parent ID:   | Points:  0.1
 Reviewer:   |Sponsor:
-+-

Comment (by Sebastian):

 I didn't put it onto 0.2.8 because that's so close to being EOL and not
 really being a functionality improvement for it, but I can cherry-pick it
 if you want

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

Re: [tor-bugs] #24394 [Core Tor/Tor]: add ipv6 dirauth address

[Tor Bug Tracker & Wiki]

#24394: add ipv6 dirauth address
-+-
 Reporter:  stefani  |  Owner:  (none)
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, tor-dirauth, 028-backport, |  Actual Points:
  029-backport, 030-backport, 031-backport   |
Parent ID:   | Points:  0.1
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:
 ipv6, tor-dirauth, 028-backport, 029-backport, 030-backport,
 031-backport, 032-backport
 =>
 ipv6, tor-dirauth, 028-backport, 029-backport, 030-backport,
 031-backport


Comment:

 Oops, 0.3.2 isn't stable yet

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

Re: [tor-bugs] #24394 [Core Tor/Tor]: add ipv6 dirauth address

[Tor Bug Tracker & Wiki]

#24394: add ipv6 dirauth address
-+-
 Reporter:  stefani  |  Owner:  (none)
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, tor-dirauth, 028-backport, |  Actual Points:
  029-backport, 030-backport, 031-backport,  |
  032-backport   |
Parent ID:   | Points:  0.1
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:   =>
 ipv6, tor-dirauth, 028-backport, 029-backport, 030-backport,
 031-backport, 032-backport
 * status:  needs_review => merge_ready
 * points:   => 0.1


Comment:

 This looks fine to me, but the commit needs to be cherry-picked onto
 maint-0.2.8 when we merge, because 0.2.8 is still supported until 1
 January 2018. (By the way, 0.3.0 is still supported until 26 January
 2018.)

 
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases

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

Re: [tor-bugs] #9775 [Core Tor/Tor]: Authorities should report when they don't vote Running but some addresses are still reachable

[Tor Bug Tracker & Wiki]

#9775: Authorities should report when they don't vote Running but some addresses
are still reachable
+--
 Reporter:  arma|  Owner:  (none)
 Type:  enhancement | Status:  new
 Priority:  Medium  |  Milestone:  Tor:
|  unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-dirauth logging reporting easy  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by teor):

 Replying to [comment:19 teor]:
 > I think this is a good change. Don't we do it already with IPv6 by
 dropping the addresses in votes?

 We do this, but Onionoo doesn't currently parse votes and use them for its
 new unreachable_or_addresses field:
 
https://metrics.torproject.org/onionoo.html#details_relay_unreachable_or_addresses

 So this only works for IPv6 addresses when a minority of authorities is on
 IPv6.

 > Or do we drop the entire relay from the vote when we drop the Running
 flag?

 We keep it, but vote it not Running. It only gets dropped from the
 consensus.

 > If I had to choose, I would prioritise relays checking their own IPv6
 ORPort reachability over this change.

 Also, consensus-health has a "ReachableIPv6" pseudo-flag, but doesn't
 parse votes or descriptors, so it can't do "UnreachableIPv6" yet:

 https://consensus-health.torproject.org/

 And Relay Search (Atlas) has IPv6 ORPort and IPv6 Exit flags, but, again,
 that doesn't really help:

 https://atlas.torproject.org/#toprelays

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

Re: [tor-bugs] #24414 [Metrics/Website]: Add Tor relay map and OrNetStats to services.html

[Tor Bug Tracker & Wiki]

#24414: Add Tor relay map and OrNetStats to services.html
-+--
 Reporter:  cypherpunks  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 It would be great to see that tormap rewritten to use OpenStreetMap tiles
 instead of Google's and Onionoo instead of manually constructing the data
 source. This is probably very easily achievable with leaflet.js.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24414 [Metrics/Website]: Add Tor relay map and OrNetStats to services.html

[Tor Bug Tracker & Wiki]

#24414: Add Tor relay map and OrNetStats to services.html
-+--
 Reporter:  cypherpunks  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 https://tormap.void.gr/  (code: https://github.com/kargig/tormap )
 originally written by Moritz, maintained by
 https://twitter.com/kargig

 (unfortunately it does not work reliably for TorBrowser users, probably
 due to Google blocking access to map data via certain exit relays)

 this uses also onionoo:
 https://nusenu.github.io/OrNetStats/

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

Re: [tor-bugs] #23782 [Metrics/Atlas]: Expose all possible query features in an "Advanced Search" HTML form

[Tor Bug Tracker & Wiki]

#23782: Expose all possible query features in an "Advanced Search" HTML form
---+--
 Reporter:  cypherpunks|  Owner:  irl
 Type:  enhancement| Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by irl):

 * parent:  #23518 =>


Comment:

 The parameter that would need doesn't exist in Onionoo, so actually we
 can't make those exact matches. With the updating of Backbone.js however,
 this no longer blocks on #23518 as we can now have optional parts to the
 URL.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24413 [Core Tor/Tor]: circuit_package_relay_cell(): Bug: outgoing relay cell sent from ../src/or/relay.c:839 has n_chan==NULL. Dropping. (on Tor 0.3.1.8 )

[Tor Bug Tracker & Wiki]

#24413: circuit_package_relay_cell(): Bug: outgoing relay cell sent from
../src/or/relay.c:839 has n_chan==NULL. Dropping. (on Tor 0.3.1.8 )
--+
 Reporter:  alecmuffett   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 * This error, repeatedly, on 0.3.1.7 and 0.3.1.8
 * I don't know if it happened on other versions.
 * Ubuntu 16.04.3 LTS with the Tor-supplied binaries;
 * Debian-Jessie, ditto

 {{{
 Nov 26 11:26:01.000 [warn] circuit_package_relay_cell(): Bug: outgoing
 relay cell sent from ../src/or/!relay.c:839 has n_chan==NULL. Dropping.
 (on Tor 0.3.1.8 )
 Nov 26 11:26:01.000 [warn] Bug: . Stack trace: (on Tor 0.3.1.8 )
 Nov 26 11:26:01.000 [warn] Bug: tor(log_backtrace+0x42)
 [0x555f99ba1242] (on Tor 0.3.1.8 )
 Nov 26 11:26:01.000 [warn] Bug:
 tor(relay_send_command_from_edge_+0x4ff) [0x555f99aa87ff] (on Tor 0.3.1.8
 )
 Nov 26 11:26:01.000 [warn] Bug: tor(connection_edge_send_command+0x62)
 [0x555f99aa8ae2] (on Tor 0.3.1.8 )
 Nov 26 11:26:01.000 [warn] Bug:
 tor(connection_edge_package_raw_inbuf+0x1df) [0x555f99aa8def] (on Tor
 0.3.1.8 )
 Nov 26 11:26:01.000 [warn] Bug:
 tor(connection_edge_process_inbuf+0x1df) [0x555f99b459df] (on Tor 0.3.1.8
 )
 Nov 26 11:26:01.000 [warn] Bug: tor(+0x107f39) [0x555f99b3df39] (on
 Tor 0.3.1.8 )
 Nov 26 11:26:01.000 [warn] Bug: tor(+0x4d38e) [0x555f99a8338e] (on Tor
 0.3.1.8 )
 Nov 26 11:26:01.000 [warn] Bug: /usr/lib/x86_64-linux-
 gnu/libevent-2.0.so.5(event_base_loop+0x819) [0x7f932471b4c9] (on Tor
 0.3.1.8 )
 Nov 26 11:26:01.000 [warn] Bug: tor(do_main_loop+0x295)
 [0x555f99a844b5] (on Tor 0.3.1.8 )
 Nov 26 11:26:01.000 [warn] Bug: tor(tor_main+0x1c35) [0x555f99a87f65]
 (on Tor 0.3.1.8 )
 Nov 26 11:26:01.000 [warn] Bug: tor(main+0x19) [0x555f99a7fcc9] (on
 Tor 0.3.1.8 )
 Nov 26 11:26:01.000 [warn] Bug: /lib/x86_64-linux-
 gnu/libc.so.6(!__libc_start_main+0xf0) [0x7f932363a830] (on Tor 0.3.1.8 )
 Nov 26 11:26:01.000 [warn] Bug: tor(_start+0x29) [0x555f99a7fd19] (on
 Tor 0.3.1.8 )
 }}}

 Configuration:

 {{{
 DataDirectory /home/ubuntu/eotk/projects.d/wikipedia.d/hs-1.d
 ControlPort unix:/home/ubuntu/eotk/projects.d/wikipedia.d/hs-1.d/tor-
 control.sock
 PidFile /home/ubuntu/eotk/projects.d/wikipedia.d/hs-1.d/tor.pid
 Log notice file /home/ubuntu/eotk/projects.d/wikipedia.d/hs-1.d/tor.log
 SafeLogging 1
 HeartbeatPeriod 60 minutes
 LongLivedPorts 80,443
 RunAsDaemon 1

 # use single onions
 SocksPort 0
 HiddenServiceSingleHopMode 1
 HiddenServiceNonAnonymousMode 1

 # softmap
 HiddenServiceDir /home/ubuntu/eotk/projects.d/wikipedia.d/hs-1.d
 HiddenServicePort 80
 unix:/home/ubuntu/eotk/projects.d/wikipedia.d/hs-1.d/port-80.sock
 HiddenServicePort 443
 unix:/home/ubuntu/eotk/projects.d/wikipedia.d/hs-1.d/port-443.sock
 HiddenServiceNumIntroductionPoints 3
 }}}

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

Re: [tor-bugs] #23544 [Metrics/Onionoo]: Add recommended_version parameter

[Tor Bug Tracker & Wiki]

#23544: Add recommended_version parameter
-+--
 Reporter:  cypherpunks  |  Owner:  metrics-team
 Type:  enhancement  | Status:  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2017 |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * status:  needs_review => merge_ready


Comment:

 Ready to go (cf. comments on #22488, #23962, #21827).

 (The review of of commits based on each other in one branch distributed
 across several tickets, is a very cumbersome review situation.  If commits
 are as tightly connected as they are here they shouldn't be distributed on
 different tickets.  As soon as the connection becomes apparent the tasks
 should be merged.  The redundancy also becomes visible in the very similar
 ready-for-review comments and replies.)

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

Re: [tor-bugs] #21827 [Metrics/Onionoo]: Add recommended_version to bridge details document

[Tor Bug Tracker & Wiki]

#21827: Add recommended_version to bridge details document
-+--
 Reporter:  cypherpunks  |  Owner:  metrics-team
 Type:  enhancement  | Status:  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * status:  needs_review => merge_ready


Comment:

 As remarked on #22488: tests and checks pass, spec changes describe the
 changes. The method name 'getRecommendedVersion` is quite misleading -
 especially together with `getVersion` - as it returns a boolean, but as
 the method was introduced long ago this shouldn't halt a merge.

 Maybe, the naming could be improved at some point?

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

Re: [tor-bugs] #24411 [Metrics/Atlas]: Country based sorting does not work

[Tor Bug Tracker & Wiki]

#24411: Country based sorting does not work
---+
 Reporter:  cypherpunks|  Owner:  irl
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by irl):

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


Comment:

 Fixed in 5871fa6.

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

Re: [tor-bugs] #24411 [Metrics/Atlas]: Country based sorting does not work

[Tor Bug Tracker & Wiki]

#24411: Country based sorting does not work
---+--
 Reporter:  cypherpunks|  Owner:  irl
 Type:  defect | Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by irl):

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


Comment:

 Hmm. Ok.

 I assume the intended behaviour is to sort alphabetically by English
 language name.

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

Re: [tor-bugs] #24412 [Metrics/Onionoo]: Search parameter limit always returns 400 error

[Tor Bug Tracker & Wiki]

#24412: Search parameter limit always returns 400 error
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:  not a bug
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

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


Comment:

 Relay Search should keep track of the state of the limit parameter.  The
 Onionoo syntax would be broken with such a change.  Thus, I don't think
 that this would be an acceptable feature request either.

 Closing as 'not a bug'.

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

Re: [tor-bugs] #23962 [Metrics/Onionoo]: Allow searching by bridges by version with the version parameter

[Tor Bug Tracker & Wiki]

#23962: Allow searching by bridges by version with the version parameter
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  enhancement  | Status:  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * status:  needs_review => merge_ready


Comment:

 Indeed, this is only 'worth' a minor version increase, especially as
 relays and bridges are separated by the document structure.
 As remarked on #22488: tests and checks pass, spec changes describe the
 changes. => ready for merge.

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

Re: [tor-bugs] #22488 [Metrics/Onionoo]: Include relay version listed in consensus in addition to platform line from server descriptor

[Tor Bug Tracker & Wiki]

#22488: Include relay version listed in consensus in addition to platform line 
from
server descriptor
-+--
 Reporter:  cypherpunks  |  Owner:  metrics-team
 Type:  enhancement  | Status:  merge_ready
 Priority:  High |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2017 |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * status:  needs_review => merge_ready


Comment:

 Patch looks fine and it is a good idea to provide the 'version' field.
 Tests and checks pass, spec changes describe the changes.  => ready for
 merge.

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

Re: [tor-bugs] #24412 [Metrics/Onionoo]: Search parameter limit always returns 400 error

[Tor Bug Tracker & Wiki]

#24412: Search parameter limit always returns 400 error
-+--
 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 irl):

 The semantics of it aren't great, but it does help to keep the query as a
 single string in Relay Search. If breaking the semantics is a terrible
 idea for an internal Onionoo reason then this could be implemented by
 parsing the query string in Relay Search and then constructing the Onionoo
 query with the limit parameter but that state would then be discarded if
 the search was re-run. Or I could just leave Relay Search with a hardcoded
 maximum result set size of 2000.

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

Re: [tor-bugs] #24412 [Metrics/Onionoo]: Search parameter limit always returns 400 error

[Tor Bug Tracker & Wiki]

#24412: Search parameter limit always returns 400 error
-+--
 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 iwakeh):

 The url you used above means that 'limit' was a field to search the
 content of, which correctly results in an error as 'limit' is no field
 known to onionoo.

 I think you want the result you get from the following url:
 `https://onionoo.torproject.org/details?search=xyz=3`

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

Re: [tor-bugs] #23914 [Metrics/Onionoo]: Extend flag parameter to support comma-separated list of flags

[Tor Bug Tracker & Wiki]

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

Comment (by irl):

 This would be required to allow aggregations in Relay Search of
 "Fast+Exit".

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24412 [Metrics/Onionoo]: Search parameter limit always returns 400 error

[Tor Bug Tracker & Wiki]

#24412: Search parameter limit always returns 400 error
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 This works:
 https://onionoo.torproject.org/details?limit=1

 This does not:
 https://onionoo.torproject.org/details?search=limit:1

 I'd like to give Relay Search users the ability to load larger results
 sets as long as they have explicitly asked for them. This would mean
 adding a limit:N to the search term as part of the search query which
 could be built using #23782.

 Unfortunately, this parameter does not seem to work.

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

Re: [tor-bugs] #22062 [Metrics/Onionoo]: Bad requests do not add the Access-Control-Allow-Origin header

[Tor Bug Tracker & Wiki]

#22062: Bad requests do not add the Access-Control-Allow-Origin header
-+--
 Reporter:  cypherpunks  |  Owner:  metrics-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2018 |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 This would be required for #8667.

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

Re: [tor-bugs] #24256 [Metrics/Onionoo]: Add a new "outdated" field to distinguish between outdated and too new tor versions

[Tor Bug Tracker & Wiki]

#24256: Add a new "outdated" field to distinguish between outdated and too new 
tor
versions
-+---
 Reporter:  arma |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by irl):

 I like the "version_status" idea. I was thinking to add the specific
 reasons why a version is not recommended (the ones that are affected by
 specific bugs as mentioned in the tor source) but I wonder if those do not
 ever actually see the consensus anyway and so wouldn't be appearing in
 Onionoo.

 This would perhaps be something to add to Atlas when a whole bunch of
 relays are just about to disappear to explain to those users that they
 need to upgrade, but once the relays are not in Onionoo anymore the
 message would never be seen again.

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

[tor-bugs] #24411 [Metrics/Atlas]: Country based sorting does not work

[Tor Bug Tracker & Wiki]

#24411: Country based sorting does not work
---+--
 Reporter:  cypherpunks|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+--
 In the search overview you can click about any column heading to sort by
 that column, that does not work for the country column.

 example:
 https://atlas.torproject.org/#search/flag:authority

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24410 [Webpages/Website]: No security check when downloading using TOR

[Tor Bug Tracker & Wiki]

#24410: No security check when downloading using TOR
--+--
 Reporter:  thermodynamite|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:  Tor: unspecified
 Severity:  Minor |   Keywords:  Download
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 When trying to download files likes videos or images using TOR the files
 sometimes fail to start downloading. Usually, this occurs when the check
 asking to confirm the download doesn't appear.

 I have had this error on websites that I regularly visit and there is
 nothing in those sessions that I do differently that would cause this bug
 to happen.

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

Re: [tor-bugs] #6947 [Metrics/Onionoo]: Allow filtering relays by version ranges

[Tor Bug Tracker & Wiki]

#6947: Allow filtering relays by version ranges
-+--
 Reporter:  rransom  |  Owner:  metrics-team
 Type:  enhancement  | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by irl):

 * component:  Metrics/Atlas => Metrics/Onionoo


Comment:

 Relay Search will magically support this for both single relay lookup and
 aggregations if it's supported by Onionoo.

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

Re: [tor-bugs] #6946 [Metrics/Onionoo]: Allow filtering relays by OS

[Tor Bug Tracker & Wiki]

#6946: Allow filtering relays by OS
-+--
 Reporter:  rransom  |  Owner:  metrics-team
 Type:  enhancement  | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by irl):

 * component:  Metrics/Atlas => Metrics/Onionoo


Comment:

 Relay Search will magically support this for both single relay lookup and
 aggregations if it's supported by Onionoo.

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

Re: [tor-bugs] #6675 [Metrics/Atlas]: Support grouping by contact

[Tor Bug Tracker & Wiki]

#6675: Support grouping by contact
---+--
 Reporter:  cypherpunks|  Owner:  metrics-team
 Type:  enhancement| Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by irl):

 Relay Search supports the following queries:

 Aggregate simple data in single table row:
 ​https://atlas.torproject.org/#aggregate/all/contact:CONTACT

 Show all relays matching in multiple table rows:
 ​https://atlas.torproject.org/#search/contact:CONTACT

 A details view with aggregated graphs may be added in #23509.

 nusenu: Does this solve your use case or do you think grouping by contact
 is still useful? This is easier than grouping by family but it would only
 group by exact matches and every time we add a grouping the code becomes
 exponentially more complex in the way it's currently implemented.

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

Re: [tor-bugs] #6662 [Metrics/Atlas]: Support grouping by family

[Tor Bug Tracker & Wiki]

#6662: Support grouping by family
---+--
 Reporter:  cypherpunks|  Owner:  metrics-team
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:  wontfix
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by irl):

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


Comment:

 Grouping by family is a hard problem.

 Relay Search supports the following queries:

 Aggregate simple family data in single table row:
 https://atlas.torproject.org/#aggregate/all/family:FINGERPRINT

 Show all relays in a family in multiple table rows:
 https://atlas.torproject.org/#search/family:FINGERPRINT

 A details view with aggregated graphs may be added in #23509.

 I think in general this addresses most use cases. A true grouping by
 family may be enabled by using a database to back Onionoo but until we get
 there, this is just not implementable.

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

Re: [tor-bugs] #24402 [Metrics/Atlas]: Make numbers in Guard and Exit column clickable (aggregated view)

[Tor Bug Tracker & Wiki]

#24402: Make numbers in Guard and Exit column clickable (aggregated view)
---+
 Reporter:  cypherpunks|  Owner:  irl
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by irl):

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


Comment:

 Fixed in e50d28c.

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

Re: [tor-bugs] #24402 [Metrics/Atlas]: Make numbers in Guard and Exit column clickable (aggregated view)

[Tor Bug Tracker & Wiki]

#24402: Make numbers in Guard and Exit column clickable (aggregated view)
---+--
 Reporter:  cypherpunks|  Owner:  irl
 Type:  enhancement| Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by irl):

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


Comment:

 Moving into my queue.

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

Re: [tor-bugs] #23968 [Applications/Tor Browser]: NoScript icon jumps to the right after update

[Tor Bug Tracker & Wiki]

#23968: NoScript icon jumps to the right after update
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  reopened
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  noscript  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 I wrote about NoScript icon jumping in 7.0.10. I couldn't reproduce on a
 clean extract. I should have checked that before posting, I'm sorry about
 that. The extract that I used had extra add-ons installed, umatrix and
 ublock 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] #23696 [Core Tor/Tor]: Bug: scheduler_kist.c:520: kist_scheduler_schedule: Non-fatal assertion !((diff < 0)) failed.

[Tor Bug Tracker & Wiki]

#23696: Bug: scheduler_kist.c:520: kist_scheduler_schedule: Non-fatal assertion
!((diff < 0)) failed.
-+-
 Reporter:  cypherpunks  |  Owner:  (none)
 Type:  defect   | Status:
 |  reopened
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, tor-sched, easy, |  Actual Points:
  0.3.2.2-alpha-must |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

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


Comment:

 After hibernation on Windows 7:
 {{{
 Tor WARN: tor_bug_occurred_(): Bug: scheduler_kist.c:530:
 kist_scheduler_schedule: Non-fatal assertion !((diff < 0)) failed. (Future
 instances of this warning will be silenced.) (on Tor 0.3.2.4-alpha )
 Tor WARN: Bug: Non-fatal assertion !((diff < 0)) failed in
 kist_scheduler_schedule at scheduler_kist.c:530. (Stack trace not
 available) (on Tor 0.3.2.4-alpha )
 }}}

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