Re: [tor-bugs] #29607 [Core Tor/Tor]: Denial of service on v2 and v3 onion service

[Tor Bug Tracker & Wiki]

#29607: Denial of service on v2 and v3 onion service
--+--
 Reporter:  pidgin|  Owner:  pidgin
 Type:  defect| Status:  accepted
 Priority:  Immediate |  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by pidgin):

 the v3 onion tor process was at 100% cpu at another machine

 last notice log messages:


 scrubbed:39:57.000 [notice] Extremely large value for circuit build
 timeout: 128s. Assuming clock jump. Purpose 14 (Measuring circuit timeout)
 scrubbed:39:57.000 [notice] Extremely large value for circuit build
 timeout: 128s. Assuming clock jump. Purpose 14 (Measuring circuit timeout)
 scrubbed:39:57.000 [notice] Extremely large value for circuit build
 timeout: 128s. Assuming clock jump. Purpose 14 (Measuring circuit timeout)
 scrubbed:39:57.000 [notice] Extremely large value for circuit build
 timeout: 128s. Assuming clock jump. Purpose 14 (Measuring circuit timeout)
 scrubbed:39:57.000 [notice] Extremely large value for circuit build
 timeout: 128s. Assuming clock jump. Purpose 14 (Measuring circuit timeout)
 scrubbed:39:57.000 [notice] Extremely large value for circuit build
 timeout: 128s. Assuming clock jump. Purpose 14 (Measuring circuit timeout)
 scrubbed:57:39.000 [warn] Unknown introduction point auth key on circuit
 4162469458 for service [scrubbed]
 scrubbed:57:39.000 [warn] circuit_mark_for_close_(): Bug: Duplicate call
 to circuit_mark_for_close at src/feature/hs/hs_service.c:3227 (first at
 src/feature/hs/hs_service.c:2446) (on Tor 0.4.0.1-alpha 81f1b89efc94723f)


 with the logmessage "57:39.000 [warn] circuit_mark_for_close_():"
 the cpu is now at 0% and the service is not accessible

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

Re: [tor-bugs] #29855 [Obfuscation/Obfsproxy]: TOR was blocked by my company.

[Tor Bug Tracker & Wiki]

#29855: TOR was blocked by my company.
---+-
 Reporter:  wanje  |  Owner:  asn
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Obfsproxy  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by wanje):

 Just allow us to browse any anonymous proxy that works and input that in
 connection through proxy settings of tor browser

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29855 [Obfuscation/Obfsproxy]: TOR was blocked by my company.

[Tor Bug Tracker & Wiki]

#29855: TOR was blocked by my company.
+---
 Reporter:  wanje   |  Owner:  asn
 Type:  defect  | Status:  new
 Priority:  Medium  |  Component:  Obfuscation/Obfsproxy
  Version:  |   Severity:  Normal
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---
 My company studied the tor connection methods and blocked them. You should
 allow tor to connect using an anonymous  web proxy server. All one would
 need is to insert it as a connection option and tor will establish a
 circuit through the anonymous proxy server

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

Re: [tor-bugs] #29770 [Internal Services/Service - lists]: mails relayed to gmail.com bounce back

[Tor Bug Tracker & Wiki]

#29770: mails relayed to gmail.com bounce back
---+--
 Reporter:  anarcat|  Owner:  tpa
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Internal Services/Service - lists  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by arma):

 I'm fine with seeing us experiment with other options. Mail in general is
 getting
 unreliable on the internet these days, but that doesn't mean we can't slow
 down our eventual demise.

 I think it might still be the case that mit.edu silently discards mailman
 confirmation mails. Now when I want to subscribe arma@mit to a Tor list, I
 log into the mailman web interface as admin and subscribe it directly.
 Otherwise I can never confirm my intent to subscribe, because I never get
 the mail inviting me to confirm.

 Once a year or so, gmail decides to start bouncing all of the mails that
 come from a given list, e.g. tor-rel...@lists.tpo. Our mailman, after a
 few messages to the list that all bounce from gmail, suspends the
 subscriptions of all gmail users on the list. Then we go through the
 horrible mailman web interface and un-suspend each of them.

 There has been something going on with state.gov over the last few years,
 where mails from them to @tpo don't arrive.

 And we should remember that @lists.tpo is a different system than @tpo.

 So: experimentation good, but we should be sure to keep an eye on what
 *other* things get broken when we do our various tests.

 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] #29754 [Core Tor/Tor]: Include new monitoring KeyValues in the bandwidth-file-spec

[Tor Bug Tracker & Wiki]

#29754: Include new monitoring KeyValues in the bandwidth-file-spec
-+-
 Reporter:  juga |  Owner:  juga
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, bandwidth-file-spec, tor-  |  Actual Points:
  bwauth |
Parent ID:  #28547   | Points:  1
 Reviewer:  teor, juga   |Sponsor:
-+-
Changes (by juga):

 * status:  needs_review => needs_revision


Comment:

 Thanks for all fixes and new keys!.
 I did some initial review. Let me know if you're going to work on this in
 the next hours, otherwise i'd continue with it.
 Let me also know if you're adding those 3 missing keys, otherwise i'll 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] #29854 [Core Tor/sbws]: Missing diagnostic keys in relay lines, but the data is in the header

[Tor Bug Tracker & Wiki]

#29854: Missing diagnostic keys in relay lines, but the data is in the header
-+-
 Reporter:  teor |  Owner:  juga
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  sbws:
 |  1.1.0
Component:  Core Tor/sbws|Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-bwauth, sbws-1.0-must-   |  Actual Points:
  moved-20181128, sbws-11x-final-|
  removed-20190312, sbws-110-proposed, changes-  |
  version-minor  |
Parent ID:  #28547   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by juga):

 Another key that i forgot to add in the spec example:
 "relay_in_recent_consensus_count"

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

Re: [tor-bugs] #29754 [Core Tor/Tor]: Include new monitoring KeyValues in the bandwidth-file-spec

[Tor Bug Tracker & Wiki]

#29754: Include new monitoring KeyValues in the bandwidth-file-spec
-+-
 Reporter:  juga |  Owner:  juga
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, bandwidth-file-spec, tor-  |  Actual Points:
  bwauth |
Parent ID:  #28547   | Points:  1
 Reviewer:  teor, juga   |Sponsor:
-+-

Comment (by juga):

 Replying to [comment:7 juga]:
 > Replying to [comment:6 teor]:
 > [...]
 > > I opened #29854 for missing KeyValues in the relay line,
 >
 > Commented there.

 To don't forget, these're the KeyValues to add to the lines example:
 "relay_recent_measurement_attempt_count",
 "relay_recent_priority_list_count",
 "relay_in_recent_consensus_count"

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

Re: [tor-bugs] #29853 [Core Tor/sbws]: sbws should show relays for diagnostics, even when MIN_REPORT has not been reached

[Tor Bug Tracker & Wiki]

#29853: sbws should show relays for diagnostics, even when MIN_REPORT has not 
been
reached
-+-
 Reporter:  teor |  Owner:  juga
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  sbws:
 |  1.1.0
Component:  Core Tor/sbws|Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-bwauth, sbws-1.0-must-   |  Actual Points:
  moved-20181128, sbws-11x-final-|
  removed-20190312, sbws-110-proposed, changes-  |
  version-minor  |
Parent ID:  #28563   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by juga):

 * status:  assigned => accepted


Comment:

 Sorry, i forgot about this case, will work on it soon.

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

Re: [tor-bugs] #29754 [Core Tor/Tor]: Include new monitoring KeyValues in the bandwidth-file-spec

[Tor Bug Tracker & Wiki]

#29754: Include new monitoring KeyValues in the bandwidth-file-spec
-+-
 Reporter:  juga |  Owner:  juga
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, bandwidth-file-spec, tor-  |  Actual Points:
  bwauth |
Parent ID:  #28547   | Points:  1
 Reviewer:  teor, juga   |Sponsor:
-+-

Comment (by juga):

 Replying to [comment:6 teor]:
 [...]
 > I opened #29854 for missing KeyValues in the relay line,

 Commented there.

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

Re: [tor-bugs] #29854 [Core Tor/sbws]: Missing diagnostic keys in relay lines, but the data is in the header

[Tor Bug Tracker & Wiki]

#29854: Missing diagnostic keys in relay lines, but the data is in the header
-+-
 Reporter:  teor |  Owner:  juga
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  sbws:
 |  1.1.0
Component:  Core Tor/sbws|Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-bwauth, sbws-1.0-must-   |  Actual Points:
  moved-20181128, sbws-11x-final-|
  removed-20190312, sbws-110-proposed, changes-  |
  version-minor  |
Parent ID:  #28547   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by juga):

 Replying to [ticket:29854 teor]:
 > These keys are in the bandwidth file header, but there are not any
 similar keys in the relay lines:
 > * recent_priority_list_count

 There's "relay_recent_priority_list_count":
 
https://github.com/torproject/sbws/blob/0333fadc221baf17d429f55261842f9f6e09ba5b/sbws/lib/v3bwfile.py#L590.
 But i forgot to add it in the example in #29754.

 > * recent_priority_relay_count

 This would be the number of relays that were in a priority queue when this
 relay was prioritized?.
 I'm not sure it's useful.

 > * recent_measurement_attempt_count

 There's "relay_recent_measurement_attempt_count":
 
https://github.com/torproject/sbws/blob/0333fadc221baf17d429f55261842f9f6e09ba5b/sbws/lib/v3bwfile.py#L590.
 But i forgot to add it in the example in #29754.

 > * recent_measurement_failure_count

 This's the one that we might be able to guess after all the others. I
 don't think it's possible to know it during the measurement, since it
 would be the case when the queued relay didn't end up in the worker thread
 `measure_relay` nor the callback `result_putter` nor the callback error
 `result_putter_err`.
 These would happen when the code reach this point:
 
