Re: [tor-bugs] #24553 [Applications/Tor Browser]: Re-enable Alternate Services

[Tor Bug Tracker & Wiki]

#24553: Re-enable Alternate Services
---+--
 Reporter:  arthuredelstein|  Owner:  tbb-team
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ff59-esr, tbb-linkability  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by gk):

 * keywords:  ff59-esr => ff59-esr, tbb-linkability
 * type:  defect => enhancement


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24534 [Metrics/ExoneraTor]: Investigate Exonerator down times

[Tor Bug Tracker & Wiki]

#24534: Investigate Exonerator down times
+--
 Reporter:  atagar  |  Owner:  metrics-team
 Type:  defect  | Status:  new
 Priority:  High|  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Major   | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by iwakeh):

 Thanks for your reply!  No need to worry about db or application here,
 because my description above was unclear and hinted a wrong picture.
 Trying to do better:

 Of course, there is no percent sign in ipv6 addresses.  A query with an
 ipv6 address is percent encoded (%3A for `:`) and messing with that
 percent encoded url query triggered the very few warnings (<5 in several
 days), i.e., it is immediately identified as invalid in our code. Jetty
 validly logs a warning. ExoneraTor replies fine by stating that there was
 an invalid ip parameter.
 Thus, these few warnings have nothing to do with the ExoneraTor issue at
 hand.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24560 [Internal Services/Tor Sysadmin Team]: Can henryi have more memory?

[Tor Bug Tracker & Wiki]

#24560: Can henryi have more memory?
-+-
 Reporter:  tom  |  Owner:  tpa
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 I don't know if this is possible, but the consensus health generation
 script runs out of memory regularly.  I never set up alerting to be able
 to say exactly how often it occurs, but folks have noticed and told me
 it's stuck, and then magically gets fixed, so I would ballpark it at 2-3
 times every 2-3 days.

 How much more memory? Don't know. But we could try a gig more and see if
 that does 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] #20628 [Applications/Tor Browser]: More locales for Tor Browser

[Tor Bug Tracker & Wiki]

#20628: More locales for Tor Browser
--+--
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-torbutton, tbb-easy, ux-team  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by phoul):

 Updating the above "completed" list, it should now include:

 {{{
 Irish Gaelic
 Hebrew
 Indonesian
 }}}

 I have recently received a request asking about timelines for adding these
 three new languages.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24556 [Core Tor/Tor]: Non-fatal assertion !((*diff)->entry == NULL) failed in cdm_diff_ht_purge at ../src/or/consdiffmgr.c:329. Stack trace

[Tor Bug Tracker & Wiki]

#24556: Non-fatal assertion !((*diff)->entry == NULL) failed in 
cdm_diff_ht_purge
at ../src/or/consdiffmgr.c:329. Stack trace
--+
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.1.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * milestone:   => Tor: 0.3.2.x-final


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

Re: [tor-bugs] #24559 [Core Tor/Tor]: Move a comment to relay_send_end_cell_from_edge()

[Tor Bug Tracker & Wiki]

#24559: Move a comment to relay_send_end_cell_from_edge()
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  comment-only  |  Actual Points:  0.1
Parent ID:| Points:  0.1
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * status:  new => merge_ready


Comment:

 See my branch comment24559.

 I would so merge this straight away if I could :-)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24559 [Core Tor/Tor]: Move a comment to relay_send_end_cell_from_edge()

[Tor Bug Tracker & Wiki]

#24559: Move a comment to relay_send_end_cell_from_edge()
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  comment-only
Actual Points:  0.1   |  Parent ID:
   Points:  0.1   |   Reviewer:
  Sponsor:|
--+


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

Re: [tor-bugs] #24264 [Core Tor/Tor]: Enable IPv6 reachability testing for the Bridge Authority

[Tor Bug Tracker & Wiki]

#24264: Enable IPv6 reachability testing for the Bridge Authority
---+--
 Reporter:  isis   |  Owner:  isis
 Type:  task   | Status:  reopened
 Priority:  High   |  Milestone:
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  dirauth, bridgeauth, ipv6  |  Actual Points:
Parent ID: | Points:  .2
 Reviewer: |Sponsor:  SponsorM
---+--

Comment (by isis):

 I've disabled the setting for now, but I think I know what needs to be
 done to get it IPv6 working, or, at least, I've identified at least two
 problems in the current setup.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24558 [Core Tor/Tor]: enable expensive hardening message is wrong with static library builds

[Tor Bug Tracker & Wiki]

#24558: enable expensive hardening message is wrong with static library builds
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Very Low  |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Trivial   |   Keywords:  easy, intro
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 A user complained on IRC that using expensive hardening and static builds
 together resulted in this warning:
 {{{
 configure: error: The compiler supports -fsanitize=address, but for some
 reason I was not able to link when using it. Are you missing run-time
 support? With GCC you need libubsan.so, and with Clang you need
 libclang_rt.ubsan*
 }}}

 We should say that you need "libubsan.*" for GCC, because you need the
 static version for static builds.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23761 [Metrics/Website]: Add IPv6 relay graphs to metrics site

[Tor Bug Tracker & Wiki]

#23761: Add IPv6 relay graphs to metrics site
--+
 Reporter:  teor  |  Owner:  metrics-team
 Type:  enhancement   | Status:  needs_revision
 Priority:  Medium|  Milestone:
Component:  Metrics/Website   |Version:
 Severity:  Normal| Resolution:
 Keywords:  core-tor-wants, ipv6  |  Actual Points:  0.5
Parent ID:| Points:  1
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * status:  needs_review => needs_revision


