Re: [tor-bugs] #25213 [Core Tor/Tor]: 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(), node)) failed.

2018-03-26 Thread Tor Bug Tracker & Wiki
#25213: 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(),
node)) failed.
-+-
 Reporter:  sjcjonker|  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, 033-must, regression,  |  Actual Points:
  033-triage-20180320, 033-included-20180320 |
Parent ID:  #20916   | Points:  0.5
 Reviewer:  teor |Sponsor:
-+-
Changes (by teor):

 * keywords:
 ipv6, 032-backport-maybe, 033-must, regression, 033-triage-20180320,
 033-included-20180320
 => ipv6, 033-must, regression, 033-triage-20180320,
 033-included-20180320
 * status:  needs_review => merge_ready


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25213 [Core Tor/Tor]: 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(), node)) failed.

2018-03-26 Thread Tor Bug Tracker & Wiki
#25213: 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(),
node)) failed.
-+-
 Reporter:  sjcjonker|  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, 032-backport-maybe, 033-must,  |  Actual Points:
  regression, 033-triage-20180320,   |
  033-included-20180320  |
Parent ID:  #20916   | Points:  0.5
 Reviewer:  teor |Sponsor:
-+-

Comment (by teor):

 This looks like the correct fix.

 (We should ignore routerinfos whenever we are using microdescriptors, so
 this change is correct. There's a lot of code that will need a similar fix
 eventually. Maybe some accessor functions would help? Or maybe we could
 just stop parsing descriptors when we use microdescriptors.)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25631 [Core Tor/Stem]: Integration tests set up and publish descriptors for an exit relay

2018-03-26 Thread Tor Bug Tracker & Wiki
#25631: Integration tests set up and publish descriptors for an exit relay
---+--
 Reporter:  dmr|  Owner:  dmr
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer:  atagar |Sponsor:
---+--

Comment (by dmr):

 Replying to [comment:4 dmr]:
 > `ProtocolWarnings 1`, `SafeLogging 0`, and `LogTimeGranularity 1` all
 look good; I'll file that as another trac ticket just because I feel they
 constitute an enhancement, not a defect. :)
 Filed; see #25632

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25055 [Core Tor/Tor]: string_is_valid_hostname() returns true for IPv4 addresses

2018-03-26 Thread Tor Bug Tracker & Wiki
#25055: string_is_valid_hostname() returns true for IPv4 addresses
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  IPv6, IPv4, tor-dns, 032-backport,   |  Actual Points:
  033-must, review-group-34, |
  033-triage-20180320, 033-included-20180320 |
Parent ID:  #25036   | Points:  1
 Reviewer:  mikeperry|Sponsor:
-+-

Comment (by mikeperry):

 nickm: Naming this appropriately is a good idea. I like
 string_is_valid_nonrfc_hostname() and a warning comment. Technically the
 function allows things like luck.y13 (which is explicitly tested in the
 unit tests), but that is not any kind of valid DNS name or IP.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25631 [Core Tor/Stem]: Integration tests set up and publish descriptors for an exit relay

2018-03-26 Thread Tor Bug Tracker & Wiki
#25631: Integration tests set up and publish descriptors for an exit relay
---+--
 Reporter:  dmr|  Owner:  dmr
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:  atagar
  Sponsor: |