https://github.com/torproject/sbws/blob/0333fadc221baf17d429f55261842f9f6e09ba5b/sbws/lib/v3bwfile.py#L590
 >
 > Counting the number of times that a relay was put in the priority list
 is useful, so we can find out if a relay is not being prioritised.
 >
 > Similarly, counting the number of times that we can't measure a relay is
 also useful.
 >
 > Can we have these keys in each relay line:
 > * relay_recent_measurement_attempt_count

 It is, see above.

 > * relay_recent_measurement_failure_count

 Don't see how, see above.

 If you agree with it, this ticket can be closed.

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

Re: [tor-bugs] #29528 [Core Tor/Tor]: UndefinedBehaviorSanitizer errors should fail the unit tests

[Tor Bug Tracker & Wiki]

#29528: UndefinedBehaviorSanitizer errors should fail the unit tests
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-ci, tor-test, 041-proposed,  |  Actual Points:  0.2
  029-backport, 034-backport, 035-backport,  |
  040-backport   |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
-+-

Comment (by teor):

 Replying to [comment:9 teor]:
 > I expect 0.4.0 to fail until #29527 is merged. If it isn't failing, then
 maybe I made a mistake in this patch?

 I'd like the reviewer to help me work out what's going on here.

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

Re: [tor-bugs] #29280 [Core Tor/Tor]: Use Chutney for CI

[Tor Bug Tracker & Wiki]

#29280: Use Chutney for CI
-+-
 Reporter:  cohosh   |  Owner:  (none)
 Type:  task | Status:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  CI, PTs 029-backport 034-backport|  Actual Points:  1
  035-backport 040-backport, network-team-   |
  roadmap-2019-Q1Q2  |
Parent ID:  #29267   | Points:
 Reviewer:  teor |Sponsor:
 |  Sponsor19
-+-

Comment (by teor):

 nickm, #29703 is ready for you to rebase onto.

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

Re: [tor-bugs] #29703 [Core Tor/Tor]: Backport test-network.sh fixes to 0.2.9

[Tor Bug Tracker & Wiki]

#29703: Backport test-network.sh fixes to 0.2.9
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  merge-after-0403-alpha, teor-merge,  |  Actual Points:  0.3
  CI, PTs 029-backport network-team- |
  roadmap-2019-Q1Q2  |
Parent ID:  #29280   | Points:  0.5
 Reviewer:  nickm|Sponsor:
-+-
Changes (by teor):

 * status:  needs_revision => needs_review
 * keywords:  CI, PTs 029-backport network-team-roadmap-2019-Q1Q2 =>
 merge-after-0403-alpha, teor-merge, CI, PTs 029-backport network-team-
 roadmap-2019-Q1Q2
 * milestone:  Tor: 0.4.1.x-final => Tor: 0.2.9.x-final
 * actualpoints:  0.2 => 0.3


Comment:

 Ok, I have backported tor/src/tools/test-network.sh from 0.3.4 to 0.2.9.

 Here is the pull request:
 ​https://github.com/torproject/tor/pull/773

 I'll need to do an "ours" merge into 0.3.4, because the changes are
 already in 0.3.4.
 There's also no need for an initial mainline merge for this branch.

 I won't merge this into 0.2.9 (and merge forward) until next week: nickm
 is doing an alpha.

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

Re: [tor-bugs] #29500 [Core Tor/Tor]: Broken circuitpadding unittests on appveyor

[Tor Bug Tracker & Wiki]

#29500: Broken circuitpadding unittests on appveyor
-+-
 Reporter:  asn  |  Owner:
 |  mikeperry
 Type:  defect   | Status:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad, tor-relay, tor-cell,|  Actual Points:
  padding, 041-proposed, 040-must|
Parent ID:  #28631   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by teor):

 This bug caused the 0.4.0 changelog merge to release-0.4.0 to fail:
 {{{
 circuitpadding/circuitpadding_tokens: [forking]
   FAIL ../src/test/test_circuitpadding.c:1124: assert(mi->histogram[4]
 OP_EQ 2): 0 vs 2
   [circuitpadding_tokens FAILED]
 circuitpadding/circuitpadding_negotiation: [forking] OK
 circuitpadding/circuitpadding_wronghop: [forking] OK
 circuitpadding/circuitpadding_conditions: [forking] OK
 circuitpadding/circuitpadding_rtt: [forking]
   FAIL ../src/test/test_circuitpadding.c:323:
 assert(relay_side->padding_info[0]->last_received_time_usec OP_NE 0): 0 vs
 0
   [circuitpadding_rtt FAILED]
 }}}
 
https://ci.appveyor.com/project/torproject/tor/builds/23252909/job/4ax058o810mck9xe?fullLog=true#L3043

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

Re: [tor-bugs] #28636 [Core Tor/Tor]: Address WTF-PAD comments by Nick (2018-11-27 over IRC)

[Tor Bug Tracker & Wiki]

#28636: Address WTF-PAD comments by Nick (2018-11-27 over IRC)
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.0.1-alpha
 Severity:  Normal   | Resolution:  fixed
 Keywords:  wtf-pad, tor-relay, tor-cell,|  Actual Points:
  padding, 041-proposed, network-team-   |
  roadmap-2019-Q1Q2  |
Parent ID:  #28632   | Points:  3
 Reviewer:  nickm|Sponsor:
 |  Sponsor2
-+-
Changes (by teor):

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


Comment:

 Ok, it passed. Merged to master.

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

Re: [tor-bugs] #28925 [Core Tor/Tor]: distinguish PT vs proxy for real in bootstrap tracker

[Tor Bug Tracker & Wiki]

#28925: distinguish PT vs proxy for real in bootstrap tracker
-+-
 Reporter:  catalyst |  Owner:
 |  catalyst
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  s8-bootstrap, usability, ux, tor-|  Actual Points:  2
  pt, tbb-needs, 040-must, network-team- |
  roadmap-2019-Q1Q2  |
Parent ID:  #28018   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor19
-+-
Changes (by catalyst):

 * actualpoints:   => 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] #24546 [Core Tor/Tor]: Use tor_addr_is_v4() rather than family, or reject all v6-mapped IPv4 addresses

[Tor Bug Tracker & Wiki]

#24546: Use tor_addr_is_v4() rather than family, or reject all v6-mapped IPv4
addresses
-+-
 Reporter:  teor |  Owner:  neel
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:
 Keywords:  tor-dirauth, ipv6,   |  Actual Points:
  033-triage-20180320, 033-removed-20180320, |
  035-triaged-in-20180711,   |
  040-deferred-20190220  |
Parent ID:   | Points:  1
 Reviewer:  ahf  |Sponsor:
 |  SponsorV-can
-+-
Changes (by teor):

 * status:  needs_review => needs_revision
 * version:   => Tor: unspecified