Comment:

 {{{
 +A relay can support IPv6 by announcing an IPv6 address and port for the
 OR protocol, which may then be confirmed as reachable by the directory authorities, and by
 permitting exiting to IPv6 targets.
 }}}
 This sentence is hard to read, I suggest we split it into two sentences,
 one about ORPorts, and one about exiting.

 {{{
 +A bridge can support IPv6 by announcing an IPv6 address and port for the
 OR protocol.
 }}}
 This sentence could say that the bridge authority tests reachability, if
 #24264 gets fixed.


 {{{
 +confirmed: Whether the directory authorities have confirmed
 IPv6 OR
 +reachability by including an "a" line for a relay containing an IPv6
 address
 +("t") or not ("f"). If this column contains the empty
 string, all
 +running relays are included, regardless of whether their IPv6 address was
 found
 +reachable. Always the empty string for bridges.
 }}}

 This paragraph is slightly inaccurate: authorities do reachability *and*
 consistency checks on the IPv6 address announced by the relay. There is no
 IPv6 "a" line in the consensus if there is a tied vote on the address.

 Also, maybe we should say "a" line in the consensus. I don't think we need
 to specify NS consensus, because it will be both consensuses when
 authorities upgrade to 0.3.3 (#23826).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24557 [Metrics/Consensus Health]: Add a "NoIPv6Consensus" flag to consensus-health

[Tor Bug Tracker & Wiki]

#24557: Add a "NoIPv6Consensus" flag to consensus-health
--+-
 Reporter:  teor  |  Owner:  tom
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:
Component:  Metrics/Consensus Health  |Version:
 Severity:  Minor |   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 If a relay has different ReachableIPv6 addresses, and there is a tie for
 the most common ReachableIPv6 address, the authorities won't add any IPv6
 ORPort in the consensus.

 We could label the consensus column as NoIPv6Consensus in this case,
 instead of leaving it blank.

 If this does start happening more, it would be great to know about it. And
 it would also help relay operators in this situation.

 (See the discussion on the metrics list.)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23101 [Core Tor/Tor]: Predict and build specific HS purpose circuits (rather than GENERAL)

[Tor Bug Tracker & Wiki]

#23101: Predict and build specific HS purpose circuits (rather than GENERAL)
-+-
 Reporter:  mikeperry|  Owner:
 |  mikeperry
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, tor-guard, guard-discovery-  |  Actual Points:
  prop247-controller, review-group-27|
Parent ID:  #13837   | Points:
 Reviewer:  asn  |Sponsor:
-+-
Changes (by asn):

 * reviewer:   => asn


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24534 [Metrics/ExoneraTor]: Investigate Exonerator down times

[Tor Bug Tracker & Wiki]

#24534: Investigate Exonerator down times
+--
 Reporter:  atagar  |  Owner:  metrics-team
 Type:  defect  | Status:  new
 Priority:  High|  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Major   | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by irl):

 There should never be a % sign on global scoped IP addresses, I'm guessing
 someone was trying to enter link local addresses with an interface
 identifier? It might be worth catching all RFC1918 and RFC4193 addresses
 and just returning them as invalid without ever performing a query, as
 they should never appear in the database and would not have any real
 meaning if they did (they are explicitly not unique identifiers).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24203 [Core Tor/Tor]: Snowflake can't be configured to run with system tor: ENV-ERROR no TOR_PT_STATE_LOCATION environment variable

[Tor Bug Tracker & Wiki]

#24203: Snowflake can't be configured to run with system tor: ENV-ERROR no
TOR_PT_STATE_LOCATION environment variable
--+--
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Major | Resolution:
 Keywords:  snowflake |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by arlolra):

 > There might be some other problem in your setup. That ENV-ERROR comes
 from ​pt.MakeStateDir. But snowflake-client doesn't call pt.MakeStateDir;

 At least some point in the past it did, see:
 
https://github.com/keroserene/snowflake/commit/12922a232ba63bd8d94c92ced32e23aa2fb055ed

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24203 [Core Tor/Tor]: Snowflake can't be configured to run with system tor: ENV-ERROR no TOR_PT_STATE_LOCATION environment variable

[Tor Bug Tracker & Wiki]