---+--
 Some support for talking with Tor's ORPort has recently made it to stem
 (see #18856).

 Integration tests thus needed to set up a relay with ORPort in the torrc.
 3fe2221ae2bad6d826c05fd0ce96e5c09a21fc01 did this, but the defaults for a
 relay are to publish descriptors and act as an exit. Both of these are
 undesirable for stem's integration tests.

 The corresponding torrc options to disable these are:
 * `ExitRelay 0`
 * `PublishServerDescriptor 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] #25630 [Core Tor/Tor]: Bug: 3-hop circuit 0x55e55d447270 with purpose 5 has no guard state

2018-03-26 Thread Tor Bug Tracker & Wiki
#25630: Bug: 3-hop circuit 0x55e55d447270 with purpose 5 has no guard state
--+--
 Reporter:  meejah|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by arma):

 To be clear, this is the controller creating circuits using the
 EXTENDCIRCUIT option. So it is not surprising that the circuit doesn't
 have a guard state.

 I guess the two main options are to somehow cobble together a guard state
 for circuits that are made over the control port, or go through all the
 various consistency checks and provide exceptions for circuits that were
 made over the controller.

 (I think we don't even know that they were made over the controller, by
 the point of many of the consistency checks. We could add an internal flag
 to remind us about whether they were, if that helps.)

 And as another minor fix, it seems clear that
 circuit_purpose_may_omit_guard() should be ok with
 CIRCUIT_PURPOSE_CONTROLLER circs not having guard state.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25631 [Core Tor/Stem]: Integration tests set up and publish descriptors for an exit relay

2018-03-26 Thread Tor Bug Tracker & Wiki
#25631: Integration tests set up and publish descriptors for an exit relay
---+--
 Reporter:  dmr|  Owner:  dmr
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer:  atagar |Sponsor:
---+--
Changes (by dmr):

 * status:  assigned => needs_review


Comment:

 atagar:
 I've rebased the original patch for this and pushed the commit up to a
 public repo on github.
 `g...@github.com:dmr-x/stem.git` branch `25631-integ-torrc` commit
 `2a91f9e35f6bd7f40d1894128b0a362aa359dae4`

 web links:
 https://github.com/dmr-x/stem/tree/25631-integ-torrc
 https://github.com/dmr-x/stem/commit/2a91f9e35f6bd7f40d1894128b0a362aa359dae4

 Please 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

[tor-bugs] #25632 [Core Tor/Stem]: Improve stem torrc logging options for integration testing

2018-03-26 Thread Tor Bug Tracker & Wiki
#25632: Improve stem torrc logging options for integration testing
---+
 Reporter:  dmr|  Owner:  atagar
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 As suggested by teor in #25631, utilizing the following options in torrc
 will improve logging for the purpose of integration testing in stem:
 * `ProtocolWarnings 1`
 * `SafeLogging 0`
 * `LogTimeGranularity 1`

 The former (`ProtocolWarnings 1`) should be used in general with a local
 test relay (i.e. during development, independent of integration testing),
 and the log `[warn]`ings surfaced automatically in integration tests,
 which I believe currently isn't the case. The `[warn]`ings should
 potentially be treated as test failures when emitted (with exception of
 tests that directly try to violate the protocol, and check that Tor
 responds as such).

 The latter two will help with debugging when a problem is encountered.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25631 [Core Tor/Stem]: Integration tests set up and publish descriptors for an exit relay

2018-03-26 Thread Tor Bug Tracker & Wiki
#25631: Integration tests set up and publish descriptors for an exit relay
---+--
 Reporter:  dmr|  Owner:  dmr
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer:  atagar |Sponsor:
---+--

Comment (by dmr):

 teor:
 I don't fully get the `AssumeReachable` option.
 I'm running `Tor 0.3.2.10 (git-0edaa32732ec8930)` and this is what my `man
 torrc` says:

 {{{
 AssumeReachable 0|1
 This option is used when bootstrapping a new Tor network. If set to 1,
 don’t do self-reachability
 testing; just upload your server descriptor immediately. If
 AuthoritativeDirectory is also set, this
 option instructs the dirserver to bypass remote reachability testing
 too and list all connected
 servers as running.
 }}}

 I'm assuming that the part about `just upload your server descriptor
 immediately` is moot with `PublishServerDescriptor 0`, although that's not
 quite clear from the manual. So I'm assuming the combo means `don’t do
 self-reachability testing`, which //does// sound quite appropriate for a
 local test relay, although I'm not sure what reachability testing looks
 like. (Just thought I'd ping you for confirmation and a potential learning
 opportunity for me.)


 `ProtocolWarnings 1`, `SafeLogging 0`, and `LogTimeGranularity 1` all look
 good; I'll file that as another trac ticket just because I feel they
 constitute an enhancement, not a defect. :)

 `SOCKSPort 0` doesn't make sense - at least //not right now//. There's
 only a chief torrc used as the base for integration tests in stem, many of
 which rely on the SocksPort.

 I would agree that it makes sense in the future to split this up into
 multiple torrc sets for different tests.

 Thanks again for the feedback! :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25630 [Core Tor/Tor]: Bug: 3-hop circuit 0x55e55d447270 with purpose 5 has no guard state

2018-03-26 Thread Tor Bug Tracker & Wiki
#25630: Bug: 3-hop circuit 0x55e55d447270 with purpose 5 has no guard state
--+--
 Reporter:  meejah|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 After discussion on #tor-dev, arma told me to file this; I am hitting this
 for every circuit my exit-scanner creates when using tor master
 (0eed0899cdeadd84).

 The circuits created all start with a current guard (but probably not any
 of "my" current guards). I've tried with both purpose=general and
 purpose=controller but the result is the same (except for the 5 vs 21 in
 the error message)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25631 [Core Tor/Stem]: Integration tests set up and publish descriptors for an exit relay

2018-03-26 Thread Tor Bug Tracker & Wiki
#25631: Integration tests set up and publish descriptors for an exit relay
---+--
 Reporter:  dmr|  Owner:  dmr
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer:  atagar |Sponsor:
---+--

Comment (by teor):

 You might want some of the other options from endosome's test relay
 script:
 {{{
 AssumeReachable 1
 ProtocolWarnings 1
 SafeLogging 0
 LogTimeGranularity 1
 SOCKSPort 0
 }}}
 https://github.com/teor2345/endosome/blob/master/relay-local.sh

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25631 [Core Tor/Stem]: Integration tests set up and publish descriptors for an exit relay

2018-03-26 Thread Tor Bug Tracker & Wiki
#25631: Integration tests set up and publish descriptors for an exit relay
---+--
 Reporter:  dmr|  Owner:  dmr
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer:  atagar |Sponsor:
---+--
Changes (by dmr):

 * status:  needs_review => assigned


Comment:

 teor: thanks! Looking over those options now. Assigning self again.

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

Re: [tor-bugs] #25605 [Core Tor/Tor]: Add tests for Rust protover::compute_for_old_tor() and C functions it calls

2018-03-26 Thread Tor Bug Tracker & Wiki
#25605: Add tests for Rust protover::compute_for_old_tor() and C functions it 
calls
-+-
 Reporter:  isis |  Owner:  isis
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  033-must, fast-fix,  |  Actual Points:
  033-triage-20180326, 033-included-20180326 |
Parent ID:   | Points:  1
 Reviewer:  nickm|Sponsor:
 |  Sponsor8-can
-+-
Changes (by nickm):

 * status:  needs_review => needs_revision


Comment:

 On the routerparse tor_version_parse tests:
  * let's make sure that these tests check the contents of the 'out'
 structure.
  * You don't need to say "if (foo) tor_free(foo)" -- all of our free
 functions accept NULL.

 Otherwise this looks fine to me.  I'm marking it needs_revision because of
 the two issues above, and because it will need to get rebased onto a later
 version of #25386.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25605#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
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] #24031 [Core Tor/Tor]: Protover.rs could use a better algorithm

2018-03-26 Thread Tor Bug Tracker & Wiki
#24031: Protover.rs could use a better algorithm
-+-
 Reporter:  nickm|  Owner:  isis
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  rust, 033-must, protover, security,  |  Actual Points:  5
  033-triage-20180326, 033-included-20180326 |
Parent ID:   | Points:  1
 Reviewer:  nickm|Sponsor:
 |  SponsorM-can
-+-

Comment (by nickm):

 Also -- could I have this as a github pull request, or failing that, as a
 gitlab pull request?  I'd like to try reviewing this with a UI, since the
 patch series is >3k lines long :)

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24031#comment:21>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
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] #25606 [Applications/Tor Browser]: Unable to change master password

2018-03-26 Thread Tor Bug Tracker & Wiki
#25606: Unable to change master password
--+---
 Reporter:  etienne   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:  master password   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by gk):

 * owner:  (none) => tbb-team
 * resolution:   => duplicate
 * status:  new => closed
 * component:  - Select a component => Applications/Tor Browser


Comment:

 Yes, #13510 has not been fixed yet. So, this ticket is a duplicate of 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] #23811 [Applications/Tor Browser]: Investigate MinGW commit for create_locale thing

2018-03-26 Thread Tor Bug Tracker & Wiki
#23811: Investigate MinGW commit for create_locale thing
--+--
 Reporter:  tom   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-rbm, ff60-esr |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * keywords:  tbb-rbm => tbb-rbm, ff60-esr


Comment:

 I think I still hit that one while trying to get Stylo cross-compiled but
 I should doublecheck that to be extra sure.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24229 [Metrics/Website]: Provide BGP Data Collection on Tor Metrics

2018-03-26 Thread Tor Bug Tracker & Wiki
#24229: Provide BGP Data Collection on Tor Metrics
-+---
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by iwakeh):

 Should the 'contrib' path be part of index.json?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25624 [Metrics/CollecTor]: Index 'contrib' directory

2018-03-26 Thread Tor Bug Tracker & Wiki
#25624: Index 'contrib'  directory
---+--
 Reporter:  iwakeh |  Owner:  metrics-team
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:  #24229
   Points: |   Reviewer:
  Sponsor: |
---+--
 Add the future 'contrib' as base-path to index.json (see parent 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

Re: [tor-bugs] #13510 [Applications/Tor Browser]: Master password can't be changed from default

2018-03-26 Thread Tor Bug Tracker & Wiki
#13510: Master password can't be changed from default
--+--
 Reporter:  User11|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-usability |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * cc: etienne (added)


Comment:

 #25606 is a duplicate.

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

Re: [tor-bugs] #25444 [Metrics/Library]: Add Apache Commons Codec dependency for java 9 (was: Add jaxb dependency explicitly for java 9)

2018-03-26 Thread Tor Bug Tracker & Wiki
#25444: Add Apache Commons Codec dependency for java 9
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  defect   | Status:  new
 Priority:  Low  |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25443   | Points:
 Reviewer:   |Sponsor:
-+--
Description changed by iwakeh:

Old description:

> jaxb dependency needs to be added explicitly when using java 9
>
> The implementation of jaxb is not part of standard java9 se anymore (it
> is part of java ee).
>
> This can be fixed by adding the 'jaxb-core' jar, which is available as
> part of debian package 'libjaxb-java'.

New description:

 (see comments)

 === old version
 jaxb dependency needs to be added explicitly when using java 9

 The implementation of jaxb is not part of standard java9 se anymore (it is
 part of java ee).

 This can be fixed by adding the 'jaxb-core' jar, which is available as
 part of debian package 'libjaxb-java'.

--

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24229 [Metrics/Website]: Provide BGP Data Collection on Tor Metrics

2018-03-26 Thread Tor Bug Tracker & Wiki
#24229: Provide BGP Data Collection on Tor Metrics
-+---
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by karsten):

 Replying to [comment:9 iwakeh]:
 > Should the 'contrib' path be part of index.json?

 I think that makes sense, yes.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25615 [Core Tor/Nyx]: Can not use nyx with Tor 0.3.2.10 to display like ARM

2018-03-26 Thread Tor Bug Tracker & Wiki
#25615: Can not use nyx with Tor 0.3.2.10 to display like ARM
--+
 Reporter:  basicnote |  Owner:  atagar
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Nyx  |Version:  Tor: 0.3.2.10
 Severity:  Normal| Resolution:
 Keywords:  Nyx, tor  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by basicnote):

 Yes, it worked when i added ControlPort [] CookieAuthentication 1 to
 my torrc. Nyx linked with Tor to display.
 Thanks your and your projects' efforts, and you reply.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25622 [Applications/Tor Browser]: Investigate setting MOZ_DISABLE_NONLOCAL_CONNECTIONS to prevent proxy bypasses

2018-03-26 Thread Tor Bug Tracker & Wiki
#25622: Investigate setting MOZ_DISABLE_NONLOCAL_CONNECTIONS to prevent proxy
bypasses
-+-
 Reporter:  gk   |  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  ff60-esr, tbb-proxy-
 Severity:  Normal   |  bypass
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 It turns out Mozilla has an environment variable,
 MOZ_DISABLE_NONLOCAL_CONNECTIONS, that might be helpful for preventing
 proxy bypasses or, if that's not the case right now, it might be patched
 so that it does indeed function as one would expect. See:
 https://lists.torproject.org/pipermail/tbb-dev/2018-March/000818.html for
 more 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] #21588 [Metrics/Statistics]: Rewrite the censorship detector used by the Tor Metrics website in Java

2018-03-26 Thread Tor Bug Tracker & Wiki
#21588: Rewrite the censorship detector used by the Tor Metrics website in Java
+--
 Reporter:  karsten |  Owner:  karsten
 Type:  enhancement | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2018|  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by iwakeh):

 Regarding distribution fitting, which is currently done by scipy and used
 as part of the detector:

 Scipy didn't re-implement the functionality, but uses minpack
 (www.netlib.org/minpack).  We briefly discussed using minpack (written in
 Fortran) via JNI.  This will lead to having an additional dependency for
 debian packages 'libcminpack1' (currently installed as dependency of
 scipy) and also provide that in the java library classpath.  In addition,
 an interface would need to be created to access the used functions (hybrd,
 hybrj etc.) natively.  All in all more fragile 'plumbing' than calling
 scipy from java.

 Next steps:
 * decide, if the native access should really be implemented using Java
 * create a new package `org.torproject.metrics.math` for the functionality
 regarding distribution fitting and other advanced optimization math for
 detection and other purposes.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25624 [Metrics/CollecTor]: Index 'contrib' directory

2018-03-26 Thread Tor Bug Tracker & Wiki
#25624: Index 'contrib'  directory
---+--
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #24229 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by iwakeh):

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


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

Re: [tor-bugs] #25600 [Obfuscation/Snowflake]: Running 2 instances of snowflake-client leads to the former one stopping

2018-03-26 Thread Tor Bug Tracker & Wiki
#25600: Running 2 instances of snowflake-client leads to the former one stopping
---+---
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:  not a bug
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by cypherpunks):

 I'm definitely noticing that after dozens of minutes of inactivity tor
 eventually hits:

 {{{
 Delaying directory fetches: No running bridges
 Application request when we haven't received a consensus with exits.
 Optimistically trying known bridges again.
 }}}

 Restarting the affected program solves the issue. But I'm not sure if this
 is a consequence of the proxy changes that you were mentioning.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22170 [Applications/Tor Browser]: Check uses of ch.boye.httpclientandroidlib.impl.client.* for proxy safety on Android

2018-03-26 Thread Tor Bug Tracker & Wiki
#22170: Check uses of ch.boye.httpclientandroidlib.impl.client.* for proxy 
safety
on Android
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-mobile,|  Actual Points:
  TorBrowserTeam201803   |
Parent ID:  #21863   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * parent:  #5709 => #21863


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19076 [Applications/Tor Browser]: Make sure that networking code in AndroidMediaResourceServer is no problem for OrFox

2018-03-26 Thread Tor Bug Tracker & Wiki
#19076: Make sure that networking code in AndroidMediaResourceServer is no 
problem
for OrFox
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile|  Actual Points:
Parent ID:  #21863| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * parent:  #5709 => #21863


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22171 [Applications/Tor Browser]: Review networking calls in esr45-esr52 diff of ./android/* closer

2018-03-26 Thread Tor Bug Tracker & Wiki
#22171: Review networking calls in esr45-esr52 diff of ./android/* closer
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff52-esr, tbb-mobile  |  Actual Points:
Parent ID:  #21863| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * parent:  #5709 => #21863


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25619 [Applications/Tor Browser]: The webrtc build downloads and runs a cipd program

2018-03-26 Thread Tor Bug Tracker & Wiki
#25619: The webrtc build downloads and runs a cipd program
--+--
 Reporter:  dcf   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  invalid
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dcf):

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


Comment:

 Replying to [comment:1 gk]:
 > I don't have this message in my log file dating from last Friday.

 Aha, thanks for checking.

 I think I just realized the cause: I found I needed a more recent
 depot_tools in order to build a more recent webrtc. It must be a new
 behavior with a newer depot_tools. In other words, it's my problem, not
 yours :) I'll see if I can find a way to disable this behavior in my
 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] #21588 [Metrics/Statistics]: Rewrite the censorship detector used by the Tor Metrics website in Java

2018-03-26 Thread Tor Bug Tracker & Wiki
#21588: Rewrite the censorship detector used by the Tor Metrics website in Java
+--
 Reporter:  karsten |  Owner:  karsten
 Type:  enhancement | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2018|  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by iwakeh):

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


Comment:

 Assigning to karsten as he is already working on 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] #25623 [Applications/Tor Browser]: Disable network during build

2018-03-26 Thread Tor Bug Tracker & Wiki
#25623: Disable network during build
--+--
 Reporter:  boklm |  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-rbm
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 In order to detect issues such as #25619 where some component is
 downloading files during its build, we should disable network in the
 container during the build step.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19077 [Applications/Tor Browser]: Make sure that networking code in sutagent is no problem for OrFox

2018-03-26 Thread Tor Bug Tracker & Wiki
#19077: Make sure that networking code in sutagent is no problem for OrFox
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile|  Actual Points:
Parent ID:  #21863| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * parent:  #5709 => #21863


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25444 [Metrics/Library]: Add jaxb dependency explicitly for java 9

2018-03-26 Thread Tor Bug Tracker & Wiki
#25444: Add jaxb dependency explicitly for java 9
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  defect   | Status:  new
 Priority:  Low  |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25443   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 Yes, that's true we removed that dependency a while ago.  Let's simply add
 Apache Commons Codec again.

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

Re: [tor-bugs] #22551 [Applications/Tor Browser]: F-Droid's Orfox APK file not updated to Tor Browser 7.0 yet

2018-03-26 Thread Tor Bug Tracker & Wiki
#22551: F-Droid's Orfox APK file not updated to Tor Browser 7.0 yet
--+
 Reporter:  cypherpunks   |  Owner:  n8fr8
 Type:  defect| Status:  closed
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:  fixed
 Keywords:  tbb-mobile|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by gk):

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


Comment:

 Fixed a while back.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25620 [Internal Services/Service - git]: Create user/dcf/tor-browser-build repo

2018-03-26 Thread Tor Bug Tracker & Wiki
#25620: Create user/dcf/tor-browser-build repo
-+
 Reporter:  dcf  |  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+
 Please create a new repo for me,
   user/dcf/tor-browser-build
 Description is
   David F.'s tor-browser-build repository

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21588 [Metrics/Statistics]: Rewrite the censorship detector used by the Tor Metrics website in Java

2018-03-26 Thread Tor Bug Tracker & Wiki
#21588: Rewrite the censorship detector used by the Tor Metrics website in Java
+--
 Reporter:  karsten |  Owner:  karsten
 Type:  enhancement | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2018|  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by karsten):

 Hmm, okay, that sounds like we need to choose the least bad solution.

 If we go for calling scipy from Java, let's at least reduce that to a
 single call and not create a Python process for each `norm.fit` call. We
 could write all input data to a file, call Python to fit normal
 distributions and write an output file, and read that in Java. Not pretty,
 but that at least reduces overhead a bit.

 Are there really no native Java libraries that do the same thing?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22059 [Applications/Tor Browser]: Remove screencasting code on mobile as well

2018-03-26 Thread Tor Bug Tracker & Wiki
#22059: Remove screencasting code on mobile as well
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, tbb-proxy-bypass  |  Actual Points:
Parent ID:  #21863| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * parent:  #5709 => #21863


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25621 [Internal Services/Service - git]: Please delete 52.6.2esr related tags and branches from tor-browser.git

2018-03-26 Thread Tor Bug Tracker & Wiki
#25621: Please delete 52.6.2esr related tags and branches from tor-browser.git
-+
 Reporter:  gk   |  Owner:  tor-gitadm
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+
 It turns out that I wrongly pushed `tor-browser-52.6.2esr-7.5-1-build1`,
 `tor-browser-52.6.2esr-7.5-1`, and `tor-browser-52.6.2esr-7.5-2` to `tor-
 browser.git` a while ago. There has never been a planned ESR 52.6.2
 release. Please remove those branches/tag as this is confusing.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25624 [Metrics/CollecTor]: Index 'contrib' directory

2018-03-26 Thread Tor Bug Tracker & Wiki
#25624: Index 'contrib'  directory
---+--
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #24229 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by iwakeh):

 * status:  accepted => needs_review


Comment:

 Please review
 [https://gitweb.torproject.org/user/iwakeh/collector.git/commit/?h=task-25624
 this 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] #16472 [Applications/Tor Browser]: Upgrade Binutils to 2.25+ for Tor Browser builds

2018-03-26 Thread Tor Bug Tracker & Wiki
#16472: Upgrade Binutils to 2.25+ for Tor Browser builds
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  reopened
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201803,   |  Actual Points:
  boklm201803|
Parent ID:  #12968   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-rbm, TorBrowserTeam201803R, boklm201803 => tbb-rbm,
 TorBrowserTeam201803, boklm201803


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25616 [Core Tor/Tor]: Non-fatal assertion in hs_desc_encode_descriptor similar to #24972

2018-03-26 Thread Tor Bug Tracker & Wiki
#25616: Non-fatal assertion in hs_desc_encode_descriptor similar to #24972
-+-
 Reporter:  alnsn|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.10
 Severity:  Normal   | Resolution:
 Keywords:  regression, tor-hs, 033-backport,|  Actual Points:
  032-backport   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

 * keywords:   => regression, tor-hs, 033-backport, 032-backport
 * priority:  Medium => High
 * milestone:   => Tor: 0.3.4.x-final


Comment:

 Yes, very much like #24792 and the extra logging added paid off: Key part
 of the log from above:

 {{{
  Mar 24 08:40:25.000 [warn] Invalid signature for service descriptor
 signing key: expired
 }}}

 I think we might have an issue with clock jump between descriptor creation
 and encoding...

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24527 [Applications/Tor Launcher]: Inform users in Tor Launcher of which settings are best for them based on their country

2018-03-26 Thread Tor Bug Tracker & Wiki
#24527: Inform users in Tor Launcher of which settings are best for them based 
on
their country
---+---
 Reporter:  hellais|  Owner:  brade
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ux-team|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by antonela):

 * cc: antonela (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] #24661 [Core Tor/Tor]: accept a reasonably live consensus for guard selection

2018-03-26 Thread Tor Bug Tracker & Wiki
#24661: accept a reasonably live consensus for guard selection
-+-
 Reporter:  catalyst |  Owner:
 |  catalyst
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  bootstrap, clock-skew,   |  Actual Points:
  s8-bootstrap, s8-errors, ux,   |
  033-triage-20180320, 034-roadmap-proposed  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by nickm):

 * milestone:  Tor: 0.3.3.x-final => Tor: 0.3.4.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

[tor-bugs] [Tor Bug Tracker & Wiki] Batch modify: #25248, #24342, #24544

2018-03-26 Thread Tor Bug Tracker & Wiki
Batch modification to #25248, #24342, #24544 by nickm:


--
Tickets URL: 

Tor Bug Tracker & Wiki 
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] #25581 [Core Tor/Tor]: Inconsistent underscore config options (for vanguard options)

2018-03-26 Thread Tor Bug Tracker & Wiki
#25581: Inconsistent underscore config options (for vanguard options)
-+-
 Reporter:  atagar   |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Minor| Resolution:
 Keywords:  regression, 033-must,|  Actual Points:
  033-triage-20180326, 033-included-20180326 |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  accepted => needs_review


Comment:

 If you're okay with it, `bug25581_033` should be the necessary change.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25581#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
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] #25213 [Core Tor/Tor]: 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(), node)) failed.

2018-03-26 Thread Tor Bug Tracker & Wiki
#25213: 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(),
node)) failed.
-+-
 Reporter:  sjcjonker|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, 032-backport-maybe, 033-must,  |  Actual Points:
  regression, 033-triage-20180320,   |
  033-included-20180320  |
Parent ID:  #20916   | Points:  0.5
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 So, this bug will fix itself once enough authorities upgrade to
 0.3.3.1-alpha or later, since `networkstatus_consensus_has_ipv6()` implies
 that `node_awaiting_ipv6()` is never true.  But maybe we don't want to
 wait so long.

 I think the problem here is that `node->ri` is set, but
 `we_use_microdescriptors_for_circuits()` returns true and the `node->md`
 field is not 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] #25213 [Core Tor/Tor]: 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(), node)) failed.

2018-03-26 Thread Tor Bug Tracker & Wiki
#25213: 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(),
node)) failed.
-+-
 Reporter:  sjcjonker|  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, 032-backport-maybe, 033-must,  |  Actual Points:
  regression, 033-triage-20180320,   |
  033-included-20180320  |
Parent ID:  #20916   | Points:  0.5
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * cc: teor (added)
 * status:  accepted => needs_review


Comment:

 Please see branch `bug25213_033` for a possible fix made by changing
 `extend_info_from_node()`.  The alternative would be to change
 `node_awaiting_ipv6()`, but I'm not sure that's wise.

 Teor, do you have time to take a look at this?  It's small, and I think
 you know this logic well.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25313 [Core Tor/Tor]: Sandbox: Caught a bad syscall attempt (syscall poll)

2018-03-26 Thread Tor Bug Tracker & Wiki
#25313: Sandbox: Caught a bad syscall attempt (syscall poll)
-+-
 Reporter:  cypherpunks  |  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  sandbox, 033-must, crash,|  Actual Points:
  029-backport, 031-backport, 032-backport,  |
  033-triage-20180320, 033-included-20180320 |
Parent ID:   | Points:
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by dgoulet):

 * status:  needs_review => merge_ready
 * reviewer:   => dgoulet


Comment:

 Replying to [comment:5 nickm]:
 > trivial fix in branch `bug25313_029`

 Indeed, seems plausible. lgtm;

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25213 [Core Tor/Tor]: 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(), node)) failed.

2018-03-26 Thread Tor Bug Tracker & Wiki
#25213: 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(),
node)) failed.
-+-
 Reporter:  sjcjonker|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, 032-backport-maybe, 033-must,  |  Actual Points:
  regression, 033-triage-20180320,   |
  033-included-20180320  |
Parent ID:  #20916   | Points:  0.5
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 Interesting.  This is happening because `extend_info_from_node()` is
 calling `fascist_firewall_choose_address_node()` with a node that is
 `node_awaiting_ipv6()`.  But earlier in `extend_info_from_node()`, it
 checks:
 {{{
   if (node->ri == NULL && (node->rs == NULL || node->md == NULL))
 return NULL;
 }}}

 which suggests to me that the check above is inconsistent with
 `node_awaiting_ipv6()`.

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

Re: [tor-bugs] #25581 [Core Tor/Tor]: Inconsistent underscore config options (for vanguard options)

2018-03-26 Thread Tor Bug Tracker & Wiki
#25581: Inconsistent underscore config options (for vanguard options)
-+-
 Reporter:  atagar   |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Minor| Resolution:
 Keywords:  regression, 033-must,|  Actual Points:
  033-triage-20180326, 033-included-20180326 |
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:
-+-
Changes (by dgoulet):

 * reviewer:   => asn


--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25581#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
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] #21588 [Metrics/Statistics]: Rewrite the censorship detector used by the Tor Metrics website in Java

2018-03-26 Thread Tor Bug Tracker & Wiki
#21588: Rewrite the censorship detector used by the Tor Metrics website in Java
+--
 Reporter:  karsten |  Owner:  karsten
 Type:  enhancement | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2018|  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by iwakeh):

 Replying to [comment:9 karsten]:
 > Hmm, okay, that sounds like we need to choose the least bad solution.
 >
 > If we go for calling scipy from Java, let's at least reduce that to a
 single call and not create a Python process for each `norm.fit` call. We
 could write all input data to a file, call Python to fit normal
 distributions and write an output file, and read that in Java. Not pretty,
 but that at least reduces overhead a bit.

 Yep, let's be pragmatic.  I would still create the new package for the
 calls in case a different solution comes up.

 >
 > Are there really no native Java libraries that do the same thing?

 Fortran is well suited for scientific computations, why re-implement?
 Apache commons does re-implement  one algorithm by minpack in a simplified
 way and w/o any means to judge the quality.  The algorithm they provide
 doesn't give the good results scipy's choice of minpack algorithm
 delivers.  I didn't encounter any free Java implementation that would
 provide the functionality.  Maybe, Apache commons math will one day
 provide all the optimization algorithms.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] [Tor Bug Tracker & Wiki] Batch modify: #25440, #24031, #25605, #25581

2018-03-26 Thread Tor Bug Tracker & Wiki
Batch modification to #25440, #24031, #25605, #25581 by nickm:


Comment:
Marking 033-must tickets as included. Round 2.

--
Tickets URL: 

Tor Bug Tracker & Wiki 
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] [Tor Bug Tracker & Wiki] Batch modify: #24857, #25557

2018-03-26 Thread Tor Bug Tracker & Wiki
Batch modification to #24857, #25557 by nickm:


Comment:
Mark this tickets as removed.

--
Tickets URL: 
Tor Bug Tracker & Wiki 
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] #25213 [Core Tor/Tor]: 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(), node)) failed.

2018-03-26 Thread Tor Bug Tracker & Wiki
#25213: 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(),
node)) failed.
-+-
 Reporter:  sjcjonker|  Owner:  nickm
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, 032-backport-maybe, 033-must,  |  Actual Points:
  regression, 033-triage-20180320,   |
  033-included-20180320  |
Parent ID:  #20916   | Points:  0.5
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  new => accepted
 * owner:  (none) => nickm


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25625 [Metrics/Website]: Make CollecTor's file structure description part of Metrics-Web's CollecTor docs

2018-03-26 Thread Tor Bug Tracker & Wiki
#25625: Make CollecTor's file structure description part of Metrics-Web's 
CollecTor
docs
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 Transfer [PROTOCOL
 
https://gitweb.torproject.org/collector.git/tree/src/main/resources/docs/PROTOCOL]
 to some useful place and format in Metrics-Web.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25625 [Metrics/Website]: Make CollecTor's file structure description part of Metrics-Web's CollecTor docs

2018-03-26 Thread Tor Bug Tracker & Wiki
#25625: Make CollecTor's file structure description part of Metrics-Web's 
CollecTor
docs
-+--
 Reporter:  iwakeh   |  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:
-+--
Description changed by iwakeh:

Old description:

> Transfer [PROTOCOL
> https://gitweb.torproject.org/collector.git/tree/src/main/resources/docs/PROTOCOL]
> to some useful place and format in Metrics-Web.

New description:

 Transfer
 
[https://gitweb.torproject.org/collector.git/tree/src/main/resources/docs/PROTOCOL
 PROTOCOL] text file to some useful place and format in Metrics-Web.

--

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25557 [Core Tor/Tor]: DDOS on HiddenService

2018-03-26 Thread Tor Bug Tracker & Wiki
#25557: DDOS on HiddenService
-+-
 Reporter:  myxaxer  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.3-alpha
 Severity:  Major| Resolution:
 Keywords:  DDOS, HiddenService, |  Actual Points:
  033-triage-20180326, 033-removed-20180326  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * component:  - Select a component => Core Tor/Tor


--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25557#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
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] #24903 [Core Tor/Tor]: Bug: Line unexpectedly reached at pathbias_should_count at src/or/circpathbias.c:372

2018-03-26 Thread Tor Bug Tracker & Wiki
#24903: Bug: Line unexpectedly reached at pathbias_should_count at
src/or/circpathbias.c:372
-+-
 Reporter:  starlight|  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.9
 Severity:  Normal   | Resolution:
 Keywords:  tor-assert-nonfatal, regression?,|  Actual Points:
  033-must, 033-triage-20180320, |
  033-included-20180320  |
Parent ID:  #24907   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  accepted => needs_review


Comment:

 Likely fix in my branch `bug24903_029`.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #6767 [Core Tor/Tor]: tor crashes with Assertion smartlist_get(rl->old_routers, idx) == sd failed

2018-03-26 Thread Tor Bug Tracker & Wiki
#6767: tor crashes with Assertion smartlist_get(rl->old_routers, idx) == sd 
failed
-+-
 Reporter:  darkk|  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.2.37
 Severity:  Major| Resolution:
 Keywords:  tor-relay, crash, assertion, |  worksforme
  029-backport, 031-backport, needs-insight, |  Actual Points:
  033-triage-20180320, 033-included-20180320 |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  accepted => closed
 * keywords:
 tor-relay, crash, assertion, 029-backport, 031-backport, needs-
 insight, 033-must, 033-triage-20180320, 033-included-20180320
 =>
 tor-relay, crash, assertion, 029-backport, 031-backport, needs-
 insight, 033-triage-20180320, 033-included-20180320
 * resolution:   => worksforme
 * priority:  High => Medium


Comment:

 Hm. We have no reports of this since 0.2.8.x, and looking through the
 code, I'm not sure that it can.  I don't think this belongs in 0.3.3.x.
 Please reopen if this is actually happening with any supported version.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25213 [Core Tor/Tor]: 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(), node)) failed.

2018-03-26 Thread Tor Bug Tracker & Wiki
#25213: 0.3.3.2-alpha - Non-fatal assertion !(node_awaiting_ipv6(get_options(),
node)) failed.
-+-
 Reporter:  sjcjonker|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, 032-backport-maybe, 033-must,  |  Actual Points:
  regression, 033-triage-20180320,   |
  033-included-20180320  |
Parent ID:  #20916   | Points:  0.5
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 b66b62fb7525cac1e18385e130249ce24f5c9fea is the problem here: it removes
 the `node->ri` check, but doesn't make a corresponding change to
 `extend_info_from_node()`

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24903 [Core Tor/Tor]: Bug: Line unexpectedly reached at pathbias_should_count at src/or/circpathbias.c:372

2018-03-26 Thread Tor Bug Tracker & Wiki
#24903: Bug: Line unexpectedly reached at pathbias_should_count at
src/or/circpathbias.c:372
-+-
 Reporter:  starlight|  Owner:  nickm
 Type:  defect   | Status:
 |  needs_information
 Priority:  High |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.9
 Severity:  Normal   | Resolution:
 Keywords:  tor-assert-nonfatal, regression?,|  Actual Points:
  033-must, 033-triage-20180320, |
  033-included-20180320  |
Parent ID:  #24907   | Points:  1
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by dgoulet):

 * status:  needs_review => needs_information
 * reviewer:   => dgoulet


Comment:

 Replying to [comment:10 nickm]:
 > Likely fix in my branch `bug24903_029`.

 Wait, how can `onehop_tunnel` be equal to 1 there? I don't see a code path
 that allows the `EXTENDCIRCUIT` command to set that value to 1. I can't
 see a way to specify `CIRCLAUNCH_ONEHOP_TUNNEL` as an extend flag?

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

Re: [tor-bugs] #25380 [Core Tor/Tor]: Transparent proxy not working with linux kernel 4.15.6

2018-03-26 Thread Tor Bug Tracker & Wiki
#25380: Transparent proxy not working with linux kernel 4.15.6
-+-
 Reporter:  vafan|  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.9
 Severity:  Major| Resolution:  wontfix
 Keywords:  033-must, hang, 032-backport, 031|  Actual Points:
  -backport-maybe, 029-backport-maybe, 025   |
  -backport-maybe, regression?,  |
  033-triage-20180320, 033-included-20180320 |
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

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


Comment:

 I'm not sure if this should be handled on tor side. Unfortunately, seems
 the kernel broke this and fixed it later (?). I can see that 4.4.118 is
 not a thing anymore but rather 4.4.124 is the latest. And I bet they did
 since 4.14.24 fixed it according to earlier comment.

 I'm closing this because there are no actionable items for us. Please re-
 open if the kernel actually didn't fix it but I would personally avoid
 having #ifdef on the kernel version...

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25461 [Core Tor/Tor]: main event-loop spins consuming 100% of a CPU core at times

2018-03-26 Thread Tor Bug Tracker & Wiki
#25461: main event-loop spins consuming 100% of a CPU core at times
--+
 Reporter:  Dhalgren  |  Owner:  dgoulet
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.3-alpha
 Severity:  Normal| Resolution:
 Keywords:  performance   |  Actual Points:
Parent ID:  #25500| Points:
 Reviewer:|Sponsor:
--+
Changes (by dgoulet):

 * owner:  (none) => dgoulet
 * 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] #25402 [Metrics/Website]: Add `contrib` section to CollecTor's file structure protocol

2018-03-26 Thread Tor Bug Tracker & Wiki
#25402: Add `contrib` section to CollecTor's file structure protocol
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:  #24229   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

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


Comment:

 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] #25173 [Core Tor/Tor]: No Control Socket when DisableNetwork and User options are set

2018-03-26 Thread Tor Bug Tracker & Wiki
#25173: No Control Socket when DisableNetwork and User options are set
-+-
 Reporter:  iry  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.9
 Severity:  Normal   | Resolution:
 Keywords:  033-triage-20180320, |  Actual Points:
  033-removed-20180320   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * milestone:  Tor: 0.3.3.x-final => Tor: unspecified


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25624 [Metrics/CollecTor]: Index 'contrib' directory

2018-03-26 Thread Tor Bug Tracker & Wiki
#25624: Index 'contrib'  directory
---+
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID:  #24229 | 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] #25552 [Core Tor/Tor]: prop224: Onion service rev counters are useless and actually harmful for scalability

2018-03-26 Thread Tor Bug Tracker & Wiki
#25552: prop224: Onion service rev counters are useless and actually harmful for
scalability
+--
 Reporter:  asn |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor|Version:  Tor: 0.3.1.9
 Severity:  Normal  | Resolution:
 Keywords:  tor-hs prop224  |  Actual Points:
Parent ID:  | Points:  4
 Reviewer:  |Sponsor:
+--

Comment (by asn):

 WRT the replay cache idea of step (a) above, we probably do need a replay
 cache on the HSDirs, because there is a 24 hour window (before we change
 blinded pubkey) where HSDirs can replace the descriptors on other HSDirs
 with older versions of the descriptor. We probably want to avoid this and
 we should use a replay cache for this.

 The right way to use a replay cache here is to store the hash of the HSV3
 descriptor on the replay cache. '''We should investigate''' whether we
 need to hash the whole descriptor, or the whole descriptor minus the
 signature (in case the signature is malleable and an attacker can tweak it
 to bypass replay cache). If we need to do the latter approach, we should
 add the right data in `hs_cache_dir_descriptor_t` as part of
 `cache_dir_desc_new()`.

 Implementation plan for step (a) above:

 1) Introduce a global `replay_cache_t *hs_cache_replay_cache` in
 `hs_cache.c` next to `hs_cache_v3_dir`. We should index entries to this
 replay cache by blinded key, or maybe add an insertion timestamp so that
 we know when to clean it up.
 2 In `cache_store_v3_as_dir`, remove the revision counter check, and
 instead query the replay cache for whether we already have seen this
 descriptor before. If we have seen this descriptor before we should treat
 it the same way we treat descriptors with a smaller or equal revision
 counter right now, that is, reject them and `log_info`.
 3) We should clean up the replay cache when we are sure that the blinded
 key for a descriptor is now useless and will never be used by clients
 again. We should look in `rend-spec-v3.txt` to make sure when that is;
 probably at 24 or 48 hours or so.

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

Re: [tor-bugs] #21588 [Metrics/Statistics]: Rewrite the censorship detector used by the Tor Metrics website in Java

2018-03-26 Thread Tor Bug Tracker & Wiki
#21588: Rewrite the censorship detector used by the Tor Metrics website in Java
+--
 Reporter:  karsten |  Owner:  karsten
 Type:  enhancement | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics-2018|  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by iwakeh):

 * cc: metrics-team (added)


Comment:

 Adding metrics-team cc, b/c I only noticed the update by accident.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25604 [Core Tor/Tor]: V3 onion is critically unreliable since latest Tor update.

2018-03-26 Thread Tor Bug Tracker & Wiki
#25604: V3 onion is critically unreliable since latest Tor update.
--+---
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-hs|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by dgoulet):

 * keywords:   => tor-hs
 * component:  Core Tor => Core Tor/Tor
 * milestone:   => Tor: unspecified


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25374 [Core Tor/Tor]: Create a better-designed system for handling computation outside the event loop

2018-03-26 Thread Tor Bug Tracker & Wiki
#25374: Create a better-designed system for handling computation outside the 
event
loop
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Low   |  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25500| Points:
 Reviewer:|Sponsor:  Sponsor8
--+
Changes (by nickm):

 * owner:  (none) => nickm
 * status:  new => accepted


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

Re: [tor-bugs] #25373 [Core Tor/Tor]: Avoid needless wakeups for token bucket refills.

2018-03-26 Thread Tor Bug Tracker & Wiki
#25373: Avoid needless wakeups for token bucket refills.
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25500| Points:
 Reviewer:|Sponsor:  Sponsor8
--+
Changes (by nickm):

 * status:  new => accepted
 * owner:  (none) => nickm


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25616 [Core Tor/Tor]: Non-fatal assertion in hs_desc_encode_descriptor similar to #24972

2018-03-26 Thread Tor Bug Tracker & Wiki
#25616: Non-fatal assertion in hs_desc_encode_descriptor similar to #24972
-+-
 Reporter:  alnsn|  Owner:  dgoulet
 Type:  defect   | Status:
 |  accepted
 Priority:  High |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.10
 Severity:  Normal   | Resolution:
 Keywords:  regression, tor-hs, 032-backport,|  Actual Points:
  033-must 033-triage-20180326   |
  033-included-20180326  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

 * keywords:
 regression, tor-hs, 032-backport, 033-must regression
 033-triage-20180326 033-included-20180326
 =>
 regression, tor-hs, 032-backport, 033-must 033-triage-20180326
 033-included-20180326


Comment:

 One too many `regression` keyword.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25616#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
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] #25626 [Applications/Tor Browser]: NoScript whitelist contains Monero pools?

2018-03-26 Thread Tor Bug Tracker & Wiki
#25626: NoScript whitelist contains Monero pools?
--+--
 Reporter:  cypherpunks   |  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 cypherpunks):

 * Attachment "NoScript_whitelist2.png" 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] #25626 [Applications/Tor Browser]: NoScript whitelist contains Monero pools?

2018-03-26 Thread Tor Bug Tracker & Wiki
#25626: NoScript whitelist contains Monero pools?
--+--
 Reporter:  cypherpunks   |  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 cypherpunks):

 * Attachment "NoScript_whitelist1.png" 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] #25402 [Metrics/Website]: Add `contrib` section to CollecTor's file structure protocol

2018-03-26 Thread Tor Bug Tracker & Wiki
#25402: Add `contrib` section to CollecTor's file structure protocol
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #24229   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * status:  new => needs_review


Comment:

 Please review
 [https://gitweb.torproject.org/user/iwakeh/collector.git/commit/?h=task-25402
 this 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

[tor-bugs] [Tor Bug Tracker & Wiki] Batch modify: #25440, #24031, #25605, #24857, ...

2018-03-26 Thread Tor Bug Tracker & Wiki
Batch modification to #25440, #24031, #25605, #24857, #25557, #25581 by nickm:


Comment:
Second batch of triage for 0.3.3: tickets that we didn't cover the first time.

--
Tickets URL: 

Tor Bug Tracker & Wiki 
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] #24303 [Core Tor/Tor]: Tor fails to start if %include

2018-03-26 Thread Tor Bug Tracker & Wiki
#24303: Tor fails to start if %include
-+-
 Reporter:  littlefeather|  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.4-alpha
 Severity:  Major| Resolution:  user
 Keywords:  config, 033-triage-20180320, |  disappeared
  033-removed-20180320   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

 * status:  needs_information => closed
 * resolution:   => user disappeared


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25581 [Core Tor/Tor]: Inconsistent underscore config options (for vanguard options)

2018-03-26 Thread Tor Bug Tracker & Wiki
#25581: Inconsistent underscore config options (for vanguard options)
-+-
 Reporter:  atagar   |  Owner:  nickm
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Minor| Resolution:
 Keywords:  regression, 033-must,|  Actual Points:
  033-triage-20180326, 033-included-20180326 |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * owner:  (none) => nickm
 * status:  new => accepted
 * cc: asn (added)


Comment:

 Mike, George -- are you okay with changing these to double-underscore
 options and having the single-underscore case remain as a synonym for
 backward compatibility?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25581#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
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] #24775 [Core Tor/Tor]: Reduce "Channel padding timeout scheduled" NOTICE messages

2018-03-26 Thread Tor Bug Tracker & Wiki
#24775: Reduce "Channel padding timeout scheduled" NOTICE messages
-+-
 Reporter:  Dbryrtfbcbhgf|  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  032-backport, 031-backport,  |  duplicate
  033-must, annoyance, 033-triage-20180320,  |  Actual Points:
  033-included-20180320  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

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


Comment:

 Yes this is a duplicate of #22212. I confirm that master doesn't have this
 issue 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] #25013 [Applications/Tor Browser]: Move TorButton code to the tor browser repository

2018-03-26 Thread Tor Bug Tracker & Wiki
#25013: Move TorButton code to the tor browser repository
--+
 Reporter:  igt0  |  Owner:  tbb-team
 Type:  defect| Status:  needs_revision
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201803  |  Actual Points:
Parent ID:  #10760| Points:
 Reviewer:  gk, sysrqb, mcs,  |Sponsor:
--+

Comment (by igt0):

 sysrqb wrote about the downsides of trying to build the .xpi outside the
 tor-browser repo:

 https://trac.torproject.org/projects/tor/ticket/25260#comment:11

 I also updated the code fixing arthur's comments:

 ** bug 25013: Add Gecko build system infrastructure into tor button**
 
https://github.com/igortoliveira/torbutton/commit/86fc5398a573a43620ec3023d92207ce63def278

 **  bug 25013: Migrate general.useragent.locale to intl.locale.requested
 **
 
https://github.com/igortoliveira/torbutton/commit/b8443a3e75ed59283bdd52b875625534be1b96b7

 **  bug 25013: Update deprecated JS code **
 
https://github.com/igortoliveira/torbutton/commit/1b51d8afc0be10bf363b5387dbbfcd75ee021161

 **  bug 25013: Update XPCOM calls after changes in the interfaces **
 
https://github.com/igortoliveira/torbutton/commit/c68eea2c04d24e3cb47f707620365da1dbe8c7b2

 **  bug 25013: Initialize startup.homepage in the startup-observer
 component **
 
https://github.com/igortoliveira/torbutton/commit/cfef8182c6a5b4a294da98f0a5e71d80ce6f6472


 Replying to [comment:25 gk]:
 > I agree with Arthur (I have not looked at the Github commits but meant
 to +1 the bundling of the .xpi in the Torbutton repo and then getting that
 copied into the browser part later on.)

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

Re: [tor-bugs] #25375 [Core Tor/Tor]: Remove as many items as possible from second_elapsed_callback() and run_scheduled_events()

2018-03-26 Thread Tor Bug Tracker & Wiki
#25375: Remove as many items as possible from second_elapsed_callback() and
run_scheduled_events()
--+
 Reporter:  nickm |  Owner:  dgoulet
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25500| Points:
 Reviewer:|Sponsor:  Sponsor8
--+
Changes (by dgoulet):

 * owner:  (none) => dgoulet
 * 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] #25061 [Core Tor/Tor]: Relays consider it a bootstrapping failure if they can't extend for somebody else's circuit

2018-03-26 Thread Tor Bug Tracker & Wiki
#25061: Relays consider it a bootstrapping failure if they can't extend for
somebody else's circuit
-+-
 Reporter:  arma |  Owner:
 |  catalyst
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  backport-032, 033-must, stability,   |  Actual Points:
  033-triage-20180320, 033-included-20180320 |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by catalyst):

 * status:  new => assigned
 * owner:  (none) => catalyst


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25517 [Core Tor/Tor]: TROVE-2018-005

2018-03-26 Thread Tor Bug Tracker & Wiki
#25517: TROVE-2018-005
-+-
 Reporter:  isis |  Owner:  isis
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  trove, 033-must, security,   |  Actual Points:
  033-triage-20180320, 033-included-20180320 |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  new => assigned
 * owner:  (none) => isis


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25386 [Core Tor/Tor]: fix rust tests

2018-03-26 Thread Tor Bug Tracker & Wiki
#25386: fix rust tests
-+-
 Reporter:  Hello71  |  Owner:  Hello71
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  rust, tor-test, 033-backport,|  Actual Points:
  review-group-34|
Parent ID:   | Points:  3
 Reviewer:  isis |Sponsor:
 |  Sponsor8-can
-+-

Comment (by Hello71):

 probably fixed non-system 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] #25626 [Applications/Tor Browser]: NoScript whitelist contains Monero pools?

2018-03-26 Thread Tor Bug Tracker & Wiki
#25626: NoScript whitelist contains Monero pools?
--+--
 Reporter:  cypherpunks   |  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 cypherpunks):

 * Attachment "NoScript_whitelist3.png" 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] #25626 [Applications/Tor Browser]: NoScript whitelist contains Monero pools?

2018-03-26 Thread Tor Bug Tracker & Wiki
#25626: NoScript whitelist contains Monero pools?
--+--
 Reporter:  cypherpunks   |  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 cypherpunks):

 * Attachment "NoScript_whitelist4.png" 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] #25627 [Core Tor/Torsocks]: tsocks_gethostbyaddr_r scribbles garbage over data->hostname and then relies on it

2018-03-26 Thread Tor Bug Tracker & Wiki
#25627: tsocks_gethostbyaddr_r scribbles garbage over data->hostname and then
relies on it
---+-
 Reporter:  exarkun|  Owner:  dgoulet
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Torsocks  |Version:
 Severity:  Blocker| Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by exarkun):

 I left one line out (and don't have description edit permissions I guess).
 In the last code snippet, `he->h_name` is an alias for `data->hostname`.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25600 [Obfuscation/Snowflake]: Running 2 instances of snowflake-client leads to the former one stopping

2018-03-26 Thread Tor Bug Tracker & Wiki
#25600: Running 2 instances of snowflake-client leads to the former one stopping
---+---
 Reporter:  cypherpunks|  Owner:  (none)
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:  not a bug
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by dcf):

 Replying to [comment:4 cypherpunks]:
 > I'm definitely noticing that after dozens of minutes of inactivity tor
 eventually hits:
 >
 > {{{
 > Delaying directory fetches: No running bridges
 > Application request when we haven't received a consensus with exits.
 Optimistically trying known bridges again.
 > }}}
 >
 > Restarting the affected program solves the issue. But I'm not sure if
 this is a consequence of the proxy changes that you were mentioning.

 I've seen this too, not only with snowflake. I suspect it's actually a tor
 bug. Sometimes a loading tab in Tor Browser will stall, and I'll see this
 message. Then, I open another tab and go to a domain that doesn't have an
 existing circuit, and it will "un-stall" the first tab. It's like tor
 sometimes starts believing that none of its bridges are working, and
 refuses to even try again, until you ask for a new circuit.

 It may happen more often with snowflake because of #25429 (disconnects
 after 30 s). Some other tor-related tickets are #20379 (fixed in November
 2016) and #24392 (fixed in November 2018). I'm not sure if #24392 is fixed
 in a released Tor Browser 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] #25245 [Core Tor/Tor]: Crash in assert_connection_ok when changing Exit options

2018-03-26 Thread Tor Bug Tracker & Wiki
#25245: Crash in assert_connection_ok when changing Exit options
-+-
 Reporter:  toralf   |  Owner:  ahf
 Type:  defect   | Status:
 |  assigned
 Priority:  Very High|  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  crash, regression?, tor-exit, tor-   |  Actual Points:
  relay, ipv6, 033-must, 033-triage-20180320,|
  033-included-20180320  |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by ahf):

 * owner:  (none) => ahf
 * 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] #25616 [Core Tor/Tor]: Non-fatal assertion in hs_desc_encode_descriptor similar to #24972

2018-03-26 Thread Tor Bug Tracker & Wiki
#25616: Non-fatal assertion in hs_desc_encode_descriptor similar to #24972
-+-
 Reporter:  alnsn|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.10
 Severity:  Normal   | Resolution:
 Keywords:  regression, tor-hs, 032-backport,|  Actual Points:
  033-must regression|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  regression, tor-hs, 032-backport, 033-must => regression, tor-
 hs, 032-backport, 033-must regression


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25627 [Core Tor/Torsocks]: tsocks_gethostbyaddr_r scribbles garbage over data->hostname and then relies on it

2018-03-26 Thread Tor Bug Tracker & Wiki
#25627: tsocks_gethostbyaddr_r scribbles garbage over data->hostname and then
relies on it
---+-
 Reporter:  exarkun|  Owner:  dgoulet
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Torsocks  |Version:
 Severity:  Blocker| Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by exarkun):

 * Attachment "gethostbyaddr_r.patch" added.

 Patch with test and fix

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25608 [Webpages/Blog]: create blog username for kushal

2018-03-26 Thread Tor Bug Tracker & Wiki
#25608: create blog username for kushal
---+-
 Reporter:  steph  |  Owner:  hiro
 Type:  task   | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Webpages/Blog  |Version:
 Severity:  Normal | Resolution:  implemented
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by steph):

 * status:  new => closed
 * resolution:   => 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] #25616 [Core Tor/Tor]: Non-fatal assertion in hs_desc_encode_descriptor similar to #24972

2018-03-26 Thread Tor Bug Tracker & Wiki
#25616: Non-fatal assertion in hs_desc_encode_descriptor similar to #24972
-+-
 Reporter:  alnsn|  Owner:  dgoulet
 Type:  defect   | Status:
 |  accepted
 Priority:  High |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.10
 Severity:  Normal   | Resolution:
 Keywords:  regression, tor-hs, 032-backport,|  Actual Points:
  033-must regression 033-triage-20180326|
  033-included-20180326  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

 * status:  new => accepted
 * owner:  (none) => dgoulet


--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25616#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
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] #25508 [Core Tor/Tor]: Expose Tor's RNG to Rust

2018-03-26 Thread Tor Bug Tracker & Wiki
#25508: Expose Tor's RNG to Rust
+
 Reporter:  nickm   |  Owner:  (none)
 Type:  enhancement | Status:  new
 Priority:  Medium  |  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  roadmap, rust, rng  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:  SponsorQ
+

Comment (by isis):

 Possible duplicate of #24660?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24660 [Core Tor/Tor]: Wrap our PRNG interface(s) in Rust with appropriate traits

2018-03-26 Thread Tor Bug Tracker & Wiki
#24660: Wrap our PRNG interface(s) in Rust with appropriate traits
--+
 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, tor-crypto  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor3-can
--+

Comment (by isis):

 Marked #25508 as a potential duplicate of 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

Re: [tor-bugs] #21394 [Core Tor/Tor]: connection timeouts are affecting Tor Browser usability

2018-03-26 Thread Tor Bug Tracker & Wiki
#21394: connection timeouts are affecting Tor Browser usability
-+-
 Reporter:  arthuredelstein  |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  029-backport, 031-backport, tbb- |  Actual Points:
  performance, tbb-usability, performance, tbb-  |
  needs, 033-triage-20180320,|
  033-included-20180320  |
Parent ID:   | Points:
 Reviewer:  mikeperry|Sponsor:
-+-
Changes (by mikeperry):

 * reviewer:  nickm => mikeperry


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25616 [Core Tor/Tor]: Non-fatal assertion in hs_desc_encode_descriptor similar to #24972

2018-03-26 Thread Tor Bug Tracker & Wiki
#25616: Non-fatal assertion in hs_desc_encode_descriptor similar to #24972
-+-
 Reporter:  alnsn|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.10
 Severity:  Normal   | Resolution:
 Keywords:  regression, tor-hs, 032-backport,|  Actual Points:
  033-must regression 033-triaged-20180326   |
  033-included-20180326  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  regression, tor-hs, 032-backport, 033-must regression =>
 regression, tor-hs, 032-backport, 033-must regression
 033-triaged-20180326 033-included-20180326


--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25616#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
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] #25616 [Core Tor/Tor]: Non-fatal assertion in hs_desc_encode_descriptor similar to #24972

2018-03-26 Thread Tor Bug Tracker & Wiki
#25616: Non-fatal assertion in hs_desc_encode_descriptor similar to #24972
-+-
 Reporter:  alnsn|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.10
 Severity:  Normal   | Resolution:
 Keywords:  regression, tor-hs, 032-backport,|  Actual Points:
  033-must regression 033-triage-20180326|
  033-included-20180326  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:
 regression, tor-hs, 032-backport, 033-must regression
 033-triaged-20180326 033-included-20180326
 =>
 regression, tor-hs, 032-backport, 033-must regression
 033-triage-20180326 033-included-20180326


--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25616#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
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] #25347 [Core Tor/Tor]: Tor stops building circuits, and doesn't start when it has enough directory information

2018-03-26 Thread Tor Bug Tracker & Wiki
#25347: Tor stops building circuits, and doesn't start when it has enough 
directory
information
-+-
 Reporter:  teor |  Owner:  asn
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Normal   | Resolution:
 Keywords:  031-backport, 032-backport,  |  Actual Points:
  033-must, tor-guard, tor-client, tbb-  |
  usability-website, tbb-needs,  |
  033-triage-20180320, 033-included-20180320 |
Parent ID:  #21969   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by asn):

 * owner:  (none) => asn
 * 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

  1   2   >