Comment:

 The CI on this ticket did not pass:
 {{{
 src/core/or/policies.c: In function ‘exit_policy_remove_redundancies’:
 src/core/or/policies.c:1709:19: error: variable ‘family’ set but not used
 [-Werror=unused-but-set-variable]
sa_family_t family;
^
 cc1: all warnings being treated as errors
 make: *** [src/core/or/src_core_libtor_app_testing_a-policies.o] Error 1
 make: *** Waiting for unfinished jobs
 }}}
 https://travis-ci.org/torproject/tor/jobs/509624393

 Please make sure that the CI passes before putting it in needs_review
 again.

 Also, the bugfix release in the changes file is the release where the bug
 was introduced, not the release where the bug was fixed. In this ticket,
 that's the release where tor_addr_is_v4() was introduced.

 Here's how you can find the release that this bug was introduced in:
 {{{
 # find the first commit that talks about tor_addr_is_v4
 $ git log --reverse -S tor_addr_is_v4 master
 commit bbbf504281
 Author: Nick Mathewson 
 Date:   Thu Jul 19 18:46:09 2007 +

  r13827@catbus:  nickm | 2007-07-19 14:42:25 -0400
  Merge in some generic address manipulation code from croup.  Needs
 some work.
 ...
 # find the release that contains that commit
 $ git describe --contains bbbf504281
 tor-0.2.0.3-alpha~82
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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: #29018, #29806

[Tor Bug Tracker & Wiki]

Batch modification to #29018, #29806 by teor:


Comment:
Tag these tickets for merge after 0.4.0.3-alpha, to make searches easier.

--
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] #29662 [Core Tor/Tor]: Introduce assert functions that allow us to printf error message

[Tor Bug Tracker & Wiki]

#29662: Introduce assert functions that allow us to printf error message
+--
 Reporter:  rl1987  |  Owner:  rl1987
 Type:  enhancement | Status:
|  needs_revision
 Priority:  Medium  |  Milestone:  Tor:
|  0.4.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  asn-merge, nickm-merge, teor-merge  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  ahf |Sponsor:
+--
Changes (by teor):

 * cc: nickm (added)
 * keywords:   => asn-merge, nickm-merge, teor-merge
 * status:  merge_ready => needs_revision


Comment:

 I wonder why we're using static arrays rather than tor_asprintf()?
 Are they long enough for printf-style assert messages?
 Maybe nickm knows why they have to be static arrays.

 Also, I found a grammar nitpick.

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

Re: [tor-bugs] #28636 [Core Tor/Tor]: Address WTF-PAD comments by Nick (2018-11-27 over IRC)

[Tor Bug Tracker & Wiki]

#28636: Address WTF-PAD comments by Nick (2018-11-27 over IRC)
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:
 |  merge_ready
 Priority:  High |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.0.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad, tor-relay, tor-cell,|  Actual Points:
  padding, 041-proposed, network-team-   |
  roadmap-2019-Q1Q2  |
Parent ID:  #28632   | Points:  3
 Reviewer:  nickm|Sponsor:
 |  Sponsor2
-+-

Comment (by teor):

 The branch in my repository failed on Appveyor due to #29706, which has
 already been merged to master. Rebuilding, to make sure that the failure
 does not happen all the time.

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

Re: [tor-bugs] #29806 [Core Tor/Tor]: Ignore bandwidth file lines with "vote=0"

[Tor Bug Tracker & Wiki]

#29806: Ignore bandwidth file lines with "vote=0"
-+-
 Reporter:  juga |  Owner:  juga
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-bwauth, 040-backport,|  Actual Points:
  035-backport, 034-backport asn-merge   |
Parent ID:  #28563   | Points:  1
 Reviewer:  nickm, teor  |Sponsor:
-+-
Changes (by teor):

 * reviewer:  nickm => nickm, teor


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

Re: [tor-bugs] #29693 [Core Tor/Tor]: Decrease probability of stochastic failures in test-slow

[Tor Bug Tracker & Wiki]

#29693: Decrease probability of stochastic failures in test-slow
-+-
 Reporter:  teor |  Owner:  asn
 Type:  defect   | Status:
 |  merge_ready
 Priority:  High |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.0.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  nickm-merge, tor-ci, tor-test,   |  Actual Points:  0.5
  040-must, 040-backport |
Parent ID:   | Points:  0.5
 Reviewer:  teor |Sponsor:
 |  Sponsor2-must
-+-
Changes (by teor):

 * reviewer:   => teor


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

Re: [tor-bugs] #29754 [Core Tor/Tor]: Include new monitoring KeyValues in the bandwidth-file-spec

[Tor Bug Tracker & Wiki]

#29754: Include new monitoring KeyValues in the bandwidth-file-spec
-+-
 Reporter:  juga |  Owner:  juga
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, bandwidth-file-spec, tor-  |  Actual Points:
  bwauth |
Parent ID:  #28547   | Points:  1
 Reviewer:  teor, juga   |Sponsor:
-+-
Changes (by teor):

 * reviewer:  teor => teor, juga


Comment:

 Replying to [comment:5 teor]:
 > I'm sorry, but this branch conflicts with #29813.
 >
 > I'm going to merge #29813, because it's merge ready.
 > Then I'll push some changes to this branch, rebased on the new master.

 It was easier to rebase #29813 on my changes for this ticket.
 See https://github.com/torproject/torspec/pull/68

 Please review my changes in that branch.

 > After that, I'll have some questions for you about missing KeyValues.

 I opened #29854 for missing KeyValues in the relay line, and #29853 for
 missing relays in the bandwidth file when we're below MIN_REPORT. Let's
 talk about those issues in those tickets.

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

Re: [tor-bugs] #29813 [Core Tor/Tor]: Add unmeasured and vote Line KeyValues in the bandwidth-file-spec

[Tor Bug Tracker & Wiki]

#29813: Add unmeasured and vote Line KeyValues in the bandwidth-file-spec
-+-
 Reporter:  juga |  Owner:  juga
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, bandwidth-file-spec, tor-  |  duplicate
  bwauth |  Actual Points:
Parent ID:  #28563   | Points:  1
 Reviewer:  nickm, teor  |Sponsor:
-+-
Changes (by teor):

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


Comment:

 Rebased on to #29754, because there were conflicts. Let's deal with it in
 #29754.

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

Re: [tor-bugs] #29853 [Core Tor/sbws]: sbws should show relays for diagnostics, even when MIN_REPORT has not been reached

[Tor Bug Tracker & Wiki]

#29853: sbws should show relays for diagnostics, even when MIN_REPORT has not 
been
reached
-+-
 Reporter:  teor |  Owner:  juga
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  sbws:
 |  1.1.0
Component:  Core Tor/sbws|Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-bwauth, sbws-1.0-must-   |  Actual Points:
  moved-20181128, sbws-11x-final-|
  removed-20190312, sbws-110-proposed, changes-  |
  version-minor  |
Parent ID:  #28563   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by teor):

 Here is the spec for this change:
 
https://github.com/torproject/torspec/pull/68/commits/bce5edc7382bfe229f9b56124574b97df1939c1b

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29854 [Core Tor/sbws]: Missing diagnostic keys in relay lines, but the data is in the header

[Tor Bug Tracker & Wiki]

#29854: Missing diagnostic keys in relay lines, but the data is in the header
-+-
 Reporter:  teor |  Owner:  juga
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:  sbws: 1.1.0
Component:  Core |Version:
  Tor/sbws   |   Keywords:  tor-bwauth, sbws-1.0-must-
 Severity:  Normal   |  moved-20181128, sbws-11x-final-
 |  removed-20190312, sbws-110-proposed, changes-
 |  version-minor
Actual Points:   |  Parent ID:  #28547
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 These keys are in the bandwidth file header, but there are not any similar
 keys in the relay lines:
 * recent_priority_list_count
 * recent_priority_relay_count
 * recent_measurement_attempt_count
 * recent_measurement_failure_count

 Counting the number of times that a relay was put in the priority list is
 useful, so we can find out if a relay is not being prioritised.

 Similarly, counting the number of times that we can't measure a relay is
 also useful.

 Can we have these keys in each relay line:
 * relay_recent_measurement_attempt_count
 * relay_recent_measurement_failure_count

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29853 [Core Tor/sbws]: sbws should show relays for diagnostics, even when MIN_REPORT has not been reached

[Tor Bug Tracker & Wiki]

#29853: sbws should show relays for diagnostics, even when MIN_REPORT has not 
been
reached
-+-
 Reporter:  teor |  Owner:  juga
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:  sbws: 1.1.0
Component:  Core |Version:
  Tor/sbws   |   Keywords:  tor-bwauth, sbws-1.0-must-
 Severity:  Normal   |  moved-20181128, sbws-11x-final-
 |  removed-20190312, sbws-110-proposed, changes-
 |  version-minor
Actual Points:   |  Parent ID:  #28563
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Hi juga,

 There's a serious bug in #28563: sbws is not reporting any relays until
 MIN_REPORT has been reached.

 But we want sbws to always report every relay for diagnostics. If the
 bandwidth file doesn't have minimum_number_eligible_relays, they should
 all be marked as "under_min_report=1 vote=0".

 
https://github.com/torproject/sbws/blob/6070d36022dc2130518dd0c68332166b2bf76c73/sbws/lib/v3bwfile.py#L1352

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

Re: [tor-bugs] #29843 [Applications/Tor Browser]: Backport fix for bug 1527534 for Tor Browser for Android

[Tor Bug Tracker & Wiki]

#29843: Backport fix for bug 1527534 for Tor Browser for Android
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  TorBrowserTeam201903R,   |  Actual Points:
  GeorgKoppen201903, tbb-8.5 |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by sysrqb):

 Seems reasonable. It's a little ugly, but I agree this is a safer method
 of applying the patch than applying it on all platforms. I haven't tested
 the patch yet, but it looks good. I'll confirm tomorrow.

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

Re: [tor-bugs] #16473 [Applications/Tor Browser]: Investigate WebGL highp precision prevalence

[Tor Bug Tracker & Wiki]

#16473: Investigate WebGL highp precision prevalence
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff38-esr, tbb-fingerprinting, tbb-   |  Actual Points:
  mobile |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by sysrqb):

 * keywords:  ff38-esr, tbb-fingerprinting => ff38-esr, tbb-fingerprinting,
 tbb-mobile


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

Re: [tor-bugs] #21304 [Obfuscation/Snowflake]: Sanitize snowflake.log

[Tor Bug Tracker & Wiki]

#21304: Sanitize snowflake.log
---+
 Reporter:  arlolra|  Owner:  cohosh
 Type:  defect | Status:  needs_revision
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords:  starter|  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:
---+

Comment (by dcf):

 Replying to [comment:11 cohosh]:
 > What are our feelings about scrubbing fingerprints from logs as well? Is
 it necessary? The one in particular I'm looking at is the received answer
 in the client log:
 > {{{
 > a=ice-options:trickle
 > a=fingerprint:sha-256
 
8D:CE:FE:08:F1:AC:32:30:88:D1:B4:1A:34:84:19:C2:43:18:4A:57:A9:20:2F:DC:C2:32:01:38:F9:8B:E5:8C
 > a=setup:active
 > a=mid:data
 > }}}
 >
 > If we don't need the fingerprint, I'd prefer to "over scrub" instead of
 potentially leaking info if the IPv6 logging violates the above
 assumption.

 (Sidestepping the question slightly.) In the case of these full SDP
 stanzas, I think we should just not be logging them at all, not by default
 anyway.

 The historical reason why the client logs these, I believe, has to do with
 early development of the system, when we would do ICE signaling manually
 (i.e., copy-and-paste the information from the terminal and into the
 browser, and vice versa). That's what the "SEND" button at
 https://snowflake.torproject.org/snowflake.html, and the
 `NewCopyPasteDialer` in client, are for. I'm okay with that mode of
 operation going away.

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

Re: [tor-bugs] #21304 [Obfuscation/Snowflake]: Sanitize snowflake.log

[Tor Bug Tracker & Wiki]

#21304: Sanitize snowflake.log
---+
 Reporter:  arlolra|  Owner:  cohosh
 Type:  defect | Status:  needs_revision
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords:  starter|  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:
---+
Changes (by dcf):

 * status:  needs_review => needs_revision
 * cc: dcf (added)