#24203: Snowflake can't be configured to run with system tor: ENV-ERROR no
TOR_PT_STATE_LOCATION environment variable
--+--
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Major | Resolution:
 Keywords:  snowflake |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by dcf):

 Replying to [comment:3 cypherpunks]:
 > This seems to be the error when trying to launch it:
 >
 > {{{
 > ENV-ERROR no TOR_PT_STATE_LOCATION environment variable
 > }}}

 There might be some other problem in your setup. That ENV-ERROR comes from
 [https://gitweb.torproject.org/pluggable-
 transports/goptlib.git/tree/pt.go?h=0.7#n368 pt.MakeStateDir]. But
 snowflake-client doesn't call pt.MakeStateDir; only snowflake-server does.
 Are you use you copied the client to /usr/bin, and not the server? (Your
 comment:3 refers to /usr/bin/snowflake, but the ticket description refers
 to /usr/bin/snowflake-client.)

 snowflake-server wants access to $TOR_PT_STATE_LOCATION because that's
 where it caches its TLS certificates and keys.

 In any case, the problem is not that the executable was blocked from
 launching, because the error message comes from code inside the pluggable
 transport, not from tor.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24556 [Core Tor/Tor]: Non-fatal assertion !((*diff)->entry == NULL) failed in cdm_diff_ht_purge at ../src/or/consdiffmgr.c:329. Stack trace

[Tor Bug Tracker & Wiki]

#24556: Non-fatal assertion !((*diff)->entry == NULL) failed in 
cdm_diff_ht_purge
at ../src/or/consdiffmgr.c:329. Stack trace
--+--
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.1.9
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 #24086 similar/same?

 {{{
 tor_bug_occurred_(): Bug: ../src/or/consdiffmgr.c:329: cdm_diff_ht_purge:
 Non-fatal assertion !((*diff)->entry == NULL) failed. (on Tor 0.3.1.9 )
  Bug: Non-fatal assertion !((*diff)->entry == NULL) failed in
 cdm_diff_ht_purge at ../src/or/consdiffmgr.c:329. Stack trace: (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(log_backtrace+0x42) [0x5646781eafe2] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(tor_bug_occurred_+0xb7) [0x564678203ee7] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(consdiffmgr_rescan+0xc22) [0x5646781994c2] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(+0x4e8cd) [0x5646780cd8cd] (on Tor 0.3.1.9 )
  Bug: /usr/lib/x86_64-linux-
 gnu/libevent-2.0.so.5(event_base_loop+0x7fc) [0x7f55dacf83dc] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(do_main_loop+0x2a4) [0x5646780ce674] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(tor_main+0x1c35) [0x5646780d1ff5] (on Tor 0.3.1.9 )
  Bug: /usr/bin/tor(main+0x19) [0x5646780c9d79] (on Tor 0.3.1.9 )
  Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)
 [0x7f55d967db45] (on Tor 0.3.1.9 )
  Bug: /usr/bin/tor(+0x4adc9) [0x5646780c9dc9] (on Tor 0.3.1.9 )
  tor_bug_occurred_(): Bug: ../src/or/consdiffmgr.c:329: cdm_diff_ht_purge:
 Non-fatal assertion !((*diff)->entry == NULL) failed. (on Tor 0.3.1.9 )
  Bug: Non-fatal assertion !((*diff)->entry == NULL) failed in
 cdm_diff_ht_purge at ../src/or/consdiffmgr.c:329. Stack trace: (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(log_backtrace+0x42) [0x5646781eafe2] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(tor_bug_occurred_+0xb7) [0x564678203ee7] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(consdiffmgr_rescan+0xc22) [0x5646781994c2] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(+0x4e8cd) [0x5646780cd8cd] (on Tor 0.3.1.9 )
  Bug: /usr/lib/x86_64-linux-
 gnu/libevent-2.0.so.5(event_base_loop+0x7fc) [0x7f55dacf83dc] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(do_main_loop+0x2a4) [0x5646780ce674] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(tor_main+0x1c35) [0x5646780d1ff5] (on Tor 0.3.1.9 )
  Bug: /usr/bin/tor(main+0x19) [0x5646780c9d79] (on Tor 0.3.1.9 )
  Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)
 [0x7f55d967db45] (on Tor 0.3.1.9 )
  Bug: /usr/bin/tor(+0x4adc9) [0x5646780c9dc9] (on Tor 0.3.1.9 )
  tor_bug_occurred_(): Bug: ../src/or/consdiffmgr.c:329: cdm_diff_ht_purge:
 Non-fatal assertion !((*diff)->entry == NULL) failed. (on Tor 0.3.1.9 )
  Bug: Non-fatal assertion !((*diff)->entry == NULL) failed in
 cdm_diff_ht_purge at ../src/or/consdiffmgr.c:329. Stack trace: (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(log_backtrace+0x42) [0x5646781eafe2] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(tor_bug_occurred_+0xb7) [0x564678203ee7] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(consdiffmgr_rescan+0xc22) [0x5646781994c2] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(+0x4e8cd) [0x5646780cd8cd] (on Tor 0.3.1.9 )
  Bug: /usr/lib/x86_64-linux-
 gnu/libevent-2.0.so.5(event_base_loop+0x7fc) [0x7f55dacf83dc] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(do_main_loop+0x2a4) [0x5646780ce674] (on Tor
 0.3.1.9 )
  Bug: /usr/bin/tor(tor_main+0x1c35) [0x5646780d1ff5] (on Tor 0.3.1.9 )
  Bug: /usr/bin/tor(main+0x19) [0x5646780c9d79] (on Tor 0.3.1.9 )
  Bug: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)
 [0x7f55d967db45] (on Tor 0.3.1.9 )
  Bug: /usr/bin/tor(+0x4adc9) [0x5646780c9dc9] (on Tor 0.3.1.9 )
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24555 [Core Tor/Tor]: Bug: tor_gmtime_r overflow - gmtime(9223372036854775807) failed with error No error

[Tor Bug Tracker & Wiki]

#24555: Bug: tor_gmtime_r overflow - gmtime(9223372036854775807) failed with 
error
No error
-+-
 Reporter:  s7r  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.3.x-final
Component:  Core |Version:  Tor: unspecified
  Tor/Tor|   Keywords:  integer-overflow time-overflow tor-
 Severity:  Normal   |  relay 2038-problem
Actual Points:   |  Parent ID:  #18480
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 It's here. FreeBSD 10.3 running `0.3.3.0-alpha-dev (git-
 e8a6a6635b26c327)`.

 Setting parent ticket the one with all time functions with undefined
 behavior.

 Relay:
 {{{
 Dec 06 04:10:15.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev e8a6a6635b26c327)
 Dec 06 04:10:15.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev e8a6a6635b26c327)
 Dec 06 09:07:16.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev e8a6a6635b26c327)
 Dec 06 11:04:16.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev e8a6a6635b26c327)
 Dec 06 11:04:16.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev e8a6a6635b26c327)
 Dec 06 12:15:25.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev e8a6a6635b26c327)
 Dec 06 15:24:16.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev e8a6a6635b26c327)
 Dec 06 17:15:17.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev e8a6a6635b26c327)
 Dec 06 20:16:16.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev e8a6a6635b26c327
 Dec 07 12:09:37.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev e8a6a6635b26c327)
 Dec 07 13:03:18.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev e8a6a6635b26c327)
 }}}

 Bridge:
 {{{
 Dec 06 03:34:15.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev 1969d573637ee6f9)
 Dec 06 03:34:15.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev 1969d573637ee6f9)
 Dec 06 09:54:15.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev 1969d573637ee6f9)
 Dec 06 09:54:15.000 [warn] correct_tm: Bug: gmtime(9223372036854775807)
 failed with error No error: 0: Rounding down to 2037 (on Tor 0.3.3.0
 -alpha-dev 1969d573637ee6f9)
 }}}

 Time on the system is accurate and synced with ntp permanently.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24534 [Metrics/ExoneraTor]: Investigate Exonerator down times (was: Exonerator is down)

[Tor Bug Tracker & Wiki]

#24534: Investigate Exonerator down times
+--
 Reporter:  atagar  |  Owner:  metrics-team
 Type:  defect  | Status:  new
 Priority:  High|  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Major   | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Old description:

> When attempting to visit https://exonerator.torproject.org/ the
> connection hangs for several minutes, then fails for me with 502 proxy
> error ("Reason: Error reading from remote server"). sysrqb says he's
> getting the same thing.

New description:

 Investigate the reasons for ExoneraTor service being unable to provide
 service.

 One incident reported by atagar:
  When attempting to visit https://exonerator.torproject.org/ the
 connection hangs  for several minutes, then fails for me with 502 proxy
 error ("Reason: Error reading from remote server"). sysrqb says he's
 getting the same thing.

--

Comment (by iwakeh):

 Changed the summary and description to describe what this ticket is about.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #14952 [Applications/Tor Browser]: Audit HTTP/2 and SPDY if needed

[Tor Bug Tracker & Wiki]

#14952: Audit HTTP/2 and SPDY if needed
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-linkability, tbb-usability-  |  Actual Points:
  website, tbb-performance, ff59-esr |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * keywords:  tbb-linkability, tbb-usability-website, tbb-performance, ff-
 59esr => tbb-linkability, tbb-usability-website, tbb-performance,
 ff59-esr


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

Re: [tor-bugs] #14952 [Applications/Tor Browser]: Audit HTTP/2 and SPDY if needed

[Tor Bug Tracker & Wiki]

#14952: Audit HTTP/2 and SPDY if needed
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-linkability, tbb-usability-  |  Actual Points:
  website, tbb-performance, ff-59esr |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by arthuredelstein):

 * keywords:  tbb-linkability, tbb-usability-website, tbb-performance =>
 tbb-linkability, tbb-usability-website, tbb-performance, ff-59esr


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #14952 [Applications/Tor Browser]: Audit HTTP/2 and SPDY if needed

[Tor Bug Tracker & Wiki]

#14952: Audit HTTP/2 and SPDY if needed
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-linkability, tbb-usability-  |  Actual Points:
  website, tbb-performance   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by arthuredelstein):

 Here's a bug that was resolved for Firefox 55:
 https://bugzilla.mozilla.org/show_bug.cgi?id=1334693
 So it looks like a lot of work has been done already.

 There's also a bug suggesting some unit tests should be written:
 https://bugzilla.mozilla.org/show_bug.cgi?id=1337868

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23709 [Core Tor/Tor]: channel: `outgoing_queue` and `incoming_queue` are always empty

[Tor Bug Tracker & Wiki]

#23709: channel: `outgoing_queue` and `incoming_queue` are always empty
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  defect| Status:  needs_review
 Priority:  High  |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-sched |  Actual Points:
Parent ID:  #23993| Points:
 Reviewer:  nickm |Sponsor:  SponsorV
--+
Changes (by dgoulet):

 * status:  needs_information => needs_review


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

Re: [tor-bugs] #24534 [Metrics/ExoneraTor]: Exonerator is down

[Tor Bug Tracker & Wiki]

#24534: Exonerator is down
+--
 Reporter:  atagar  |  Owner:  metrics-team
 Type:  defect  | Status:  new
 Priority:  High|  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Major   | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by iwakeh):

 Further investigation lead to a thread dump with 200 waiting backend
 queries, but no such query thread.
 Logs didn't reveal anything suspicious except very few errors due to weird
 data input (reproducible by entering an ipv6 address with additional
 percent sign number combination).
 In addition, ExoneraTor often is queried more than 3 times per second,
 which is surprising, but not at all a performance problem.
 Thus, a temporary measure can be to simply catch all possible errors and
 then proceed when we catch something.
 Please find a minimal catch-all patch
 [https://gitweb.torproject.org/user/iwakeh/exonerator.git/commit/?h=task-24534
 -debug-
 patch=a8bb4babdb0a55e5f78b9d226c59145c16f06bff=3=1=0
 here] (all changes other than adding try-catch were made to avoid
 checkstyle complaints).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24552 [Core Tor/Tor]: Coverity CID 1425934: FORWARD_NULL in circuit_stream_is_being_handled()

[Tor Bug Tracker & Wiki]

#24552: Coverity CID 1425934: FORWARD_NULL in circuit_stream_is_being_handled()
--+
 Reporter:  ahf   |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by ahf):

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


Comment:

 This was fixed in `c2c0f83c23986344c4f3fab033ea1126452f2897` (#24551)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24554 [Core Tor/Tor]: sched: Have per-scheduler type data in a channel_t

[Tor Bug Tracker & Wiki]

#24554: sched: Have per-scheduler type data in a channel_t
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-sched |  Actual Points:
Parent ID:  #23993| Points:
 Reviewer:  pastly|Sponsor:
--+
Changes (by pastly):

 * reviewer:   => pastly


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24545 [Applications/Orbot]: Orbot fails to compile

[Tor Bug Tracker & Wiki]

#24545: Orbot fails to compile
+-
 Reporter:  igt0|  Owner:  igt0
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Applications/Orbot  |Version:
 Severity:  Normal  | Resolution:  wontfix
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+-
Changes (by igt0):

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


Comment:

 It is already fixed in the github repo.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24447 [Applications/GetTor]: GetTor automatic update seems to be have been broken again

[Tor Bug Tracker & Wiki]

#24447: GetTor automatic update seems to be have been broken again
-+
 Reporter:  cypherpunks  |  Owner:  ilv
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:
Component:  Applications/GetTor  |Version:
 Severity:  Critical | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by ilv):

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


Comment:

 Service is working again with the latest 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] #24549 [Applications/GetTor]: GetTor not replying

[Tor Bug Tracker & Wiki]

#24549: GetTor not replying
-+---
 Reporter:  steph|  Owner:  ilv
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/GetTor  |Version:
 Severity:  Normal   | Resolution:  duplicate
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by ilv):

 fyi: email and twitter are working 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] #24554 [Core Tor/Tor]: sched: Have per-scheduler type data in a channel_t

[Tor Bug Tracker & Wiki]

#24554: sched: Have per-scheduler type data in a channel_t
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-sched |  Actual Points:
Parent ID:  #23993| Points:
 Reviewer:|Sponsor:
--+
Changes (by dgoulet):

 * parent:   => #23993


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24554 [Core Tor/Tor]: sched: Have per-scheduler type data in a channel_t

[Tor Bug Tracker & Wiki]

#24554: sched: Have per-scheduler type data in a channel_t
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-sched |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by dgoulet):

 * status:  assigned => needs_review


Comment:

 See branch: `ticket24554_033_01`
 OnionGit: https://oniongit.eu/dgoulet/tor/merge_requests/12

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24554 [Core Tor/Tor]: sched: Have per-scheduler type data in a channel_t

[Tor Bug Tracker & Wiki]

#24554: sched: Have per-scheduler type data in a channel_t
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  enhancement   | Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  tor-sched
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Right now in `channel_t`, we have a `sched_heap_idx` and
 `scheduler_state`. Both are specific to the scheduler layer and are per-
 channel. The KIST scheduler also keeps data per-channel in a global state
 it keeps some other place.

 Because of #23744, which is a ticket about the scheduler state not
 applying to both Vanilla and KIST, we need a way to have a interface that
 allows any "scheduler data per-channel" to be specific to a type of
 scheduler (KIST or Vanilla).

 To achieve compartmentalization of whatever state the scheduler needs to
 keep, we need an interface that allows a specific scheduler to store data
 per-channel instead of in a global state which, in the case of KIST, would
 avoid two things:

 1. Huge amount of memory allocation at runtime that needs to be done by
 the main loop (this is currently a problem with KIST code).

 2. Avoid data duplication or/and synchronization problem between the
 channel subsystem and the scheduler subsystem.

 Finally, by doing so, we can build an opaque interface for the specific
 scheduler information data structure in order to make them *ONLY*
 accessible from the per-type scheduler code. This means a builtin
 protection to prevent any other layer in the tor to change or access the
 channel's scheduler state.

 Once we have this capability, we can go ahead and fix #23744 and move the
 `sched_heap_idx` and `scheduler_state` out of a channel object so ONLY the
 scheduler has access to those and be able to have different semantic for
 different scheduler type.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24553 [Applications/Tor Browser]: Re-enable Alternate Services

[Tor Bug Tracker & Wiki]

#24553: Re-enable Alternate Services
--+--
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  ff59-esr
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Mozilla patched Alternate Services (Alt-Svc) to have first-party
 isolation:
 https://bugzilla.mozilla.org/1334690, effective Firefox 54. We disabled
 Alt-Svc , but in TBB/ESR59 we can potentially re-enable it.

 We also need to examine if there are other related headers or mechanisms
 that could act as supercookie vectors. (Patrick McManus mentioned alt-used
 as a possibility.) If there are, then those need to be isolated as 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] #14952 [Applications/Tor Browser]: Audit HTTP/2 and SPDY if needed

[Tor Bug Tracker & Wiki]

#14952: Audit HTTP/2 and SPDY if needed
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-linkability, tbb-usability-  |  Actual Points:
  website, tbb-performance   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by arthuredelstein):

 Mozilla decided not to backport their patches for first-party isolation of
 AltSvc,
 https://bugzilla.mozilla.org/1334690#c16,
 so we would need to do so for TBB/ESR52,
 https://bugzilla.mozilla.org/show_bug.cgi?id=1334690#c16

 We also need to examine if there are other HTTP/2 headers or mechanisms
 that could act as supercookie vectors. (Patrick McManus mentioned alt-used
 as a possibility.) If there are, then those need to be isolated as 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] #24540 [HTTPS Everywhere/EFF-HTTPS Everywhere]: Weird site issues with Tor & HTTPSEverywhere

[Tor Bug Tracker & Wiki]

#24540: Weird site issues with Tor & HTTPSEverywhere
-+-
 Reporter:  mroystonward |  Owner:  jsha
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  HTTPS Everywhere/EFF-HTTPS   |Version:
  Everywhere |
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 I can't reproduce the behaviour you are describing when HTTPS Everywhere
 is disabled.

 I still think this is a server config issue where the correct certificate
 is not consistently served.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24367 [Core Tor/Tor]: Changing pluggable transports (during start-up) in Tor Browser is broken

[Tor Bug Tracker & Wiki]

#24367: Changing pluggable transports (during start-up) in Tor Browser is broken
-+-
 Reporter:  gk   |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  regression, tor-bridge-client,   |  Actual Points:
  s8-errors, tbb-wants   |
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-

Comment (by teor):

 Replying to [comment:19 gk]:
 > teor: Are you still working on this bug? It would be really neat if we
 could get this tor issue fixed for 0.3.2.

 I am working with arma and nickm to fix #24392 and #24486. We thought we
 had a solution, but it needs revising.
 I'll probably end up doing the revision. We will probably get this done in
 0.3.2.

 It seems like there might be other bugs that contribute to this issue. I
 don't know whether they are in Tor or Tor Launcher. I don't understand all
 the details.

 I don't intend to work on this issue beyond fixing #24392 and #24486.
 I might help review or write short patches if someone can identify a
 specific bug in Tor.
 A reproducible series of steps that only involve tor (not Tor Launcher)
 would be really helpful here.
 (This is volunteer work for me, and I don't feel I know enough about Tor /
 Tor Launcher interactions to be helpful.)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23459 [Core Tor/Tor]: prop224: Specialize interface of hs_circuitmap_get_rend_circ_client_side()

[Tor Bug Tracker & Wiki]

#23459: prop224: Specialize interface of 
hs_circuitmap_get_rend_circ_client_side()
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, prop224-extra,  |  Actual Points:
  refactoring, easy, 032-unreached   |
Parent ID:   | Points:  0.4
 Reviewer:   |Sponsor:
-+-
Changes (by ffmancera):

 * status:  new => needs_review


Comment:

 Done! Check my github
 [https://github.com/ffmancera/tor/tree/github/bug23459 branch bug23459]. I
 hope everything is fine!

 PD: I am not sure if the commit message is good enough.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24475 [Applications/Tor Browser]: Add support for Windows 64 to update-responses

[Tor Bug Tracker & Wiki]

#24475: Add support for Windows 64 to update-responses
+--
 Reporter:  boklm   |  Owner:  tbb-team
 Type:  task| Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  tbb-rbm, TorBrowserTeam201712R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:  Sponsor4
+--
Changes (by gk):

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


Comment:

 Looks good. Applied to `master` as commit
 5a274fb97d317860e59592ec37a6ce9f3a007fd9.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24367 [Core Tor/Tor]: Changing pluggable transports (during start-up) in Tor Browser is broken

[Tor Bug Tracker & Wiki]

#24367: Changing pluggable transports (during start-up) in Tor Browser is broken
-+-
 Reporter:  gk   |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  regression, tor-bridge-client,   |  Actual Points:
  s8-errors, tbb-wants   |
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by gk):

 * status:  assigned => needs_information


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

Re: [tor-bugs] #24367 [Core Tor/Tor]: Changing pluggable transports (during start-up) in Tor Browser is broken

[Tor Bug Tracker & Wiki]

#24367: Changing pluggable transports (during start-up) in Tor Browser is broken
-+-
 Reporter:  gk   |  Owner:  (none)
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  regression, tor-bridge-client,   |  Actual Points:
  s8-errors, tbb-wants   |
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by gk):

 * keywords:  regression, tor-bridge-client, s8-errors => regression, tor-
 bridge-client, s8-errors, tbb-wants


Comment:

 teor: Are you still working on this bug? It would be really neat if we
 could get this tor issue fixed for 0.3.2.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24552 [Core Tor/Tor]: Coverity CID 1425934: FORWARD_NULL in circuit_stream_is_being_handled()

[Tor Bug Tracker & Wiki]

#24552: Coverity CID 1425934: FORWARD_NULL in circuit_stream_is_being_handled()
--+
 Reporter:  ahf   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by nickm):

 This could be a duplicate of #24551

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24552 [Core Tor/Tor]: Coverity CID 1425934: FORWARD_NULL in circuit_stream_is_being_handled()

[Tor Bug Tracker & Wiki]

#24552: Coverity CID 1425934: FORWARD_NULL in circuit_stream_is_being_handled()
--+
 Reporter:  ahf   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Coverity detected the following error:

 {{{
 src/or/circuituse.c: 1025 in circuit_stream_is_being_handled():
 Null pointer dereferences  (FORWARD_NULL)
 Comparing "conn" to null implies that "conn" might be null.
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24337 [Core Tor/Tor]: Every _free() function should be a macro that sets the corresponding pointer to NULL.

[Tor Bug Tracker & Wiki]

#24337: Every _free() function should be a macro that sets the corresponding
pointer to NULL.
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:
  |  needs_review
 Priority:  Medium|  Milestone:  Tor:
  |  0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  review-group-26, review-group-27  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
  |  Sponsor8-can
--+

Comment (by nickm):

 (and FREE_AND_NULL now does what FREE_AND_NULL_UNMATCHED) used to do.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24337 [Core Tor/Tor]: Every _free() function should be a macro that sets the corresponding pointer to NULL.

[Tor Bug Tracker & Wiki]

#24337: Every _free() function should be a macro that sets the corresponding
pointer to NULL.
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:
  |  needs_review
 Priority:  Medium|  Milestone:  Tor:
  |  0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  review-group-26, review-group-27  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
  |  Sponsor8-can
--+

Comment (by nickm):

 I've updated the branch so that there is only FREE_AND_NULL(), and
 everything uses it.  Back to you, dgoulet. :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24203 [Core Tor/Tor]: Snowflake can't be configured to run with system tor: ENV-ERROR no TOR_PT_STATE_LOCATION environment variable (was: Snowflake can't be configured to run with syst

[Tor Bug Tracker & Wiki]

#24203: Snowflake can't be configured to run with system tor: ENV-ERROR no
TOR_PT_STATE_LOCATION environment variable
--+--
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Major | Resolution:
 Keywords:  snowflake |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

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

Re: [tor-bugs] #24217 [Metrics/Statistics]: Specify data format and aggregation process of new IPv6 relay statistics

[Tor Bug Tracker & Wiki]

#24217: Specify data format and aggregation process of new IPv6 relay statistics
+--
 Reporter:  karsten |  Owner:  metrics-team
 Type:  enhancement | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by iwakeh):

 See #24218 ([https://trac.torproject.org/projects/tor/raw-
 attachment/ticket/24218/data-spec-template.pdf attachment]) for a first
 content structure.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24203 [Core Tor/Tor]: Snowflake can't be configured to run with system tor because of AppArmor

[Tor Bug Tracker & Wiki]

#24203: Snowflake can't be configured to run with system tor because of AppArmor
--+--
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Major | Resolution:
 Keywords:  snowflake |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 This seems to be the error when trying to launch it:

 {{{
 ENV-ERROR no TOR_PT_STATE_LOCATION environment variable
 }}}

 (Note: I had already added `/usr/bin/snowflake ix,` in the last line of
 `/etc/apparmor.d/abstractions/tor`)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24531 [Core Tor/Tor]: sched: Add function to change scheduler state and always use it

[Tor Bug Tracker & Wiki]

#24531: sched: Add function to change scheduler state and always use it
-+
 Reporter:  pastly   |  Owner:  (none)
 Type:  defect   | Status:  needs_revision
 Priority:  Medium   |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-sched, easy  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by pastly):

 * status:  needs_review => needs_revision


Comment:

 The patch as provided needs revision.

 - `==` are not assignments.
 - function definitions need types for their arguments (unlike pseudocode)
 -  `scheduler_set_channel` is not a good name for the function
 - "Function to log and change all the old and new states" does not
 describe what the function does

 And this is just plain wrong

 {{{
 @@ -707,7 +712,7 @@ scheduler_bug_occurred(const channel_t *chan)
   " Num cells on cmux: %d. Connection outbuf len: %lu.",
   chan->global_identifier,
   channel_state_to_string(chan->state),
 - chan->scheduler_state, circuitmux_num_cells(chan->cmux),
 + scheduler_set_channel(chan,new_state),
 circuitmux_num_cells(chan->cmux),
   (unsigned long)outbuf_len);
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24531 [Core Tor/Tor]: sched: Add function to change scheduler state and always use it

[Tor Bug Tracker & Wiki]

#24531: sched: Add function to change scheduler state and always use it
-+
 Reporter:  pastly   |  Owner:  (none)
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-sched, easy  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by cypherpunks):

 * status:  new => needs_review


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

Re: [tor-bugs] #24379 [Applications/Tor Browser]: Make DuckDuckGo's onion service the default search engine for about:tor

[Tor Bug Tracker & Wiki]

#24379: Make DuckDuckGo's onion service  the default search engine for about:tor
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 Replying to [comment:2 gk]:
 > Please don't add random keywords to the ticket, thanks.
 Sorry for that, I thought it may have been more convenient in light of the
 other ff59 work at modifying about:tor and the onboarding.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #10573 [Applications/Tor Browser]: `nsILocalFile` should be replaced with `nsIFile` in our extensions

[Tor Bug Tracker & Wiki]

#10573: `nsILocalFile` should be replaced with `nsIFile` in our extensions
-+-
 Reporter:  cypherpunks  |  Owner:  tbb-team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Minor| Resolution:
 Keywords:  tbb-easy, TorBrowserTeam201712R  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by mcs):

 I think we are missing the Tor Launcher patch now. The two remaining
 attachments contain the same patch; the second has a corrected bug number
 in the commit 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] #8415 [Core Tor/Tor]: Use event_set_mem_functions

[Tor Bug Tracker & Wiki]

#8415: Use event_set_mem_functions
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor:
  |  unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  easy backend libevent malloc  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by aruna1234):

 okay. I'll take care.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24531 [Core Tor/Tor]: sched: Add function to change scheduler state and always use it

[Tor Bug Tracker & Wiki]

#24531: sched: Add function to change scheduler state and always use it
-+
 Reporter:  pastly   |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-sched, easy  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by aruna1234):

 * Attachment "0001-Bug-24531-Add-function-to-change-scheduler-state-
 and.patch" 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] #24497 [Webpages/Website]: Improve documentation for tor relay operators

[Tor Bug Tracker & Wiki]

#24497: Improve documentation for tor relay operators
--+
 Reporter:  arthuredelstein   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by alison):

 I've begun migrating content from our draft blog post to here:
 https://trac.torproject.org/projects/tor/wiki/OperatorsTips

 I started with nusenu's proposed outline and added some additional
 headings. Feel free to make formatting changes for ease of reading. Change
 the text if you want, too. Change anything!

 We should definitely move the linked content onto their own wiki pages
 (even things like blog posts and other content from tpo.org, because the
 website will be overhauled and we don't want to lose anything). I haven't
 done that yet in the content that I moved over.

 I plan to work on migrating more of this today.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24549 [Applications/GetTor]: GetTor not replying

[Tor Bug Tracker & Wiki]

#24549: GetTor not replying
-+---
 Reporter:  steph|  Owner:  ilv
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/GetTor  |Version:
 Severity:  Normal   | Resolution:  duplicate
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by steph):

 * status:  new => closed
 * resolution:   => 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] #24549 [Applications/GetTor]: GetTor not replying

[Tor Bug Tracker & Wiki]

#24549: GetTor not replying
-+-
 Reporter:  steph|  Owner:  ilv
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/GetTor  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by ilv):

 Yes, the service is down. Please see #24447.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #18859 [Core Tor/Tor]: A new SOCKS connection should use a pre-built circuit for its first stream

[Tor Bug Tracker & Wiki]

#18859: A new SOCKS connection should use a pre-built circuit for its first 
stream
-+-
 Reporter:  arthuredelstein  |  Owner:
 |  arthuredelstein
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-performance tor-client   |  Actual Points:
  performance  031-backpot   |
Parent ID:   | Points:
 Reviewer:  nickm|Sponsor:
-+-
Changes (by nickm):

 * keywords:
 tbb-performance tor-client needs-diagnosis needs-analysis performance
 review-group-27 031-backpot
 => tbb-performance tor-client  performance  031-backpot


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #18859 [Core Tor/Tor]: A new SOCKS connection should use a pre-built circuit for its first stream

[Tor Bug Tracker & Wiki]

#18859: A new SOCKS connection should use a pre-built circuit for its first 
stream
-+-
 Reporter:  arthuredelstein  |  Owner:
 |  arthuredelstein
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-performance tor-client needs-|  Actual Points:
  diagnosis needs-analysis performance review-   |
  group-27 031-backpot   |
Parent ID:   | Points:
 Reviewer:  nickm|Sponsor:
-+-
Changes (by nickm):

 * keywords:
 tbb-performance tor-client needs-diagnosis needs-analysis performance
 review-group-27
 =>
 tbb-performance tor-client needs-diagnosis needs-analysis performance
 review-group-27 031-backpot
 * status:  needs_review => merge_ready
 * milestone:  Tor: 0.3.2.x-final => Tor: 0.3.1.x-final


Comment:

 Thanks!  I've re-done the changes file a bit to make it pass lintChanges,
 to make it "major" per arma's request, and to try to explain the problem
 from a user's POV.  It's now a branch `arthuredelstein_18859+1_031` which
 I'm merging into 0.3.2 and later.  If it doesn't cause trouble, it  should
 get backported.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24551 [Core Tor/Tor]: Tor crashes with: ../src/or/connection_edge.c:3979:17: runtime error: member access within null pointer of type 'const struct entry_connection_t'

[Tor Bug Tracker & Wiki]

#24551: Tor crashes with: ../src/or/connection_edge.c:3979:17: runtime error:
member access within null pointer of type 'const struct entry_connection_t'
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

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


Comment:

 Reverted with c2c0f83c23986344c4f3fab033ea1126452f2897

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #18859 [Core Tor/Tor]: A new SOCKS connection should use a pre-built circuit for its first stream

[Tor Bug Tracker & Wiki]

#18859: A new SOCKS connection should use a pre-built circuit for its first 
stream
-+-
 Reporter:  arthuredelstein  |  Owner:
 |  arthuredelstein
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-performance tor-client needs-|  Actual Points:
  diagnosis needs-analysis performance review-   |
  group-27   |
Parent ID:   | Points:
 Reviewer:  nickm|Sponsor:
-+-

Comment (by nickm):

 (I had accidentally committed an earlier version of this along with my
 046acf208bc53a3fa7ea9 commit, and just reverted it with
 c2c0f83c23986344c4f3fab03)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24551 [Core Tor/Tor]: Tor crashes with: ../src/or/connection_edge.c:3979:17: runtime error: member access within null pointer of type 'const struct entry_connection_t'

[Tor Bug Tracker & Wiki]

#24551: Tor crashes with: ../src/or/connection_edge.c:3979:17: runtime error:
member access within null pointer of type 'const struct entry_connection_t'
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by nickm):

 Whoops.  Looks like I accidentally committed  some extra code as part of
 046acf208bc53a3fa7ea9967707835188eb6651c

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24475 [Applications/Tor Browser]: Add support for Windows 64 to update-responses

[Tor Bug Tracker & Wiki]

#24475: Add support for Windows 64 to update-responses
+--
 Reporter:  boklm   |  Owner:  tbb-team
 Type:  task| Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201712R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:  Sponsor4
+--
Changes (by boklm):

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


Comment:

 I rebased the patch on master in branch `bug_24475_v2`:
 https://gitweb.torproject.org/user/boklm/tor-browser-
 build.git/commit/?h=bug_24475_v2=5a274fb97d317860e59592ec37a6ce9f3a007fd9

 I tried it using a build of `tbb-7.5a9-build3`, and the generated
 downloads.json, .htaccess, and .xml files look good.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24531 [Core Tor/Tor]: sched: Add function to change scheduler state and always use it

[Tor Bug Tracker & Wiki]

#24531: sched: Add function to change scheduler state and always use it
-+
 Reporter:  pastly   |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-sched, easy  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by pastly):

 Write the function. Then replace every instance of

 {{{
 chan->scheduler_state = SCHED_CHAN_IDLE;
 }}}

 with

 {{{
 scheduler_set_channel_state(chan, SCHED_CHAN_IDLE);
 }}}

 Of course, do this for all states and not just `SCHED_CHAN_IDLE`.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24309 [Applications/Tor Browser]: Activity 4.1: Improve how circuits are displayed to the user

[Tor Bug Tracker & Wiki]

#24309: Activity 4.1: Improve how circuits are displayed to the user
--+--
 Reporter:  isabela   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:  antonela  |Sponsor:
--+--
Changes (by antonela):

 * Attachment "24309-3.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] #8415 [Core Tor/Tor]: Use event_set_mem_functions

[Tor Bug Tracker & Wiki]

#8415: Use event_set_mem_functions
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor:
  |  unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  easy backend libevent malloc  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by teor):

 Hi aruna1234,

 Please focus on one or two tickets, finish those tickets, and then try a
 few more tickets.
 We can't help you with a lot of tickets at the same time. It's too
 confusing for everyone.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23966 [Core Tor/Tor]: Refactor node_has_curve25519_onion_key() to use node_get_curve25519_onion_key()

[Tor Bug Tracker & Wiki]

#23966: Refactor node_has_curve25519_onion_key() to use
node_get_curve25519_onion_key()
+
 Reporter:  teor|  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  easy, refactor  |  Actual Points:
Parent ID:  | Points:  0.2
 Reviewer:  |Sponsor:
+

Comment (by teor):

 Both functions already exist.
 This ticket is about rewriting node_has… so that it uses node_get… and a
 comparison,

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23966 [Core Tor/Tor]: Refactor node_has_curve25519_onion_key() to use node_get_curve25519_onion_key()

[Tor Bug Tracker & Wiki]

#23966: Refactor node_has_curve25519_onion_key() to use
node_get_curve25519_onion_key()
+
 Reporter:  teor|  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  easy, refactor  |  Actual Points:
Parent ID:  | Points:  0.2
 Reviewer:  |Sponsor:
+

Comment (by aruna1234):

 Replying to [ticket:23966 teor]:
 > In #23577, we will create node_get_curve25519_onion_key().
 > We should use it to implement node_has_curve25519_onion_key(), so they
 give consistent results.

 Or as this says, we should create node_get_curve25519_onion_key() and then
 call node_has_curve25519_onion_key() from this function so they give
 consistent results?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24531 [Core Tor/Tor]: sched: Add function to change scheduler state and always use it

[Tor Bug Tracker & Wiki]

#24531: sched: Add function to change scheduler state and always use it
-+
 Reporter:  pastly   |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-sched, easy  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by aruna1234):

 so, first we need to write that function, and then replace all the
 assignment statements in scheduler.c with the function call?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24551 [Core Tor/Tor]: Tor crashes with: ../src/or/connection_edge.c:3979:17: runtime error: member access within null pointer of type 'const struct entry_connection_t'

[Tor Bug Tracker & Wiki]

#24551: Tor crashes with: ../src/or/connection_edge.c:3979:17: runtime error:
member access within null pointer of type 'const struct entry_connection_t'
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 I just recompiled tor picking up the latest changes on `master` and it now
 crashes on start-up in my Tor Browser:
 {{{
 ../src/or/connection_edge.c:3979:17: runtime error: member access within
 null pointer of type 'const struct entry_connection_t'
 ASAN:DEADLYSIGNAL
 =
 ==8351==ERROR: AddressSanitizer: SEGV on unknown address 0x0100
 (pc 0x55f1524fb45d bp 0x7ffcbd3c61d0 sp 0x7ffcbd3c6170 T0)
 ==8351==The signal is caused by a READ memory access.
 ==8351==Hint: address points to the zero page.
 #0 0x55f1524fb45c in connection_edge_compatible_with_circuit
 ../src/or/connection_edge.c:3980
 #1 0x55f15245f4ca in circuit_stream_is_being_handled
 ../src/or/circuituse.c:1042
 #2 0x55f15245fb43 in circuit_remove_handled_ports
 ../src/or/circuituse.c:1002
 #3 0x55f15240ee35 in circuit_get_unhandled_ports
 ../src/or/circuitbuild.c:1760
 #4 0x55f15240ee35 in circuit_all_predicted_ports_handled
 ../src/or/circuitbuild.c:1776
 #5 0x55f15246adcf in needs_exit_circuits ../src/or/circuituse.c:1109
 #6 0x55f15246adcf in circuit_predict_and_launch_new
 ../src/or/circuituse.c:1231
 #7 0x55f15246adcf in circuit_build_needed_circs
 ../src/or/circuituse.c:1311
 #8 0x55f152247e47 in run_scheduled_events ../src/or/main.c:1516
 #9 0x55f152247e47 in second_elapsed_callback ../src/or/main.c:2283
 #10 0x7fa42dab09b9  (/usr/lib/x86_64-linux-
 gnu/libevent-2.1.so.6+0x229b9)
 #11 0x7fa42dab1536 in event_base_loop (/usr/lib/x86_64-linux-
 gnu/libevent-2.1.so.6+0x23536)
 #12 0x55f152249197 in run_main_loop_once ../src/or/main.c:2714
 #13 0x55f152249197 in run_main_loop_until_done ../src/or/main.c:2771
 #14 0x55f152249197 in do_main_loop ../src/or/main.c:2678
 #15 0x55f15224d6c4 in tor_run_main ../src/or/main.c:3920
 #16 0x55f15223b295 in tor_main ../src/or/tor_api.c:84
 #17 0x55f15223849b in main ../src/or/tor_main.c:22
 #18 0x7fa42b7f5560 in __libc_start_main (/lib/x86_64-linux-
 gnu/libc.so.6+0x20560)
 #19 0x55f15223af49 in _start
 (/home/thomas/Arbeit/Tor/tor/build/src/or/tor+0x69bf49)

 AddressSanitizer can not provide additional info.
 SUMMARY: AddressSanitizer: SEGV ../src/or/connection_edge.c:3980 in
 connection_edge_compatible_with_circuit
 ==8351==ABORTING
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #3317 [Core Tor/Tor]: Tor should lock its HiddenServiceDirs

[Tor Bug Tracker & Wiki]

#3317: Tor should lock its HiddenServiceDirs
--+--
 Reporter:  rransom   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-hs easy   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by aruna1234):

 what is it that the bug demands?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #8415 [Core Tor/Tor]: Use event_set_mem_functions

[Tor Bug Tracker & Wiki]

#8415: Use event_set_mem_functions
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor:
  |  unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  easy backend libevent malloc  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by aruna1234):

 and how can I do 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] #23271 [Core Tor/Tor]: control_auth_cookie isn't deleted when tor stops

[Tor Bug Tracker & Wiki]

#23271: control_auth_cookie isn't deleted when tor stops
--+
 Reporter:  yurivict271   |  Owner:  (none)
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.0.10
 Severity:  Normal| Resolution:
 Keywords:  easy tor-control  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by ffmancera):

 * status:  needs_revision => needs_review


Comment:

 All done! Check my github
 [https://github.com/ffmancera/tor/tree/github/bug23271 branch bug23271]. I
 hope everything is fine!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #10573 [Applications/Tor Browser]: `nsILocalFile` should be replaced with `nsIFile` in our extensions

[Tor Bug Tracker & Wiki]

#10573: `nsILocalFile` should be replaced with `nsIFile` in our extensions
-+-
 Reporter:  cypherpunks  |  Owner:  tbb-team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Minor| Resolution:
 Keywords:  tbb-easy, TorBrowserTeam201712R  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by aruna1234):

 thanks for the help!

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

Re: [tor-bugs] #24260 [Metrics/Website]: Add metrics timeline events underneath graphs

[Tor Bug Tracker & Wiki]

#24260: Add metrics timeline events underneath graphs
--+--
 Reporter:  karsten   |  Owner:  metrics-team
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Metrics/Website   |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team metrics-timeline  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by karsten):

 [https://gitweb.torproject.org/karsten/metrics-
 web.git/commit/?h=task-24260=53978c70410e7059a329809bdb6b42c4a0223c79
 Commit 53978c7 in my task-24260 branch] still needs review. It's currently
 deployed but not merged to master yet. If it looks good (enough), I'll
 rebase and merge to master. 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] #22990 [Metrics/Library]: Add a heartbeat log message indicating progress and estimated time left

[Tor Bug Tracker & Wiki]

#22990: Add a heartbeat log message indicating progress and estimated time left
-+--
 Reporter:  karsten  |  Owner:  iwakeh
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2017 |  Actual Points:
Parent ID:   | Points:
 Reviewer:  iwakeh   |Sponsor:
-+--
Changes (by karsten):

 * status:  needs_revision => needs_review


Comment:

 Please review [https://gitweb.torproject.org/user/karsten/metrics-
 lib.git/commit/?h=task-22990 the new commit in my task-22990 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] #22990 [Metrics/Library]: Add a heartbeat log message indicating progress and estimated time left

[Tor Bug Tracker & Wiki]

#22990: Add a heartbeat log message indicating progress and estimated time left
-+
 Reporter:  karsten  |  Owner:  iwakeh
 Type:  enhancement  | Status:  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-2017 |  Actual Points:
Parent ID:   | Points:
 Reviewer:  iwakeh   |Sponsor:
-+

Comment (by karsten):

 I'm revising this patch now.

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

Re: [tor-bugs] #24218 [Metrics/Statistics]: Implement new metrics-web module for IPv6 relay statistics

[Tor Bug Tracker & Wiki]

#24218: Implement new metrics-web module for IPv6 relay statistics
+--
 Reporter:  karsten |  Owner:  metrics-team
 Type:  enhancement | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  iwakeh  |Sponsor:
+--

Comment (by karsten):

 Please also review [https://gitweb.torproject.org/karsten/metrics-
 web.git/commit/?h=tasks-24218-23761=57c58b5f1b099ac61e09169661a19b8c4a82984f
 commit 57c58b5 in my tasks-24218-23761 branch] with the CSV file
 specification.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24379 [Applications/Tor Browser]: Make DuckDuckGo's onion service the default search engine for about:tor

[Tor Bug Tracker & Wiki]

#24379: Make DuckDuckGo's onion service  the default search engine for about:tor
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * keywords:  ff59-esr =>


Comment:

 Please don't add random keywords to the ticket, 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] #10573 [Applications/Tor Browser]: `nsILocalFile` should be replaced with `nsIFile` in our extensions

[Tor Bug Tracker & Wiki]

#10573: `nsILocalFile` should be replaced with `nsIFile` in our extensions
-+-
 Reporter:  cypherpunks  |  Owner:  tbb-team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Minor| Resolution:
 Keywords:  tbb-easy, TorBrowserTeam201712R  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 Replying to [comment:15 mcs]:
 > aruna1234, can you please delete the attachments that are not needed so
 that only the ones that should be reviewed remain on this ticket? Thanks!

 I deleted them.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #10573 [Applications/Tor Browser]: `nsILocalFile` should be replaced with `nsIFile` in our extensions (was: `nsILocalFile` should be replaced with `nsIFile`)

[Tor Bug Tracker & Wiki]

#10573: `nsILocalFile` should be replaced with `nsIFile` in our extensions
-+-
 Reporter:  cypherpunks  |  Owner:  tbb-team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Minor| Resolution:
 Keywords:  tbb-easy, TorBrowserTeam201712R  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by aruna1234):

 * Attachment "0001-Bug-10537-Replace-deprecated-nsILocalFile-with-
 nsIFi.patch" removed.


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