Comment:

 Thanks, this is looking pretty good.

 We'll need the same functionality across multiple programs: broker,
 client, proxy-go, server. I think you've what you've done so far—putting
 the tests in server and copying the code where needed—is good for
 prototyping. Let me suggest a further simplification: ''only'' worry about
 the server log for now, and then we can perhaps factor the safe-logging
 code into a separate package for use by the other programs.

 * [https://github.com/cohosh/snowflake/compare/ticket21304#diff-
 91bbeda7eb98a7adc57b9e47e2cf5c2bL283 In server],
   logs are scrubbed whether the `--log` option is used or not.
   [https://github.com/cohosh/snowflake/compare/ticket21304#diff-
 ba4bd8a4477426567c409d66c2cf8a28L383 In proxy-go] though,
   logs are only scrubbed when `--log` is used, otherwise they are left
 unscrubbed.
   Is there a reason for the difference?
   I think it's best to default to scrubbed in all cases.
   Maybe even [https://github.com/cohosh/snowflake/compare/ticket21304
 #diff-0efd2b39fd0c8010b9dd51b4f07edf1bL94 in client],
   we should run logs through the scrubber before sending them to
 `ioutil.Discard`,
   both to remind us to use the scrubber after we can rely on #26360 being
 fixed and re-enable non-file logging,
   and to eliminate one difference in the logging code paths
   (imagine a bug in the log scrubber that only manifests when logging to a
 file).
   Maybe use logic like this:
   {{{
 var logOutput io.Writer = os.Stderr
 if logFilename != "" {
 f, err := os.OpenFile(logFilename,
 os.O_CREATE|os.O_APPEND|os.O_WRONLY, 0600)
 if err != nil {
 log.Fatalf("can't open log file: %s", err)
 }
 defer f.Close()
 logOutput = f
 }
 //We want to send the log output through our scrubber first
 log.SetOutput(&logScrubber{logOutput})
   }}}
   In client, the initial value for `logOutput` can be `ioutil.Discard`
 rather than `os.Stderr`.
 * Speaking of which, the default log output in the absence of a `--log`
 option should be
   `os.Stderr`, not `os.Stdout`.
   [https://golang.org/pkg/log/#pkg-overview Ref]: "That logger writes to
 standard error..."
   There's now a [https://golang.org/pkg/log/#Logger.Writer Logger.Writer]
 method that would allow
   us to ask for the default output, but as it was only
 [https://github.com/golang/go/pull/28399 added in 1.12],
   it's probably still too new to use.
 * The `logScrubber.Write` method only looks at one buffer's worth of data
 at a time,
   so it fails when an IP address is split across buffers. For example,
 this test fails:
   {{{
 type byteAtATimeWriter struct {
 io.Writer
 }
 func (w *byteAtATimeWriter) Write(p []byte) (int, error) {
 total := 0
 for i := range p {
 n, err := w.Writer.Write(p[i : i+1])
 total += n
 if err != nil {
 return total, err
 }
 }
 return total, nil
 }
 func TestLogScrubberSplit(t *testing.T) {
 log.SetFlags(0)
 var buff bytes.Buffer
 log.SetOutput(&byteAtATimeWriter{&logScrubber{&buff}})
 log.Print("test 1.2.3.4 test")
 if !bytes.Equal(buff.Bytes(), []byte("test X.X.X.X test\n")) {
 t.Errorf("%q", buff.Bytes())
 }
 }
   }}}
   See below re `RedactErrorWriter` for an idea on how to deal with this.
 * You can use `!bytes.Equal(a, b)` instead of `bytes.Compare(a, b) != 0`.
 Try this:
   {{{
 gofmt -l -w -r 'bytes.Compare(a, b) != 0 -> !bytes.Equal(a, b)'
 server_test.go
   }}}
   Or, use `buff.String` and use string equality.
 * Should we scrub port numbers, too? A port number could be identifying
 within a short time span.
   See below for more ideas about this.
 * Consider structuring repetitive tests like this:
   {{{
 for _, test := range []struct {
 input, expected string
 }{
 {
 "http: TLS handshake error from 129.97.208.23:38310:",
 "http: TLS handshake error from X.X.X.X:38310:\n",
 },
 {
 "http2: panic serving
 [2620:101:f000:780:9097:75b1:519f:dbb8]:58344: interface conversion:
 *http2.responseWriter is not http.Hijacker: missing method Hijack",
 "http2: 

Re: [tor-bugs] #29754 [Core Tor/Tor]: Include new monitoring KeyValues in the bandwidth-file-spec

[Tor Bug Tracker & Wiki]

#29754: Include new monitoring KeyValues in the bandwidth-file-spec
-+-
 Reporter:  juga |  Owner:  juga
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, bandwidth-file-spec, tor-  |  Actual Points:
  bwauth |
Parent ID:  #28547   | Points:  1
 Reviewer:  teor |Sponsor:
-+-
Changes (by teor):

 * reviewer:   => teor


Comment:

 I'm sorry, but this branch conflicts with #29813.

 I'm going to merge #29813, because it's merge ready.
 Then I'll push some changes to this branch, rebased on the new master.

 After that, I'll have some questions for you about missing KeyValues.

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

Re: [tor-bugs] #28636 [Core Tor/Tor]: Address WTF-PAD comments by Nick (2018-11-27 over IRC)

[Tor Bug Tracker & Wiki]

#28636: Address WTF-PAD comments by Nick (2018-11-27 over IRC)
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:
 |  merge_ready
 Priority:  High |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.0.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad, tor-relay, tor-cell,|  Actual Points:
  padding, 041-proposed, network-team-   |
  roadmap-2019-Q1Q2  |
Parent ID:  #28632   | Points:  3
 Reviewer:  nickm|Sponsor:
 |  Sponsor2
-+-

Comment (by teor):

 I squashed "Improvements based on Tim's review." into "circpad/prob_distr:
 Use crypto_fast_rng() instead of the old RNG."

 I'm waiting for CI to pass, then I will merge to master.

 Reminder: Please fill in the actual points on 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] #29847 [Core Tor/Tor]: Improve our handling of stochastic tests

[Tor Bug Tracker & Wiki]

#29847: Improve our handling of stochastic tests
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prob-distr math tor-test |  Actual Points:
  041-proposed   |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  prob-distr math tor-test 041-must => prob-distr math tor-test
 041-proposed
 * milestone:  Tor: 0.4.1.x-final => Tor: unspecified


Comment:

 We adjusted #29693 so that the false positive rate is acceptable, even if
 the tests run in every supported release series.

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

Re: [tor-bugs] #29852 [Internal Services/Service - git]: Let ahf and cohosh push to /pluggable-transports/snowflake.git

[Tor Bug Tracker & Wiki]

#29852: Let ahf and cohosh push to /pluggable-transports/snowflake.git
-+
 Reporter:  dcf  |  Owner:  tor-gitadm
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  snowflake|  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by irl):

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


Comment:

 {{{
 @snowflake   = serene arlo dcf ahf cohosh
 }}}

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

Re: [tor-bugs] #29768 [Applications/Tor Browser]: Introduce new features to users in Tor Browser

[Tor Bug Tracker & Wiki]

#29768: Introduce new features to users in Tor Browser
--+--
 Reporter:  antonela  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-8.5   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by dunqan):

 Hey mcs/gk & antonela,

 Some initial ideas for feedback below:

 == about:tor ==

 * Update the copy on the onboarding-speech-bubble
 * Reduce the border radius to ~12px
 * Add a notification dot (hex 00E2B1)

 On that last point, would it be possible to animate the dot slightly? e.g.
 Could we make it pulse in CSS, like so [https://codepen.io/olam/pen/zcqea
 here] or [https://codepen.io/vram1980/pen/Kyaie here]? Alternatively
 something like [http://jsfiddle.net/risto/hvabkcc7/ this] would be
 subtler.

 [[Image(https://trac.torproject.org/projects/tor/raw-
 attachment/ticket/29768/new-features-1.0.png, 700px)]]

 == Onboarding ==

 * Automatically skip returning users down to the first "New" item
 * Replace tick icon with purple "NEW" pill for updated items (I've redrawn
 & increased the size of the tick icon slightly to match too)
 * Consider a highlight state for text to emphasise changes for returning
 users (this is really an optional extra, however I'm conscious that some
 updates in future may be quite subtle and may need the extra emphasis)

 [[Image(https://trac.torproject.org/projects/tor/raw-
 attachment/ticket/29768/new-features-2.0.png, 700px)]]

 Full & downloadable .sketch doc here for reference antonela:
 https://sketch.cloud/s/d1Wv2

 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] #29801 [Core Tor/Tor]: Add teor's suggestions for Prop#299 (referring IPv4 or IPv6 based on IP Version Failure Count)

[Tor Bug Tracker & Wiki]

#29801: Add teor's suggestions for Prop#299 (referring IPv4 or IPv6 based on IP
Version Failure Count)
---+--
 Reporter:  neel   |  Owner:  neel
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ipv6, prop299  |  Actual Points:
Parent ID:  #27491 | Points:
 Reviewer:  nickm  |Sponsor:
---+--
Changes (by neel):

 * status:  needs_revision => needs_review


Comment:

 I have pushed your suggestions as two new commits to
 https://github.com/torproject/torspec/pull/63. I hope I didn't miss
 anything.

 Setting as "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] #29768 [Applications/Tor Browser]: Introduce new features to users in Tor Browser

[Tor Bug Tracker & Wiki]

#29768: Introduce new features to users in Tor Browser
--+--
 Reporter:  antonela  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-8.5   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dunqan):

 * Attachment "new-features-1.0.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] #29768 [Applications/Tor Browser]: Introduce new features to users in Tor Browser

[Tor Bug Tracker & Wiki]

#29768: Introduce new features to users in Tor Browser
--+--
 Reporter:  antonela  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-8.5   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dunqan):

 * Attachment "new-features-2.0.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] #29852 [Internal Services/Service - git]: Let ahf and cohosh push to /pluggable-transports/snowflake.git

[Tor Bug Tracker & Wiki]

#29852: Let ahf and cohosh push to /pluggable-transports/snowflake.git
-+
 Reporter:  dcf  |  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake|  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by dcf):

 This is per our discussion in #tor-meeting today.
 http://meetbot.debian.net/tor-meeting/2019/tor-
 meeting.2019-03-21-20.00.log.html

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

[tor-bugs] #29852 [Internal Services/Service - git]: Let ahf and cohosh push to /pluggable-transports/snowflake.git

[Tor Bug Tracker & Wiki]

#29852: Let ahf and cohosh push to /pluggable-transports/snowflake.git
-+
 Reporter:  dcf  |  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   |   Keywords:  snowflake
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+
 {{{
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512

 I'l like ahf and cohosh to be able to push to the
 /pluggable-transports/snowflake.git repo.

 Signed, David 2019-03-21
 -BEGIN PGP SIGNATURE-

 iQIzBAEBCgAdFiEEeXoyauxKR4rwUMw64rk9gVzTiOUFAlyUEAoACgkQ4rk9gVzT
 iOXPww//UwoNN6Fi3PaKepwqQYbO6TunJJ4SeBzwDPKOFwOe0E0F5zSzJnVP329h
 8f5o/20E88gRdHRlbJ5SzZnGWwW2KJFSRStJhSx7r3glJrsbsK6gUXFB8nbIuM7B
 sczbG7gzOv9b3ly/EjjBk0+mC5EjtdzqsiqKYDH2mXQCRoDQsqlnWAvCVfPPgnC4
 LRyFLtaK5dZQU6gRWqBN1EhWzrtLdbl2qSG2mLot+8z/BJrUk2BkNDXsyQla6ahP
 vKpS3XKN5ldBfxBXTqOLZQTgUKQwRoTIT0xZpbuSb2WCRx7N3WDWbpwKbyL4GTJO
 ZNNXsrz5qiSZ6h20qHTMt4TMrmKMQrmkcocWJ/6uqCqYCrDqCyF7SFmfwJzNYgtE
 36OfQnaYcuH8XJYHEviwrLJRPWfgjcxzkEvA/RxwFTl/1Er1ulwxrFq8yya8IFCy
 uQjSydLtga/WLWhq993x8aUGFvapF4P8L9iWkRSEqxln+WTxbx4F3yAszH3UeALS
 eCzyl5kp6N1MkEB+VbvfsEViOLYqSwgZf74XRkmcMt9R1fy72CpSqUO24gY0Neuu
 XpJ7F6+ksvKhKie31fZPxQb30ifEyZgsXSh4a9ia/62X99cl13sAZ/aoJ3vCjT8L
 kfCRit6QtZ5GuPCOXTuiPbgkxlBJRvnp4TZsB8iAkmIUoBuzH5U=
 =nwyV
 -END PGP SIGNATURE-
 }}}

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

Re: [tor-bugs] #28925 [Core Tor/Tor]: distinguish PT vs proxy for real in bootstrap tracker

[Tor Bug Tracker & Wiki]

#28925: distinguish PT vs proxy for real in bootstrap tracker
-+-
 Reporter:  catalyst |  Owner:
 |  catalyst
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  s8-bootstrap, usability, ux, tor-|  Actual Points:
  pt, tbb-needs, 040-must, network-team- |
  roadmap-2019-Q1Q2  |
Parent ID:  #28018   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor19
-+-
Changes (by catalyst):

 * status:  assigned => needs_review


Comment:

 Pull request at https://github.com/torproject/tor/pull/827

 I believe this merges cleanly to master, but it pushes a couple of files
 over their line count exceptions in practracker. I'm not sure how we want
 to handle that.

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

Re: [tor-bugs] #28652 [Core Tor/sbws]: When sbws stops making progress, log a warning

[Tor Bug Tracker & Wiki]

#28652: When sbws stops making progress, log a warning
+---
 Reporter:  teor|  Owner:  juga
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:  sbws: 1.1.x-final
Component:  Core Tor/sbws   |Version:
 Severity:  Normal  | Resolution:  implemented
 Keywords:  no-changes-version  |  Actual Points:
Parent ID:  #28547  | Points:  1
 Reviewer:  asn |Sponsor:
+---
Changes (by juga):

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


Comment:

 i like the code, merged.

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

Re: [tor-bugs] #29754 [Core Tor/Tor]: Include new monitoring KeyValues in the bandwidth-file-spec

[Tor Bug Tracker & Wiki]

#29754: Include new monitoring KeyValues in the bandwidth-file-spec
-+-
 Reporter:  juga |  Owner:  juga
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, bandwidth-file-spec, tor-  |  Actual Points:
  bwauth |
Parent ID:  #28547   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by juga):

 * status:  assigned => needs_review


Comment:

 I think i might need to rephrase almost all, because i'm not sure it can
 be understood, but in case review gives some tips.

 https://github.com/torproject/torspec/pull/67

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

Re: [tor-bugs] #28499 [Webpages/Support]: tb-manual: create redirects for old resources

[Tor Bug Tracker & Wiki]

#28499: tb-manual: create redirects for old resources
--+--
 Reporter:  emmapeel  |  Owner:  hiro
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Support  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by emmapeel):

 * status:  new => assigned


Comment:

 The possibility of doing this is very important for when we change the
 website, so we can catch up on all the broken links.

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

Re: [tor-bugs] #28487 [Webpages/Styleguide]: add 'odd' and 'even' styling for tables to the tor styleguide

[Tor Bug Tracker & Wiki]

#28487: add 'odd' and 'even' styling for tables to the tor styleguide
-+
 Reporter:  emmapeel |  Owner:  hiro
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Webpages/Styleguide  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by emmapeel):

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


Comment:

 my bad, there is already stripy styling:
 https://styleguide.torproject.org/

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

Re: [tor-bugs] #28474 [Community/Tor Support]: add https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO/InstantMessaging to the support portal

[Tor Bug Tracker & Wiki]

#28474: add
https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO/InstantMessaging
to the support portal
---+--
 Reporter:  emmapeel   |  Owner:  stephw
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Community/Tor Support  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by emmapeel):

 * component:  Community/Tor Browser Manual => Community/Tor Support


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

Re: [tor-bugs] #28474 [Community/Tor Browser Manual]: add https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO/InstantMessaging to the support portal (was: add https://trac.torproject.org/pro

[Tor Bug Tracker & Wiki]

#28474: add
https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO/InstantMessaging
to the support portal
--+--
 Reporter:  emmapeel  |  Owner:  stephw
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Community/Tor Browser Manual  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Description changed by emmapeel:

Old description:

> This great document should be signed off and published in the user manual
> (so it can be translated)

New description:

 This great document should be signed off and published in the support
 portal (so it can be translated)

--

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

Re: [tor-bugs] #27491 [Core Tor/Tor]: Prefer IPv4 or IPv6 based on the number of failures

[Tor Bug Tracker & Wiki]

#27491: Prefer IPv4 or IPv6 based on the number of failures
--+--
 Reporter:  neel  |  Owner:  neel
 Type:  enhancement   | Status:  assigned
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  needs-proposal, ipv6  |  Actual Points:
Parent ID:  #17835| Points:
 Reviewer:|Sponsor:
--+--
Changes (by neel):

 * status:  new => assigned


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

[tor-bugs] #29851 [Core Tor/sbws]: Catch SIGHUP to be able to reload configuration without stopping the scanner

[Tor Bug Tracker & Wiki]

#29851: Catch SIGHUP to be able to reload configuration without stopping the
scanner
---+---
 Reporter:  juga   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  sbws: unspecified
Component:  Core Tor/sbws  |Version:  sbws: 1.0.5
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points:  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] #29681 [Internal Services/Tor Sysadmin Team]: replace munin with prometheus and grafana

[Tor Bug Tracker & Wiki]

#29681: replace munin with prometheus and grafana
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 the apache dashboard has been deployed on all hosts running apache.

 i did a quick investigation of the other possible exporters and dashboards
 that we could use in our infrastructure. here's a copy of my notes:

 '''email servers monitoring (eugeni, etc? postfix)'''

 * [https://github.com/kumina/postfix_exporter in debian],
 [https://github.com/kumina/postfix_exporter/issues/21 possible dashboard]
 * another approach: [https://github.com/cherti/mailexporter email delivery
 tests]

 '''mailman monitoring'''

 no known exporter or dashboard

 '''databases'''

 * [https://github.com/wrouesnel/postgres_exporter/ postgres exporter in
 debian]
 * [https://github.com/wrouesnel/postgres_exporter/issues/218 no known
 dashboard]
 * [https://github.com/prometheus/mysqld_exporter mysqld exporter in
 debian] - [https://grafana.com/dashboards/625 possible dashboard]
 [https://github.com/percona/grafana-dashboards another from  percona],
 [https://github.com/prometheus/mysqld_exporter/issues/286 not officially
 documented]

 '''DNS / bind'''

 - [https://github.com/digitalocean/bind_exporter/ in debian],
 [https://grafana.com/dashboards/1666 official dashboard]

 '''GitLab'''

 there is [https://docs.gitlab.com/ee/administration/monitoring/prometheus/
 builtin support for prometheus] that has to be
 
[https://docs.gitlab.com/ee/administration/monitoring/prometheus/gitlab_metrics.html
 configured]

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

Re: [tor-bugs] #13005 [Community/Tor Browser Manual]: Please document Tor Browser environment variables

[Tor Bug Tracker & Wiki]

#13005: Please document Tor Browser environment variables
--+--
 Reporter:  mttp  |  Owner:  traumschule
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Community/Tor Browser Manual  |Version:
 Severity:  Normal| Resolution:
 Keywords:  faq   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by emmapeel):

 * component:  Webpages/Website => Community/Tor Browser Manual


Comment:

 maybe we should add it to the tb-manual?

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

Re: [tor-bugs] #29297 [Obfuscation/Obfsproxy]: Write reachability tests to verify if obfs4 is working or not

[Tor Bug Tracker & Wiki]

#29297: Write reachability tests to verify if obfs4 is working or not
-+-
 Reporter:  chelseakomlo |  Owner:  cohosh
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Obfuscation/Obfsproxy|Version:
 Severity:  Normal   | Resolution:
 Keywords:  obfs4, network-team- |  Actual Points:
  roadmap-2019-Q1Q2  |
Parent ID:  #29279   | Points:  2
 Reviewer:  dcf, ahf |Sponsor:
 |  Sponsor19
-+-
Changes (by dcf):

 * cc: dcf (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] #29816 [Internal Services/Tor Sysadmin Team]: replace "Tor VM hosts" spreadsheet with Grafana dashboard

[Tor Bug Tracker & Wiki]

#29816: replace "Tor VM hosts" spreadsheet with Grafana dashboard
-+-
 Reporter:  anarcat  |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Minor| Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 other possible inspiration include:

  * [https://grafana.com/dashboards/9750 this dashboard] which shows how
 many servers have how many cores - a little backwards really: we'd want to
 list each server instead..
  * this [https://grafana.com/dashboards/3928 libvirt dashboard] (that may
 belong with [https://github.com/kumina/libvirt_exporter this libvirt
 exporter]) - interesting, but doesn't show capacity, only actual usage

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

Re: [tor-bugs] #29512 [Webpages/Website]: Financial reports link is broken

[Tor Bug Tracker & Wiki]

#29512: Financial reports link is broken
--+
 Reporter:  bekeela   |  Owner:  hiro
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by antonela):

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


Comment:

 Fixed at
 
https://github.com/torproject/tpo/pull/35/commits/b2470a7d5274bf9665639ecca1f6aac66d05cce6

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

Re: [tor-bugs] #29503 [Webpages/Website]: Add logo to link preview on new site

[Tor Bug Tracker & Wiki]

#29503: Add logo to link preview on new site
--+--
 Reporter:  steph |  Owner:  steph
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+--
Changes (by steph):

 * Attachment "Screen Shot 2019-03-21 at 3.52.30 PM.png" added.

 old site (bad quality image)

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

Re: [tor-bugs] #29503 [Webpages/Website]: Add logo to link preview on new site

[Tor Bug Tracker & Wiki]

#29503: Add logo to link preview on new site
--+--
 Reporter:  steph |  Owner:  steph
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+--
Changes (by steph):

 * Attachment "Screen Shot 2019-03-21 at 3.52.03 PM.png" added.

 staging preview

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

Re: [tor-bugs] #29503 [Webpages/Website]: Add logo to link preview on new site

[Tor Bug Tracker & Wiki]

#29503: Add logo to link preview on new site
--+--
 Reporter:  steph |  Owner:  steph
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+--

Comment (by steph):

 Not icons, but the website link preview. The image that shows if you post
 the site on social media

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

Re: [tor-bugs] #29515 [Webpages/Website]: Jobs: text in 'required qualifications' and 'preferred qualifications' scrolling box doesn't wrap text legibly

[Tor Bug Tracker & Wiki]

#29515: Jobs: text in 'required qualifications' and 'preferred qualifications'
scrolling box doesn't wrap text legibly
--+
 Reporter:  alsmith   |  Owner:  hiro
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+
Changes (by antonela):

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


Comment:

 Everybody can make changes on that content using markdown. I updated the
 databags this time.
 Fixed at
 
https://github.com/torproject/tpo/pull/35/commits/9df427316d5c26e8e01918d2f77c6503d5375f9c

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

Re: [tor-bugs] #29475 [Webpages/Website]: jobs link is broken on new website pages

[Tor Bug Tracker & Wiki]

#29475: jobs link is broken on new website pages
--+
 Reporter:  arma  |  Owner:  hiro
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by antonela):

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


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

Re: [tor-bugs] #29503 [Webpages/Website]: Add logo to link preview on new site

[Tor Bug Tracker & Wiki]

#29503: Add logo to link preview on new site
--+--
 Reporter:  steph |  Owner:  steph
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+--

Comment (by antonela):

 Those riseup links are dead, which icons are you talking about steph?

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

Re: [tor-bugs] #29504 [Webpages/Website]: Add keywords to website

[Tor Bug Tracker & Wiki]

#29504: Add keywords to website
--+--
 Reporter:  steph |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+--
Changes (by antonela):

 * parent:   => #25640


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

Re: [tor-bugs] #29513 [Webpages/Website]: Grey circles - meant to populate with images?

[Tor Bug Tracker & Wiki]

#29513: Grey circles - meant to populate with images?
--+
 Reporter:  alsmith   |  Owner:  hiro
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by antonela):

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


Comment:

 We have beautiful illos there now! take a look <3

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

Re: [tor-bugs] #29516 [Webpages/Website]: On about/jobs, the 'Join us on IRC' link doesn't go anywhere

[Tor Bug Tracker & Wiki]

#29516: On about/jobs, the 'Join us on IRC' link doesn't go anywhere
--+
 Reporter:  alsmith   |  Owner:  hiro
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+
Changes (by antonela):

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


Comment:

 Fixed at
 
https://github.com/torproject/tpo/pull/35/commits/023a52cbd532114a4b74170752c2eead444f295f

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

Re: [tor-bugs] #29517 [Webpages/Website]: 'Check out the manual' broken link on download page

[Tor Bug Tracker & Wiki]

#29517: 'Check out the manual' broken link on download page
--+
 Reporter:  alsmith   |  Owner:  hiro
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+
Changes (by antonela):

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


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

Re: [tor-bugs] #29608 [Webpages/Website]: Sponsors Page Update

[Tor Bug Tracker & Wiki]

#29608: Sponsors Page Update
--+
 Reporter:  bekeela   |  Owner:  hiro
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+
Changes (by antonela):

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


Comment:

 fixed at
 
https://github.com/torproject/tpo/pull/35/commits/77ff8cdd8173479a5ec267972f57af87642b9cf0

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

Re: [tor-bugs] #24546 [Core Tor/Tor]: Use tor_addr_is_v4() rather than family, or reject all v6-mapped IPv4 addresses

[Tor Bug Tracker & Wiki]

#24546: Use tor_addr_is_v4() rather than family, or reject all v6-mapped IPv4
addresses
-+-
 Reporter:  teor |  Owner:  neel
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-dirauth, ipv6,   |  Actual Points:
  033-triage-20180320, 033-removed-20180320, |
  035-triaged-in-20180711,   |
  040-deferred-20190220  |
Parent ID:   | Points:  1
 Reviewer:  ahf  |Sponsor:
 |  SponsorV-can
-+-
Changes (by neel):

 * status:  assigned => needs_review


Comment:

 I have an updated PR for this bug:
 https://github.com/torproject/tor/pull/826

 The reason for a new PR is because the Tor codebase has changed
 significantly since my last PR.

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

Re: [tor-bugs] #28622 [Applications/Tor Browser]: Update Tor Browser Icon for Android

[Tor Bug Tracker & Wiki]

#28622: Update Tor Browser Icon for Android
-+-
 Reporter:  pili |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_information
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, tbb-mobile, TBA-a3, |  Actual Points:
  TorBrowserTeam201903, tbb-8.5, tbb-parity  |
Parent ID:  #27399   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * 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] #28622 [Applications/Tor Browser]: Update Tor Browser Icon for Android

[Tor Bug Tracker & Wiki]

#28622: Update Tor Browser Icon for Android
-+-
 Reporter:  pili |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_information
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, tbb-mobile, TBA-a3, |  Actual Points:
  TorBrowserTeam201903, tbb-8.5, tbb-parity  |
Parent ID:  #27399   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * status:  new => needs_information


Comment:

 I started working on that yesterday and today and mainly cleaned-up
 directories. Antonela said she'll help with the mobile icons (thanks!). We
 need the following ones (taking the official ones as example):

 32x32 and 64x64 favicons (see: https://dxr.mozilla.org/mozilla-
 esr60/source/mobile/android/branding/official/content)

 and then a bunch of icons found in the `drawable-Xdpi`folders (see:
 https://dxr.mozilla.org/mozilla-
 esr60/source/mobile/android/branding/official/res).

 In particular (for each of stable, alpha, and nightly, which we want to
 have for mobile as well at some point):

 72x72 and 144x144 in hdpi
 96x96 and 192x192 in xhdpi
 144x144 and 288x288 (Mozilla has 300x300 for alpha and nightly icons
 instead) in xxhdpi
 192x192 in xxxhdpi

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

Re: [tor-bugs] #29813 [Core Tor/Tor]: Add unmeasured and vote Line KeyValues in the bandwidth-file-spec

[Tor Bug Tracker & Wiki]

#29813: Add unmeasured and vote Line KeyValues in the bandwidth-file-spec
-+-
 Reporter:  juga |  Owner:  juga
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, bandwidth-file-spec, tor-  |  Actual Points:
  bwauth |
Parent ID:  #28563   | Points:  1
 Reviewer:  nickm, teor  |Sponsor:
-+-
Changes (by juga):

 * status:  reopened => 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] #29813 [Core Tor/Tor]: Add unmeasured and vote Line KeyValues in the bandwidth-file-spec

[Tor Bug Tracker & Wiki]

#29813: Add unmeasured and vote Line KeyValues in the bandwidth-file-spec
-+-
 Reporter:  juga |  Owner:  juga
 Type:  defect   | Status:
 |  reopened
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, bandwidth-file-spec, tor-  |  Actual Points:
  bwauth |
Parent ID:  #28563   | Points:  1
 Reviewer:  nickm, teor  |Sponsor:
-+-
Changes (by juga):

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


Comment:

 ops

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

Re: [tor-bugs] #29813 [Core Tor/Tor]: Add unmeasured and vote Line KeyValues in the bandwidth-file-spec

[Tor Bug Tracker & Wiki]

#29813: Add unmeasured and vote Line KeyValues in the bandwidth-file-spec
-+-
 Reporter:  juga |  Owner:  juga
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, bandwidth-file-spec, tor-  |  implemented
  bwauth |  Actual Points:
Parent ID:  #28563   | Points:  1
 Reviewer:  nickm, teor  |Sponsor:
-+-
Changes (by juga):

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


Comment:

 ok, let's merge 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] #29805 [Core Tor/Tor]: 41 coverity defects on prob_distr.c

[Tor Bug Tracker & Wiki]

#29805: 41 coverity defects on prob_distr.c
-+
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:  Tor: 0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prob-distr coverity  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by asn):

 * status:  new => needs_review


Comment:

 Thanks for all the help catalyst and riastradh.

 Here is a branch that splits the type-checking part of the macro into its
 own macro:
 https://github.com/torproject/tor/pull/825

 Let's see if CI passes!

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

Re: [tor-bugs] #29843 [Applications/Tor Browser]: Backport fix for bug 1527534 for Tor Browser for Android

[Tor Bug Tracker & Wiki]

#29843: Backport fix for bug 1527534 for Tor Browser for Android
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  TorBrowserTeam201903R,   |  Actual Points:
  GeorgKoppen201903, tbb-8.5 |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  TorBrowserTeam201903, GeorgKoppen201903, tbb-8.5 =>
 TorBrowserTeam201903R, GeorgKoppen201903, tbb-8.5
 * status:  new => needs_review


Comment:

 `bug_29843` (https://gitweb.torproject.org/user/gk/tor-browser-
 build.git/commit/?h=bug_29843&id=b619af79d04bde9313d8a4a2696c4a5a06c60175)
 in my `tor-browser-build` repo has the backport. I went that route because
 I don't want to have the desktop platforms exposed to the backport as it
 did not get any ESR testing on Mozilla's infra (Mozilla did not backport
 the patch themselves as they are not shipping mobile based on ESR).

 It is compiling and the build is running on my phone. However, I did not
 get WebGL to run to further test the patch. Not sure what the problem
 is...

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

Re: [tor-bugs] #29614 [Applications/Tor Browser]: Use SHA-256 algorithm for Windows authenticode timestamping

[Tor Bug Tracker & Wiki]

#29614: Use SHA-256 algorithm for Windows authenticode timestamping
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-security, TorBrowserTeam201903,  |  Actual Points:
  GeorgKoppen201903, tbb-8.5 |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 Replying to [comment:1 gk]:
 > Should be not too hard to adapt our timestamping script, see:
 https://sourceforge.net/p/osslsigncode/support-requests/9/.

 Unfortunately, this did not work. I'll need to look again at the code and
 our patch do decouple the signing from the timestamping to figure out what
 goes wrong here.

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

Re: [tor-bugs] #29662 [Core Tor/Tor]: Introduce assert functions that allow us to printf error message

[Tor Bug Tracker & Wiki]

#29662: Introduce assert functions that allow us to printf error message
--+
 Reporter:  rl1987|  Owner:  rl1987
 Type:  enhancement   | Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.4.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:  ahf   |Sponsor:
--+
Changes (by ahf):

 * status:  needs_review => merge_ready


Comment:

 The code looks good and I like the idea. Let's see what one of the mergers
 says.

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

Re: [tor-bugs] #28563 [Core Tor/sbws]: Work out how sbws can report excluded relays in the bandwidth file

[Tor Bug Tracker & Wiki]

#28563: Work out how sbws can report excluded relays in the bandwidth file
-+-
 Reporter:  teor |  Owner:  juga
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  sbws:
 |  1.1.0
Component:  Core Tor/sbws|Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-bwauth, sbws-1.0-must-   |  Actual Points:
  moved-20181128, sbws-11x-final-|
  removed-20190312, sbws-110-proposed, changes-  |
  version-minor  |
Parent ID:  #28547   | Points:
 Reviewer:  nickm|Sponsor:
-+-

Comment (by juga):

 Replying to [comment:36 juga]:
 > Replying to [comment:35 teor]:
 > > Juga, after you merge this code, please check that the number of
 relays in the bandwidth file is about the same as the number of relays in
 the consensus.
 >
 > ok, i'm merging everything in my master branch (not in git.tpo) and i'll
 run it for at at least 1 loop in a test server, then check number of
 relays lines is aprox. the same as relays in the consensus.

 Yeah, it's aprox. the same.

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

Re: [tor-bugs] #28563 [Core Tor/sbws]: Work out how sbws can report excluded relays in the bandwidth file

[Tor Bug Tracker & Wiki]

#28563: Work out how sbws can report excluded relays in the bandwidth file
-+-
 Reporter:  teor |  Owner:  juga
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  sbws:
 |  1.1.0
Component:  Core Tor/sbws|Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-bwauth, sbws-1.0-must-   |  Actual Points:
  moved-20181128, sbws-11x-final-|
  removed-20190312, sbws-110-proposed, changes-  |
  version-minor  |
Parent ID:  #28547   | Points:
 Reviewer:  nickm|Sponsor:
-+-

Comment (by juga):

 merged, but can't close cause of children

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

Re: [tor-bugs] #29770 [Internal Services/Service - lists]: mails relayed to gmail.com bounce back

[Tor Bug Tracker & Wiki]

#29770: mails relayed to gmail.com bounce back
---+--
 Reporter:  anarcat|  Owner:  tpa
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Internal Services/Service - lists  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by anarcat):

 so we had another report of a problem occurring with gmail.com recipients
 today on the tor-inter...@lists.torproject.org mailing list.

 the problem was with the email `Message-ID:
 <20190321172741.gb78...@vpn209009.nrl.navy.mil>` which gmail refused with
 the following error:

 {{{
 Mar 21 17:27:53 eugeni/eugeni postfix/smtp[4376]: 6C5ECE0ED2:
 to=<[REDACTED]@gmail.com>, relay=gmail-smtp-
 in.l.google.com[2a00:1450:400c:c00::1a]:25, delay=0.9,
 delays=0.03/0.22/0.15/0.5, dsn=5.7.1, status=bounced (host gmail-smtp-
 in.l.google.com[2a00:1450:400c:c00::1a] said: 550-5.7.1 Unauthenticated
 email from nrl.navy.mil is not accepted due to 550-5.7.1 domain's DMARC
 policy. Please contact the administrator of 550-5.7.1 nrl.navy.mil domain
 if this was a legitimate mail. Please visit 550-5.7.1
 https://support.google.com/mail/answer/2451690 to learn about the 550
 5.7.1 DMARC initiative. j5si3735441wmh.102 - gsmtp (in reply to end of
 DATA command))
 }}}

 The email indeed comes from a domain with the following DMARC policy:

 {{{
 _dmarc.nrl.navy.mil.1031IN  TXT "v=DMARC1; p=reject;
 rua=mailto:dmarc-report...@dren.mil; ri=86400"
 }}}

 ... an aggressive, but not unusual or invalid DMARC policy.

 I'm not sure what the way forward is here, but I believe that a simple fix
 would be to enable the `general/from_is_list` setting to "munge" the
 `From` header to be the mailing list itself instead of the original
 sender. this is a controversial change, so a "lesser-evil" alternative
 might be the `privacy/sender/dmarc_moderation_action` setting which does
 that only for messages with a DMARC policy. But then we get inconsistent
 headers for the mailing list which might confuse filters and/or users.

 since this is a little controversial, i'd like to consult with fellow TPAs
 before going ahead with any change.

 for those who want to experiment with those changes, those are direct URLs
 for the tor-project@ mailing list:

 https://lists.torproject.org/cgi-bin/mailman/admin/tor-
 project/?VARHELP=general/from_is_list
 https://lists.torproject.org/cgi-bin/mailman/admin/tor-
 project/?VARHELP=privacy/sender/dmarc_moderation_action

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

Re: [tor-bugs] #28565 [Core Tor/sbws]: Report excluded results in a relay's bandwidth line

[Tor Bug Tracker & Wiki]

#28565: Report excluded results in a relay's bandwidth line
-+-
 Reporter:  teor |  Owner:  juga
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  sbws:
 |  1.1.0
Component:  Core Tor/sbws|Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-bwauth, sbws-1.0-must-   |  implemented
  moved-20181128, sbws-11x-final-|  Actual Points:
  removed-20190312, sbws-110-proposed, changes-  |
  version-minor  |
Parent ID:  #28547   | Points:  1
 Reviewer:  teor |Sponsor:
-+-
Changes (by juga):

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


Comment:

 merged

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

Re: [tor-bugs] #28983 [Core Tor/sbws]: Work out how long it takes sbws to measure the network

[Tor Bug Tracker & Wiki]

#28983: Work out how long it takes sbws to measure the network
+---
 Reporter:  teor|  Owner:  juga
 Type:  enhancement | Status:  closed
 Priority:  Medium  |  Milestone:  sbws: 1.1.x-final
Component:  Core Tor/sbws   |Version:
 Severity:  Normal  | Resolution:  implemented
 Keywords:  no-changes-version  |  Actual Points:
Parent ID:  | Points:  1
 Reviewer:  asn |Sponsor:
+---
Changes (by juga):

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


Comment:

 merged

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

Re: [tor-bugs] #29589 [Core Tor/sbws]: Recover a destination when it stops failing

[Tor Bug Tracker & Wiki]

#29589: Recover a destination when it stops failing
---+---
 Reporter:  juga   |  Owner:  (none)
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:  sbws: 1.1.x-final
Component:  Core Tor/sbws  |Version:  sbws: 1.0.2
 Severity:  Normal | Resolution:  implemented
 Keywords:  changes-version-patch  |  Actual Points:  1
Parent ID: | Points:  1
 Reviewer:  ahf|Sponsor:
---+---
Changes (by juga):

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


Comment:

 merged

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

Re: [tor-bugs] #29722 [Core Tor/sbws]: Document that authorities are not measured

[Tor Bug Tracker & Wiki]

#29722: Document that authorities are not measured
-+-
 Reporter:  juga |  Owner:  juga
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  sbws:
 |  1.1.x-final
Component:  Core Tor/sbws|Version:  sbws:
 |  1.0.5
 Severity:  Normal   | Resolution:
 |  implemented
 Keywords:  no-changes-version, sbws-docs, easy  |  Actual Points:
Parent ID:   | Points:  1
 Reviewer:  cohosh   |Sponsor:
-+-
Changes (by juga):

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


Comment:

 Merged.

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

Re: [tor-bugs] #29468 [Webpages/Website]: Broken link: "Verify Tor Browser signature here"

[Tor Bug Tracker & Wiki]

#29468: Broken link: "Verify Tor Browser signature here"
--+--
 Reporter:  intrigeri |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #29422| Points:
 Reviewer:|Sponsor:
--+--
Changes (by emmapeel):

 * parent:   => #29422


Comment:

 Yeah actually this ticket will be fixed when #29422 is fixed.

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

Re: [tor-bugs] #29515 [Webpages/Website]: Jobs: text in 'required qualifications' and 'preferred qualifications' scrolling box doesn't wrap text legibly

[Tor Bug Tracker & Wiki]

#29515: Jobs: text in 'required qualifications' and 'preferred qualifications'
scrolling box doesn't wrap text legibly
--+--
 Reporter:  alsmith   |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+--
Changes (by emmapeel):

 * parent:   => #25640


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

Re: [tor-bugs] #28652 [Core Tor/sbws]: When sbws stops making progress, log a warning

[Tor Bug Tracker & Wiki]

#28652: When sbws stops making progress, log a warning
+---
 Reporter:  teor|  Owner:  juga
 Type:  defect  | Status:  merge_ready
 Priority:  Medium  |  Milestone:  sbws: 1.1.x-final
Component:  Core Tor/sbws   |Version:
 Severity:  Normal  | Resolution:
 Keywords:  no-changes-version  |  Actual Points:
Parent ID:  #28547  | Points:  1
 Reviewer:  asn |Sponsor:
+---
Changes (by asn):

 * status:  needs_review => merge_ready


Comment:

 Replying to [comment:9 juga]:
 > should be fixed now

 Hm, better. And the test looks good.

 I think there might be more stuff you can hide into the heartbeat module
 so that they are not exposed in the main loop. The goal is to simplify the
 main loop and hide the heartbeat details into the heartbeat module.

 I did an implementation here:
 
https://github.com/torproject/sbws/pull/354/commits/944bad5561dc92d04569ed06eceadd139315e0d4

 However, I was not able to test it because my user file does not work
 anymore (something about country codes?), and I'm not sure how to run the
 unittest either.

 If you like the code feel free to use it, otherwise, feel free to merge
 the current state of your branch. It's all 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] #29153 [Webpages/Website]: Websites won't allow allow access

[Tor Bug Tracker & Wiki]

#29153: Websites won't allow allow access
--+---
 Reporter:  LethiaNGames  |  Owner:  hiro
 Type:  project   | Status:  closed
 Priority:  Immediate |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Critical  | Resolution:  not a bug
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by emmapeel):

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


Comment:

 please have a look at:

 https://support.torproject.org/censorship/censorship-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

[tor-bugs] #29850 [Webpages/Website]: localize sublinks so you stay on the current language

[Tor Bug Tracker & Wiki]

#29850: localize sublinks so you stay on the current language
--+--
 Reporter:  emmapeel  |  Owner:  hiro
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  website redesign
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:  ux-team,
Actual Points:|  Parent ID:  #25640
   Points:|   Reviewer:
  Sponsor:|
--+--
 * go to https://lektor-
 staging.torproject.org/tpo/staging/es/about/history/
 * click on 'informes' on the menu under the title
 * you are sent to /staging/about/reports/ , instead of
 /es/staging/about/reports/ (mind the /es).

 what should happen:

 * You stay navigating in /es/ as you have selected it previously.

 note: it works ok for button About that is part of the menu at the top of
 the page: that button changes along with the selected language.

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

Re: [tor-bugs] #29849 [Webpages/Website]: first text is duplicated when browsing /about/* subpages

[Tor Bug Tracker & Wiki]

#29849: first text is duplicated when browsing /about/* subpages
--+--
 Reporter:  emmapeel  |  Owner:  hiro
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  website redesign
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team, tpo  |  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+--
Changes (by emmapeel):

 * Attachment "repeated_content.png" added.

 duplicated content

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29849 [Webpages/Website]: first text is duplicated when browsing /about/* subpages

[Tor Bug Tracker & Wiki]

#29849: first text is duplicated when browsing /about/* subpages
--+--
 Reporter:  emmapeel  |  Owner:  hiro
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  website redesign
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:  ux-team, tpo
Actual Points:|  Parent ID:  #25640
   Points:|   Reviewer:
  Sponsor:|
--+--
 When browsing pages on the new tpo site, the first two paragraphs are
 duplicated, see:

 https://lektor-staging.torproject.org/tpo/staging/es/about/history/

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

Re: [tor-bugs] #28636 [Core Tor/Tor]: Address WTF-PAD comments by Nick (2018-11-27 over IRC)

[Tor Bug Tracker & Wiki]

#28636: Address WTF-PAD comments by Nick (2018-11-27 over IRC)
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:
 |  merge_ready
 Priority:  High |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.0.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad, tor-relay, tor-cell,|  Actual Points:
  padding, 041-proposed, network-team-   |
  roadmap-2019-Q1Q2  |
Parent ID:  #28632   | Points:  3
 Reviewer:  nickm|Sponsor:
 |  Sponsor2
-+-
Changes (by asn):

 * 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] #28636 [Core Tor/Tor]: Address WTF-PAD comments by Nick (2018-11-27 over IRC)

[Tor Bug Tracker & Wiki]

#28636: Address WTF-PAD comments by Nick (2018-11-27 over IRC)
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.0.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad, tor-relay, tor-cell,|  Actual Points:
  padding, 041-proposed, network-team-   |
  roadmap-2019-Q1Q2  |
Parent ID:  #28632   | Points:  3
 Reviewer:  nickm|Sponsor:
 |  Sponsor2
-+-
Changes (by asn):

 * status:  needs_revision => needs_review


Comment:

 Replying to [comment:25 teor]:
 > Here are things that need revision:
 > * Please fill in the actual points on this ticket.
 > * This is a bug on code that was released in 0.4.0.1-alpha, so it needs
 a changes file.
 >   * Was any of this code released earlier than 0.4.0.1-alpha?
 > * I did a review, I found at least one potential bug, and one typo:
 >   * https://github.com/torproject/tor/pull/819
 > * I don't know enough to know if this code needs spec changes:
 >   * The only functional change I can see is padding is disabled in
 dormant mode.
 >

 Great catches. Thanks!

 Pushed a commit 9fcea183d1 that should satisfy all the above. Let me know
 if you don't like 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] #29503 [Webpages/Website]: Add logo to link preview on new site

[Tor Bug Tracker & Wiki]

#29503: Add logo to link preview on new site
--+--
 Reporter:  steph |  Owner:  steph
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+--

Comment (by steph):

 Replying to [comment:1 emmapeel]:
 > i don't see the images anymore. steph could you upload them again? Maybe
 here?
 Attached some options to be used at antonela's discretion

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

Re: [tor-bugs] #29503 [Webpages/Website]: Add logo to link preview on new site

[Tor Bug Tracker & Wiki]

#29503: Add logo to link preview on new site
--+--
 Reporter:  steph |  Owner:  steph
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+--
Changes (by steph):

 * Attachment "tor-project-logo-onions.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] #29503 [Webpages/Website]: Add logo to link preview on new site

[Tor Bug Tracker & Wiki]

#29503: Add logo to link preview on new site
--+--
 Reporter:  steph |  Owner:  steph
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+--
Changes (by steph):

 * Attachment "tor-project-logo-2400.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] #29693 [Core Tor/Tor]: Decrease probability of stochastic failures in test-slow

[Tor Bug Tracker & Wiki]

#29693: Decrease probability of stochastic failures in test-slow
-+-
 Reporter:  teor |  Owner:  asn
 Type:  defect   | Status:
 |  merge_ready
 Priority:  High |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.0.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  nickm-merge, tor-ci, tor-test,   |  Actual Points:  0.5
  040-must, 040-backport |
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
 |  Sponsor2-must
-+-

Comment (by asn):

 Yes, let's! Nick please merge bug29693_040_radical AKA
 https://github.com/torproject/tor/pull/824.

 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] #29503 [Webpages/Website]: Add logo to link preview on new site

[Tor Bug Tracker & Wiki]

#29503: Add logo to link preview on new site
--+--
 Reporter:  steph |  Owner:  steph
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+--
Changes (by emmapeel):

 * owner:  hiro => steph
 * status:  new => assigned
 * parent:   => #25640


Comment:

 i don't see the images anymore. steph could you upload them again? Maybe
 here?

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

Re: [tor-bugs] #29516 [Webpages/Website]: On about/jobs, the 'Join us on IRC' link doesn't go anywhere

[Tor Bug Tracker & Wiki]

#29516: On about/jobs, the 'Join us on IRC' link doesn't go anywhere
--+--
 Reporter:  alsmith   |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+--
Changes (by emmapeel):

 * parent:   => #25640


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

Re: [tor-bugs] #29845 [Webpages/Website]: Add Tor Browser for Android x86 download links

[Tor Bug Tracker & Wiki]

#29845: Add Tor Browser for Android x86 download links
--+--
 Reporter:  boklm |  Owner:  hiro
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+--
Changes (by emmapeel):

 * parent:   => #25640


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

Re: [tor-bugs] #29608 [Webpages/Website]: Sponsors Page Update

[Tor Bug Tracker & Wiki]

#29608: Sponsors Page Update
--+--
 Reporter:  bekeela   |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25640| Points:
 Reviewer:|Sponsor:
--+--
Changes (by emmapeel):

 * parent:   => #25640


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