Re: [tor-bugs] #31538 [Applications/Tor Browser]: Windows bundles based on ESR 68 are not built reproducibly

2019-09-11 Thread Tor Bug Tracker & Wiki
#31538: Windows bundles based on ESR 68 are not built reproducibly
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  tbb-rbm, ff68-esr, tbb-9.0-must- |  Actual Points:
  alpha, TorBrowserTeam201909,   |
  GeorgKoppen201909  |
Parent ID:  #30322   | Points:  2
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 Replying to [comment:19 gk]:
 > However, other object files are still included non-deterministically
 after that part. I am not sure yet where they are coming from...

 Okay, I think I am at the bottom of that rabbit hole. Thre reason for that
 issue is that `libc++.a` is getting merged with the contents of
 `libc++abi.a` (which, by the way, itself is reproducible at least after
 switching to CMake's 3.5.13). Now, that merging gets done in libc++'s
 `merge_archives.py` (https://github.com/llvm/llvm-
 project/blob/release/8.x/libcxx/utils/merge_archives.py). The problem here
 is:
 {{{
 files = glob.glob(os.path.join(temp_directory_root, '*.o*'))
 }}}
 From the doc (https://docs.python.org/2/library/glob.html):
 {{{
 "The glob module finds all the pathnames matching a specified pattern
 according to the rules used by the Unix shell, although results are
 returned in arbitrary order."
 }}}
 So, doing a simple
 {{{
 files = sorted(glob.glob(os.path.join(temp_directory_root, '*.o*')))
 }}}
 gets us finally a reproducible `libc++.a` and a reproducible 64-bit .exe.
 I am currently testing the 32-bit version as well and will prepare a
 proper patch for review 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] #31111 [Core Tor/Tor]: negotiate one machine per index

2019-09-11 Thread Tor Bug Tracker & Wiki
#3: negotiate one machine per index
--+
 Reporter:  pulls |  Owner:  (none)
 Type:  defect| Status:
  |  merge_ready
 Priority:  Medium|  Milestone:  Tor:
  |  0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor:
  |  0.4.1.3-alpha
 Severity:  Normal| Resolution:
 Keywords:  wtf-pad circpad-researchers-want  |  Actual Points:
Parent ID:| Points:
 Reviewer:  mikeperry |Sponsor:
--+
Changes (by mikeperry):

 * keywords:  wtf-pad => wtf-pad circpad-researchers-want
 * status:  needs_information => merge_ready


Comment:

 This looks good to go to me then.

 Note: This does not affect the padding machines we deployed on the live
 network. This bug does not need backport, nor is it urgent. But it is a
 bug that researchers will encounter during development, so we should merge
 the fix 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] #30743 [Core Tor/Tor]: Write a coccinelle script to catch increment/decrement calls inside log_debug().

2019-09-11 Thread Tor Bug Tracker & Wiki
#30743: Write a coccinelle script to catch increment/decrement calls inside
log_debug().
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  assigned => needs_review


Comment:

 See branch `ticket30743` with PR at
 https://github.com/torproject/tor/pull/1322 .  Running it over the source
 code with the apply.sh script in #31705 found no additional instances of
 bugs like #30628.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31703 [Webpages/Website]: Downloading Tor Browser from 2620:0:6b0:b:225:dada:19:1 is painfully slow

2019-09-11 Thread Tor Bug Tracker & Wiki
#31703: Downloading Tor Browser from 2620:0:6b0:b:225:dada:19:1 is painfully 
slow
--+--
 Reporter:  pospeselr |  Owner:  anarcat
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Chat

 {{{
 (2019-09-11 12:44:26 PM) pospeselr: this one i think:
 2620:0:6b0:b:225:dada:19:1
 (2019-09-11 12:47:30 PM) pospeselr: though if i wget it it does come down
 a bit faster
 (2019-09-11 12:47:53 PM) arma1: that address is a team cymru address
 (2019-09-11 12:48:03 PM) arma1: i wonder if its magic black box ddos
 defense thinks you're a bad person
 (2019-09-11 12:48:21 PM) pospeselr: well i mean i am obviously, but i
 would still like to dl tor browser quickly >:[
 (2019-09-11 12:48:52 PM) pospeselr: and i take it back, the wget dl is
 slowly slowing down, 80 kb/s now
 (2019-09-11 12:49:23 PM) arma1: anarcat: ^ you any good at these topics?
 :)
 (2019-09-11 12:49:43 PM) anarcat: arma1: i'm in a meeting, but i'll be
 here in 10min
 (2019-09-11 12:49:47 PM) anarcat: arma1: what's the TL;DR
 (2019-09-11 12:49:59 PM) pospeselr: server slow plz make fast
 (2019-09-11 12:50:03 PM) arma1: one of the dist.tpo is being slow for
 pospeselr
 (2019-09-11 12:50:14 PM) arma1: not critical
 (2019-09-11 12:50:18 PM) anarcat: one of, which?
 (2019-09-11 12:50:37 PM) anarcat: how to reproduce?
 (2019-09-11 12:50:38 PM) arma1: dist.torproject.org aka
 2620:0:6b0:b:225:dada:19:1
 (2019-09-11 12:50:51 PM) anarcat: Host
 1.0.0.0.9.1.0.0.a.d.a.d.5.2.2.0.b.0.0.0.0.b.6.0.0.0.0.0.0.2.6.2.ip6.arpa
 not found: 3(NXDOMAIN)
 (2019-09-11 12:50:53 PM) anarcat: great
 (2019-09-11 12:51:21 PM) anarcat: that's at cymru
 (2019-09-11 12:52:25 PM) anarcat: it's web-cymru-01.torproject.org
 specifically
 (2019-09-11 12:52:34 PM) anarcat: which file should i try to get?
 (2019-09-11 12:53:03 PM) anarcat: ( i found the server through a search in
 ldap)
 (2019-09-11 12:53:54 PM) pospeselr:
 https://dist.torproject.org/torbrowser/8.5.5/tor-browser-linux64-8.5.5_en-
 US.tar.xz
 (2019-09-11 12:54:36 PM) anarcat: Connecting to dist.torproject.org
 (dist.torproject.org)|2620:0:6b0:b:225:dada:19:1|:443... failed: Network
 is unreachable.
 (2019-09-11 12:54:37 PM) anarcat: duh
 (2019-09-11 12:55:18 PM) anarcat: i'm getting 130KB/s there now
 (2019-09-11 12:55:30 PM) pospeselr: yeah exactly
 (2019-09-11 12:55:41 PM) pospeselr: and it'll slow down to tourghly 50
 kb/s shortly
 (2019-09-11 12:56:33 PM) anarcat: yeah, there might be saturation there
 (2019-09-11 12:56:39 PM) anarcat: i'll take a look at the host (moly)
 (2019-09-11 12:58:26 PM) anarcat: network's saturated on moly
 (2019-09-11 12:58:28 PM) anarcat: 12MB/s
 (2019-09-11 12:58:32 PM) anarcat: mbps
 (2019-09-11 1:01:38 PM) arma1: anarcat: in the past, sometimes, cymru ran
 black box ddos resistance doohickeys on their network, and we discovered
 them (and bugs in them) by seeing anomalies like this
 (2019-09-11 1:09:41 PM) anarcat: well it sure seems like the cymru web
 mirror is capped to 100mbps
 }}}

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

Re: [tor-bugs] #31703 [Internal Services/Service - dist]: Downloading Tor Browser from 2620:0:6b0:b:225:dada:19:1 is painfully slow

2019-09-11 Thread Tor Bug Tracker & Wiki
#31703: Downloading Tor Browser from 2620:0:6b0:b:225:dada:19:1 is painfully 
slow
--+--
 Reporter:  pospeselr |  Owner:  anarcat
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - dist  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by ggus):

 * cc: ggus (removed)
 * component:  Webpages/Website => Internal Services/Service - dist


Comment:

 Moving to Internal Services/Service - dist.

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

Re: [tor-bugs] #28533 [Circumvention/BridgeDB]: bridgesdb: replace the message to mail support with a link to the documentation

2019-09-11 Thread Tor Bug Tracker & Wiki
#28533: bridgesdb: replace the message to mail support with a link to the
documentation
+---
 Reporter:  emmapeel|  Owner:  phw
 Type:  defect  | Status:  closed
 Priority:  High|  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  ex-sponsor-19   |  Actual Points:  0.2
Parent ID:  | Points:  1
 Reviewer:  cohosh  |Sponsor:  Sponsor30-can
+---
Changes (by phw):

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


Comment:

 Thanks, everyone. I merged and deployed the patch.

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

[tor-bugs] #31702 [Applications/Tor Browser]: Backport patch for bug 1578075 for macOS Catalina

2019-09-11 Thread Tor Bug Tracker & Wiki
#31702: Backport patch for bug 1578075 for macOS Catalina
--+
 Reporter:  gk|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
  |  TorBrowserTeam201909
Actual Points:|  Parent ID:
   Points:  0.25  |   Reviewer:
  Sponsor:|
--+
 We are almost ready to ship macOS bundles compatible with Catalina.
 However, we need to backport at least the patch for
 https://bugzilla.mozilla.org/show_bug.cgi?id=1578075 as Mozilla does not
 seem to be making another esr60 release.

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

Re: [tor-bugs] #30870 [Applications/Orbot]: Default obfs4 bridges are all offline

2019-09-11 Thread Tor Bug Tracker & Wiki
#30870: Default obfs4 bridges are all offline
+--
 Reporter:  phw |  Owner:  n8fr8
 Type:  defect  | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Applications/Orbot  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-bridges |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by arma):

 Replying to [ticket:30870 phw]:
 > but in the short run we should make sure that these bridges are kept in
 sync with our default bridges

 Btw, the original idea here was that Orbot intentionally shipped with a
 different list of default bridges than Tor Browser, because then whichever
 one attracted more censor attention wouldn't automatically undermine the
 other.

 Though if Orbot isn't maintaining its chosen bridges, that original idea
 isn't so smart anymore. :)

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

Re: [tor-bugs] #30857 [Internal Services/Services Admin Team]: migrate (some projects? everything?) from trac to gitlab

2019-09-11 Thread Tor Bug Tracker & Wiki
#30857: migrate (some projects? everything?) from trac to gitlab
-+-
 Reporter:  anarcat  |  Owner:  (none)
 Type:  project  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Services Admin |Version:
  Team   |
 Severity:  Normal   | Resolution:
 Keywords:  tickets-migration|  Actual Points:
Parent ID:  #29400   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gaba):

 Yes. I understand the problem you are describing and the solution you
 have. And I'm not sure how we are going to have something usable in gitlab
 with all the issues in one project (legacy in your example).

 We could have all trac issues in a 'legacy project' and then any new issue
 in its own project (the structure that we proposed in the gitlab migration
 document). But still will make it hard to manage issues that way.

 Right now we have (as a way to test) a project Scalability
 (https://dip.torproject.org/torproject/scalability) that is at the base of
 the Tor project group and is shared with other groups (like metrics and
 core). Still we can not add issues from scalability to the metrics and
 core kanban boards...

 I understand the problem but I do not think the legacy project is a
 solution that works for us.

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

Re: [tor-bugs] #31626 [Core Tor/Tor]: Move confparse.[ch] into lib/confmgt

2019-09-11 Thread Tor Bug Tracker & Wiki
#31626: Move confparse.[ch] into lib/confmgt
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  042-should|  Actual Points:  .1
Parent ID:  #29211| Points:  0
 Reviewer:  teor  |Sponsor:  Sponsor31-can
--+
Changes (by nickm):

 * status:  assigned => needs_review
 * reviewer:   => teor
 * actualpoints:   => .1


Comment:

 CI has passed.

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

Re: [tor-bugs] #30126 [Applications/Tor Browser]: Make Tor Browser on macOS compatible with Apple's notarization

2019-09-11 Thread Tor Bug Tracker & Wiki
#30126: Make Tor Browser on macOS compatible with Apple's notarization
+--
 Reporter:  gk  |  Owner:  tbb-team
 Type:  task| Status:  closed
 Priority:  Very High   |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  tbb-security, TorBrowserTeam201909  |  Actual Points:  2.5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:
+--
Changes (by gk):

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


Comment:

 \o/ It seems we are done here. I opened #31702 for backporting the crash
 bug fix and then we should roll out updates asap I think, ideally starting
 with our alpha series.

 mcs/brade please add to the points actually spent. I am just adding mine.

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

Re: [tor-bugs] #31703 [Webpages/Website]: Downloading Tor Browser from 2620:0:6b0:b:225:dada:19:1 is painfully slow

2019-09-11 Thread Tor Bug Tracker & Wiki
#31703: Downloading Tor Browser from 2620:0:6b0:b:225:dada:19:1 is painfully 
slow
--+--
 Reporter:  pospeselr |  Owner:  anarcat
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by anarcat):

 battle plan:

  1. i poked cymru about upgrading to gbps. weasel memory tells us we used
 to be but we have been downgraded over 6 months ago at least (according to
 backups)
  2. if cymru fails or times out (7 days?), we setup another mirror (or
 varnish cache) elsewhere (fsn cluster?)

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

Re: [tor-bugs] #31407 [Circumvention/Snowflake]: Create a broker spec for metrics collection

2019-09-11 Thread Tor Bug Tracker & Wiki
#31407: Create a broker spec for metrics collection
-+-
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  enhancement  | Status:  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec |  Actual Points:
Parent ID:   | Points:
 Reviewer:  phw  |Sponsor:
-+-
Changes (by phw):

 * status:  needs_review => merge_ready


Comment:

 Looks good to me.

 Small suggestion: revisions are easier to review if we address them in
 separate follow-up patches. Once everything looks good, we can squash the
 revision patches and end up with a single, well-formatted commit. Without
 separate revision patches, it's a bit tricky to see what changed between
 revisions.

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

Re: [tor-bugs] #29945 [Webpages/Website]: fiscal documents page has missing docs, typos, and wrong labels

2019-09-11 Thread Tor Bug Tracker & Wiki
#29945: fiscal documents page has missing docs, typos, and wrong labels
--+--
 Reporter:  arma  |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #29901| Points:
 Reviewer:|Sponsor:
--+--

Comment (by ggus):

 Contacted Beekela, and her suggestions are:

 a) 2016-12-05 Tor Project Bylaws - move to top under "Founding Documents"
 section

 b) 2012 Financial Statements - AUDIT

 c) 2011 State of MA Form PC - AUDIT

 d) 2010 IRS Form 990, State of MA Form PC, and Independent Audit Results -
 AUDIT, IRS 990

 e) 2009 Dept of Commerce Data Collection Form - FISCAL YEAR

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

Re: [tor-bugs] #31653 [Core Tor/Tor]: padding machine sending padding from relay to client closes circuit

2019-09-11 Thread Tor Bug Tracker & Wiki
#31653: padding machine sending padding from relay to client closes circuit
--+
 Reporter:  pulls |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor:
  |  0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor:
  |  0.4.1.5
 Severity:  Normal| Resolution:
 Keywords:  wtf-pad circpad-researchers-want  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by mikeperry):

 * keywords:  wtf-pad circpad => wtf-pad circpad-researchers-want


Comment:

 The #29494 implementation will change this codepath. It is reasonable for
 now to merge a workaround that just sets in_usec = 0 to ensure correct
 behavior for 0 delay in the meantime.

 There is roughly a 2/1000 chance of this happening during client rend
 circuit creation in production in 0.4.1.x (because the left edge of the
 histogram for that circuit type is 0ms and the right edge is 1000, and we
 roll the dice once on the client side and once on the relay side).

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

Re: [tor-bugs] #26294 [Core Tor/Tor]: attacker can force intro point rotation by ddos

2019-09-11 Thread Tor Bug Tracker & Wiki
#26294: attacker can force intro point rotation by ddos
-+-
 Reporter:  arma |  Owner:  asn
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, tor-dos, network-team-   |  Actual Points:  6
  roadmap-august, security, 042-should   |
Parent ID:  #2   | Points:  7
 Reviewer:  dgoulet  |Sponsor:
 |  Sponsor27-must
-+-

Comment (by s7r):

 The attacks are quite possible, but also the current replay cache behavior
 can be trivailly gamed so the onion service will rotate intro points more
 often than we would normally want and thus trigger a different sybil type
 attack where eventually the onion service pick a hostile introduction
 point. Both time limit and number of introductions limit are important and
 mitigate different thread models.

 Which is why I think configuring the replay cache to limit on a "hybrid"
 threshold (time + introductions) as described in comment:11 will not
 interfere with the issues and concerns described above. It's just about
 choosing the right variable min and max values so that introduction points
 are not rotated too fast but also cannot send unlimited replays
 (introductions) during their time-based lifetime. A "hybrid" limitation as
 described will simply enhance the current behavior instead of radically
 changing 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] #31703 [Internal Services/Service - dist]: Downloading Tor Browser from 2620:0:6b0:b:225:dada:19:1 is painfully slow

2019-09-11 Thread Tor Bug Tracker & Wiki
#31703: Downloading Tor Browser from 2620:0:6b0:b:225:dada:19:1 is painfully 
slow
--+--
 Reporter:  pospeselr |  Owner:  anarcat
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - dist  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by anarcat):

 rejected options:

  * redirect traffic to sunet (got cold feet after last DDOS) or savii (not
 all the files)
  * just pull cymru out of rotation altogether (could overload existing
 mirrors and kill other mirrors)

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

Re: [tor-bugs] #30870 [Applications/Orbot]: Default obfs4 bridges are all offline

2019-09-11 Thread Tor Bug Tracker & Wiki
#30870: Default obfs4 bridges are all offline
+---
 Reporter:  phw |  Owner:  n8fr8
 Type:  defect  | Status:  needs_information
 Priority:  Medium  |  Milestone:
Component:  Applications/Orbot  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-bridges |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---
Changes (by phw):

 * status:  needs_review => needs_information


Comment:

 Setting this to "needs_information" to see what orbot's strategy here is.
 I will remove the fix I pushed earlier because it's already outdated
 again. For what it's worth, our list of default bridges is available here:
 https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/DefaultBridges

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

Re: [tor-bugs] #31637 [Core Tor/Tor]: Make sure we have test coverage for Option, +Option and /Option across defaults, torrc, command line

2019-09-11 Thread Tor Bug Tracker & Wiki
#31637: Make sure we have test coverage for Option, +Option and /Option across
defaults, torrc, command line
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-august  |  Actual Points:
Parent ID:  #29211   | Points:
 Reviewer:  teor |Sponsor:
-+-

Comment (by nickm):

 Okay, I've got something that works.  See notes above: It's not ready to
 merge, but I'd like to know how the approach looks to you.

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

Re: [tor-bugs] #31637 [Core Tor/Tor]: Make sure we have test coverage for Option, +Option and /Option across defaults, torrc, command line

2019-09-11 Thread Tor Bug Tracker & Wiki
#31637: Make sure we have test coverage for Option, +Option and /Option across
defaults, torrc, command line
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-august  |  Actual Points:
Parent ID:  #29211   | Points:
 Reviewer:  teor |Sponsor:
-+-
Changes (by nickm):

 * status:  assigned => 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] #30857 [Internal Services/Services Admin Team]: migrate (some projects? everything?) from trac to gitlab

2019-09-11 Thread Tor Bug Tracker & Wiki
#30857: migrate (some projects? everything?) from trac to gitlab
-+-
 Reporter:  anarcat  |  Owner:  (none)
 Type:  project  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Services Admin |Version:
  Team   |
 Severity:  Normal   | Resolution:
 Keywords:  tickets-migration|  Actual Points:
Parent ID:  #29400   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 >  Yes. I understand the problem you are describing and the solution you
 have. And I'm not sure how we are going to have something usable in gitlab
 with all the issues in one project (legacy in your example).
 >
 >  We could have all trac issues in a 'legacy project' and then any new
 issue in its own project (the structure that we proposed in the gitlab
 migration document). But still will make it hard to manage issues that
 way.

 You're absolutely right: it would be awful to have all tickets in the same
 project in GitLab.

 That's not what I'm proposing here.

 What I am proposing is that we '''import''' all tickets in the same
 ''legacy'' project '''BUT''' we then '''move''' each ticket to the right
 project outside of ''legacy''.

 The goal of importing everything in the same project is to make
 redirections workable. Without this, we have to guess, on the redirection
 side, which project the ticket ended up in. This could be quite difficult
 to implement and will lead a complex redirection system. We're lucky
 enough to have a "flat" numbering space for the ticket numbers in Trac
 (there's only one list of tickets), so it would be great to have the same
 thing on GitLab's side.

 By importing all tickets in the same project and then moving them, we
 accomplish this: the redirector can point to the legacy project, which in
 turn will point to the right project the issue has been moved to. I think
 it's a win-win...

 >  I understand the problem but I do not think the legacy project is a
 solution that works for us.

 ... but I'm ready to accept that as well. It's the best solution I can
 think of but I'd be happy to hear about possible alternatives. The only
 one I can think of is to have an explicit list of ticket N ->
 GITLAB_PROJECT_NAME/Y with ~40,000 entries, and I think that would be a
 pain in the ass to create and carry around forever. :)

 In summary, I agree with you that having all tickets in the same project
 is not workable, and that's not what I'm suggesting.

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

Re: [tor-bugs] #31637 [Core Tor/Tor]: Make sure we have test coverage for Option, +Option and /Option across defaults, torrc, command line

2019-09-11 Thread Tor Bug Tracker & Wiki
#31637: Make sure we have test coverage for Option, +Option and /Option across
defaults, torrc, command line
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-august  |  Actual Points:
Parent ID:  #29211   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 I've started a shell script that will be useful for this, and maybe also
 for parts of #31631.

 It isn't done yet!  I've only written the script and a few example tests
 for it -- I need to write a bunch more tests before I can call this done,
 and also I need to write a changes file.  But before I more ahead, I'd
 like to know what you think of this approach.  No need to do a full review
 now: I just want to know whether you think I should proceed with this line
 of work.

 The branch is `ticket31637_wip`. PR at
 https://github.com/torproject/tor/pull/1320 .

 (WRT #31631: It tests configuration round-trips, but not state or
 sr_disk_state.)

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

Re: [tor-bugs] #31637 [Core Tor/Tor]: Make sure we have test coverage for Option, +Option and /Option across defaults, torrc, command line

2019-09-11 Thread Tor Bug Tracker & Wiki
#31637: Make sure we have test coverage for Option, +Option and /Option across
defaults, torrc, command line
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-august  |  Actual Points:
Parent ID:  #29211   | Points:
 Reviewer:  teor |Sponsor:
-+-

Comment (by nickm):

 (I'm currently wrestling with appveyor to try work around CRLF issues.
 Any advice here would be welcome)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31704 [Applications]: help

2019-09-11 Thread Tor Bug Tracker & Wiki
#31704: help
---+--
 Reporter:  kain3e |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Very High  |  Component:  Applications
  Version: |   Severity:  Normal
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
 Every time I open tor it wont open it says to restart tor when i do it
 never works when i press copy to clipboard 0 comes up even if its just to
 delete the orginal tor file i cant find 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] #31704 [Applications]: help

2019-09-11 Thread Tor Bug Tracker & Wiki
#31704: help
--+
 Reporter:  kain3e|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Very High |  Milestone:
Component:  Applications  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by arma):

 Looks like another instance of #31506.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31705 [Core Tor/Tor]: Add sufficient coccinelle tooling to run coccinelle without stress

2019-09-11 Thread Tor Bug Tracker & Wiki
#31705: Add sufficient coccinelle tooling to run coccinelle without stress
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  task   | Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor:  Sponsor31-can  |
---+
 I think we need two pieces of coccinelle tooling to be able to use it
 effectively:

 1) A script that tells us which files have parsing problems.

 2) A script to invoke spatch with the right arguments.

 Based on 1 and 2, we can improve our tor-coccinelle.h file to handle more
 of our codebase, and we can apply coccinelle scripts without trying to
 remember the name of the "-macro-file-builtins" flag.

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

Re: [tor-bugs] #30203 [Webpages/Website]: The "Download Tor Source Code" page is mixing source code and win32 binaries

2019-09-11 Thread Tor Bug Tracker & Wiki
#30203: The "Download Tor Source Code" page is mixing source code and win32
binaries
--+--
 Reporter:  boklm |  Owner:  antonela
 Type:  defect| Status:  assigned
 Priority:  High  |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #29901| Points:
 Reviewer:|Sponsor:
--+--

Comment (by antonela):

 Replying to [comment:7 gk]:
 > Replying to [comment:6 hiro]:
 > > I think this could be a good solution: https://share.riseup.net
 /#sqydaqO5OYR-72FeHfhbGw
 >
 > But it is still mixing source code with binaries while saying "Download
 Tor Source Code". Maybe we could label the while thing "Alternative
 Downloads" or something, indicating that we offer here a bunch of
 different (albeit related) things?

 True. We are still mixing source code with binaries and is something that
 we want to fix once the developers portal is in place.

 Now, I see Tor source code as a more critical downloadable than windows
 expert bundles. That is why we have "Download Tor source code" in our
 current /download page.

 If you still see it as a problem, I'm happy to rename this link with
 something like "Alternative Downloads" as arma/you suggested if that
 reflects better what it is inside.

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

Re: [tor-bugs] #30126 [Applications/Tor Browser]: Make Tor Browser on macOS compatible with Apple's notarization

2019-09-11 Thread Tor Bug Tracker & Wiki
#30126: Make Tor Browser on macOS compatible with Apple's notarization
+--
 Reporter:  gk  |  Owner:  tbb-team
 Type:  task| Status:  reopened
 Priority:  Very High   |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-security, TorBrowserTeam201909  |  Actual Points:  2.5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:
+--
Changes (by gk):

 * status:  closed => reopened
 * 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] #31465 [Applications/Tor Browser]: Adapt tor-browser-build projects for macOS notarization

2019-09-11 Thread Tor Bug Tracker & Wiki
#31465: Adapt tor-browser-build projects for macOS notarization
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-security, tbb-rbm,   |  Actual Points:
  TorBrowserTeam201908R, GeorgKoppen201908   |
Parent ID:  #30126   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:
 tbb-security, tbb-rbm, TorBrowserTeam201908R, GeorgKoppen201908, tbb-
 backport
 => tbb-security, tbb-rbm, TorBrowserTeam201908R, GeorgKoppen201908


Comment:

 Apple seems to have relaxed the notarization requirements so that we don't
 need that backport anymore for our hopefully last esr60-based browser
 release.

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

Re: [tor-bugs] #30126 [Applications/Tor Browser]: Make Tor Browser on macOS compatible with Apple's notarization

2019-09-11 Thread Tor Bug Tracker & Wiki
#30126: Make Tor Browser on macOS compatible with Apple's notarization
+--
 Reporter:  gk  |  Owner:  tbb-team
 Type:  task| Status:  closed
 Priority:  Very High   |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  tbb-security, TorBrowserTeam201909  |  Actual Points:  2.5
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:
+--
Changes (by gk):

 * status:  reopened => 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] #31637 [Core Tor/Tor]: Make sure we have test coverage for Option, +Option and /Option across defaults, torrc, command line

2019-09-11 Thread Tor Bug Tracker & Wiki
#31637: Make sure we have test coverage for Option, +Option and /Option across
defaults, torrc, command line
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-august  |  Actual Points:
Parent ID:  #29211   | Points:
 Reviewer:  teor |Sponsor:
-+-
Changes (by nickm):

 * 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] #31603 [Internal Services/Service - github tpo]: GitHub close Support, tpo, community issues

2019-09-11 Thread Tor Bug Tracker & Wiki
#31603: GitHub close Support, tpo, community issues
+--
 Reporter:  ggus|  Owner:  hiro
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Internal Services/Service - github tpo  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by antonela):

 I don't have credentials to do it, but here is the way to disable issues
 in Github's repositories

 https://help.github.com/en/articles/disabling-issues

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

Re: [tor-bugs] #31407 [Circumvention/Snowflake]: Create a broker spec for metrics collection

2019-09-11 Thread Tor Bug Tracker & Wiki
#31407: Create a broker spec for metrics collection
-+--
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec |  Actual Points:
Parent ID:   | Points:
 Reviewer:  phw  |Sponsor:
-+--
Changes (by cohosh):

 * status:  needs_revision => needs_review


Comment:

 Made suggested fixes:
 
https://github.com/cohosh/snowflake/commit/2bf398af39bda0d2fa684f9d0571e9ea727e1ef9

 I also renamed the folder to `doc` to match obfs4.

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

Re: [tor-bugs] #31464 [Applications/Tor Browser]: meek and moat are broken on macOS 10.9 with the switch to Go 1.12

2019-09-11 Thread Tor Bug Tracker & Wiki
#31464: meek and moat are broken on macOS 10.9 with the switch to Go 1.12
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  tbb-rbm, meek |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

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


Comment:

 Replying to [comment:3 mcs]:
 > Replying to [comment:2 dcf]:
 > > I suppose this is a problem not only with the meek from meek.git, but
 also when using meek_lite with obfs4proxy (#29430)? Or does obfs4proxy
 somehow avoid using the problematic `_unlinkat` symbol? If the latter is
 the case, then #29430 would seem to solve it.
 >
 > In fact, obfs4proxy seems to avoid this problem. See 30126#comment:56
 >
 > > According to https://github.com/golang/go/wiki/Darwin, OS X 10.9 is
 not supported past Go 1.10.8.
 >
 > I guess we should try to support macOS 10.9.x as long as we can, but it
 may be a losing battle. And even though Mozilla still supports it for
 Firefox, we should not recommend it since 10.9 only rarely receives
 security updates from Apple.
 >
 > Georg, should we close this ticket since this issue seems to be resolved
 with Tor Browser 9.0a6 (after the switch to meek_lite)?

 Yes.

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

Re: [tor-bugs] #31660 [Applications/Tor Browser]: Revise onboarding to take new Firefox experience into account

2019-09-11 Thread Tor Bug Tracker & Wiki
#31660: Revise onboarding to take new Firefox experience into account
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 Replying to [comment:1 antonela]:
 > Thanks for the heads up, gk. Do you have any documentation link I could
 explore regarding any Firefox onboarding in ESR68? I failed when I tried
 to find it.

 I have not looked closely to be honest. It's part of the activity stream
 now, https://bugzilla.mozilla.org/show_bug.cgi?id=1457565 being the meta
 bug. Clicking a bit around I found

 https://trello.com/c/gRkk9mI2/188-i-want-a-simple-onboarding-tour-to-run-
 at-the-first-run-of-the-first-new-tab-page

 but we should probably dig up more 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] #29494 [Core Tor/Tor]: Optimize interaction between circuitmux and circuitpadding

2019-09-11 Thread Tor Bug Tracker & Wiki
#29494: Optimize interaction between circuitmux and circuitpadding
--+
 Reporter:  mikeperry |  Owner:  mikeperry
 Type:  enhancement   | Status:
  |  needs_revision
 Priority:  High  |  Milestone:  Tor:
  |  unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  wtf-pad circpad-researchers-want  |  Actual Points:
Parent ID:| Points:  5
 Reviewer:|Sponsor:  Sponsor2
--+
Changes (by mikeperry):

 * keywords:  wtf-pad, network-team-roadmap-2019-Q1Q2 042-proposed => wtf-
 pad circpad-researchers-want


Comment:

 I think the odds are high that this will be important for research
 results. Tagging it to denote 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] #31705 [Core Tor/Tor]: Add sufficient coccinelle tooling to run coccinelle without stress

2019-09-11 Thread Tor Bug Tracker & Wiki
#31705: Add sufficient coccinelle tooling to run coccinelle without stress
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  task  | Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor31-can
--+

Comment (by nickm):

 See branch `ticket31705` with PR at
 https://github.com/torproject/tor/pull/1321

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

Re: [tor-bugs] #30743 [Core Tor/Tor]: Write a coccinelle script to catch increment/decrement calls inside log_debug().

2019-09-11 Thread Tor Bug Tracker & Wiki
#30743: Write a coccinelle script to catch increment/decrement calls inside
log_debug().
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by nickm):

 Pfew, this has gotten complicated.  I've opened another ticket to improve
 our coccinelle tooling: #31705.

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

Re: [tor-bugs] #31111 [Core Tor/Tor]: Properly support two padding machines per circuit (was: negotiate one machine per index)

2019-09-11 Thread Tor Bug Tracker & Wiki
#3: Properly support two padding machines per circuit
--+
 Reporter:  pulls |  Owner:  (none)
 Type:  defect| Status:
  |  merge_ready
 Priority:  Medium|  Milestone:  Tor:
  |  0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor:
  |  0.4.1.3-alpha
 Severity:  Normal| Resolution:
 Keywords:  wtf-pad circpad-researchers-want  |  Actual Points:
Parent ID:| Points:
 Reviewer:  mikeperry |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] #31653 [Core Tor/Tor]: Padding cells sent with 0ms delay cause circuit failures (was: padding machine sending padding from relay to client closes circuit)

2019-09-11 Thread Tor Bug Tracker & Wiki
#31653: Padding cells sent with 0ms delay cause circuit failures
--+
 Reporter:  pulls |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor:
  |  0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor:
  |  0.4.1.5
 Severity:  Normal| Resolution:
 Keywords:  wtf-pad circpad-researchers-want  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

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

[tor-bugs] #31711 [- Select a component]: Spread the word about the Digital Climate Strike on Tor's social media

2019-09-11 Thread Tor Bug Tracker & Wiki
#31711: Spread the word about the Digital Climate Strike on Tor's social media
--+--
 Reporter:  teor  |  Owner:  steph
 Type:  task  | Status:  assigned
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:  #31708
   Points:|   Reviewer:
  Sponsor:|
--+--
 Here's an example post:
 https://mobile.twitter.com/SeventhGen/status/1169227616236253186

 And here are some sample graphics and text:
 https://digital.globalclimatestrike.net/#social-downloads

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

Re: [tor-bugs] #26742 [Internal Services/Service - trac]: Where did the search bar on trac go? What did the 力 say?

2019-09-11 Thread Tor Bug Tracker & Wiki
#26742: Where did the search bar on trac go? What did the 力 say?
--+--
 Reporter:  cypherpunks   |  Owner:  qbi
 Type:  defect| Status:  reopened
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by cypherpunks):

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


Comment:

 OP means it's absent w/o login.

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

Re: [tor-bugs] #30870 [Applications/Orbot]: Default obfs4 bridges are all offline

2019-09-11 Thread Tor Bug Tracker & Wiki
#30870: Default obfs4 bridges are all offline
+---
 Reporter:  phw |  Owner:  n8fr8
 Type:  defect  | Status:  needs_information
 Priority:  Medium  |  Milestone:
Component:  Applications/Orbot  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-bridges |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---

Comment (by n8fr8):

 Why is it so hard to keep good obfs4 bridges online? It is frustrating
 that we have to keep changing these.

 I am not even talking about "unblocked in China", I just mean reliably
 running. What is the expected life time of an obfs4 bridge?

 We don't run our own bridges, but it may be time for us to do 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] #31111 [Core Tor/Tor]: Properly support two padding machines per circuit

2019-09-11 Thread Tor Bug Tracker & Wiki
#3: Properly support two padding machines per circuit
--+
 Reporter:  pulls |  Owner:  (none)
 Type:  defect| Status:
  |  merge_ready
 Priority:  Medium|  Milestone:  Tor:
  |  0.4.3.x-final
Component:  Core Tor/Tor  |Version:  Tor:
  |  0.4.1.3-alpha
 Severity:  Normal| Resolution:
 Keywords:  wtf-pad circpad-researchers-want  |  Actual Points:
Parent ID:| Points:
 Reviewer:  mikeperry |Sponsor:
--+
Changes (by teor):

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


Comment:

 Hi Mike,

 Do you want this fix merged into 0.4.2 or 0.4.3 ?
 For the moment, I'm going to assume 0.4.3, and put it in that milestone.

 Please change if you want something different.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31709 [Webpages/Website]: Add the Digital Climate Strike code to the Tor Website

2019-09-11 Thread Tor Bug Tracker & Wiki
#31709: Add the Digital Climate Strike code to the Tor Website
--+
 Reporter:  teor  |  Owner:  hiro
 Type:  task  | Status:  new
 Priority:  High  |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:  #31708
   Points:|   Reviewer:
  Sponsor:|
--+
 Please add the Digital Climate Strike code to the Tor Website, by
 following the Self-Hosted instructions:
 https://github.com/fightforthefuture/digital-climate-strike#option-2-self-
 hosted

 We'll also want to set these options before loading the script:
 {{{
 
   var DIGITAL_CLIMATE_STRIKE_OPTIONS = {
 /* The Tor website base URL */
 iframeHost: 'https://www.torproject.org',
 /* Disable Google Analytics, for user privacy */
 disableGoogleAnalytics: true,
 /* Let users dismiss the banner, and use the Tor website */
 showCloseButtonOnFullPageWidget: true,
   };
 
 
 }}}

 For more details, see:
 https://github.com/fightforthefuture/digital-climate-strike#customization-
 options

 More info about the Digital Climate Strike, see:
 https://digital.globalclimatestrike.net/

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

Re: [tor-bugs] #31654 [Core Tor/Tor]: Should --list-torrc-options and GETINFO config/names have more in common?

2019-09-11 Thread Tor Bug Tracker & Wiki
#31654: Should --list-torrc-options and GETINFO config/names have more in 
common?
--+--
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 That's now #31706

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31706 [Core Tor/Tor]: Expose config flags to the controller

2019-09-11 Thread Tor Bug Tracker & Wiki
#31706: Expose config flags to the controller
--+--
 Reporter:  teor  |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:  #31654
   Points:|   Reviewer:
  Sponsor:|
--+--
 In #31625, we refactored the config behaviours into an orthogonal set of
 flags.

 We should expose at least settable to the controller. We may decide to
 expose them all.

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

Re: [tor-bugs] #31111 [Core Tor/Tor]: Properly support two padding machines per circuit

2019-09-11 Thread Tor Bug Tracker & Wiki
#3: Properly support two padding machines per circuit
--+
 Reporter:  pulls |  Owner:  (none)
 Type:  defect| Status:
  |  merge_ready
 Priority:  Medium|  Milestone:  Tor:
  |  unspecified
Component:  Core Tor/Tor  |Version:  Tor:
  |  0.4.1.3-alpha
 Severity:  Normal| Resolution:
 Keywords:  wtf-pad circpad-researchers-want  |  Actual Points:
Parent ID:| Points:
 Reviewer:  mikeperry |Sponsor:
--+
Changes (by mikeperry):

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


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

[tor-bugs] #31710 [Webpages/Blog]: Write blog post about the digital climate strike, and how Tor makes activists safer

2019-09-11 Thread Tor Bug Tracker & Wiki
#31710: Write blog post about the digital climate strike, and how Tor makes
activists safer
---+--
 Reporter:  teor   |  Owner:  teor
 Type:  task   | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Webpages/Blog  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:  #31708
   Points: |   Reviewer:
  Sponsor: |
---+--
 We want to write a blog post about:
 * Tor's participation in the Digital Climate Strike, and
 * How using Tor makes climate activists safer

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

Re: [tor-bugs] #31657 [Core Tor/Tor]: Rephrase "missing descriptors" notice log to be less confusing

2019-09-11 Thread Tor Bug Tracker & Wiki
#31657: Rephrase "missing descriptors" notice log to be less confusing
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  fast-fix, log, tor-guard, tor-   |  Actual Points:  0.1
  bridge, tor-client, BugSmashFund, 042-should   |
Parent ID:  #21969   | Points:  0.1
 Reviewer:  asn  |Sponsor:
-+-
Changes (by teor):

 * status:  needs_revision => 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] #31705 [Core Tor/Tor]: Add sufficient coccinelle tooling to run coccinelle without stress

2019-09-11 Thread Tor Bug Tracker & Wiki
#31705: Add sufficient coccinelle tooling to run coccinelle without stress
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  task  | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor31-can
--+
Changes (by nickm):

 * status:  assigned => needs_review


Comment:

 CI has passed

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31707 [Core Tor/Tor]: Better handling and UX for missing and expired guard descriptors

2019-09-11 Thread Tor Bug Tracker & Wiki
#31707: Better handling and UX for missing and expired guard descriptors
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: unspecified
Component:  Core |Version:  Tor: 0.3.3.1-alpha
  Tor/Tor|   Keywords:  fast-fix, log, tor-guard, tor-
 Severity:  Normal   |  bridge, tor-client, BugSmashFund, 042-should
Actual Points:   |  Parent ID:  #21969
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Split off #31657:

 Replying to teor:
 > How do we reliably detect pathological cases?
 > Suppress the message, until it occurs a few times within a short
 timeframe?

 dgoulet:

 That's a good question I don't have an answer for.

 Unfortunately, I don't think that's the kind of message that occurs
 multiple times, looking at #30746 (and friends) this seems to be able to
 cause havoc with just a single repeatition.

 I'm not sure why this is the case, since `router_have_minimum_dir_info()`
 seems to be called all the time and that should eventually call
 `entry_guards_get_err_str_if_dir_info_missing()` which is the source of
 the log message... Things are kinda messy between these two functions tho,
 so it's kinda hard to understand what's the issue.

 Perhaps we can merge this patch for now since it does not seem to make the
 situation worse, and we can think in the future how to improve the UX? If
 you agree, feel free to toggle this into merge_ready since the patch LGTM.

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

Re: [tor-bugs] #29083 [Core Tor/Tor]: WTF-PAD: Specify exit policy for machine conditions

2019-09-11 Thread Tor Bug Tracker & Wiki
#29083: WTF-PAD: Specify exit policy for machine conditions
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad, tor-relay, tor-cell,|  Actual Points:
  padding, circpad-researchers-maybe-want|
Parent ID:   | Points:  4
 Reviewer:   |Sponsor:
 |  Sponsor2-can
-+-
Changes (by mikeperry):

 * keywords:  wtf-pad, tor-relay, tor-cell, padding => wtf-pad, tor-relay,
 tor-cell, padding, circpad-researchers-maybe-want


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

Re: [tor-bugs] #31657 [Core Tor/Tor]: Rephrase "missing descriptors" notice log to be less confusing

2019-09-11 Thread Tor Bug Tracker & Wiki
#31657: Rephrase "missing descriptors" notice log to be less confusing
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  fast-fix, log, tor-guard, tor-   |  Actual Points:  0.1
  bridge, tor-client, BugSmashFund, 042-should   |
Parent ID:  #21969   | Points:  0.1
 Reviewer:  asn  |Sponsor:
-+-

Comment (by teor):

 Let's deal with the UX / behaviour in #31707.

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

Re: [tor-bugs] #27511 [Applications/Tor Browser]: Add New identity button to toolbar

2019-09-11 Thread Tor Bug Tracker & Wiki
#27511: Add New identity button to toolbar
-+-
 Reporter:  isnaiter |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:
 |  reopened
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, tbb-newnym, tbb-9.0-must-   |  Actual Points:
  alpha, TorBrowserTeam201909|
Parent ID:  #10760   | Points:  0.5
 Reviewer:   |Sponsor:
 |  Sponsor9
-+-

Comment (by antonela):

 A while ago, I dropped some ideas at a similar TBA ticket.

 https://trac.torproject.org/projects/tor/ticket/28800#comment:8

 What do you think? When do you think users need a New Identity? When do
 you think users actually *use* a New Identity?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31708 [- Select a component]: Make the Tor website join the Digital Climate Strike on September 20

2019-09-11 Thread Tor Bug Tracker & Wiki
#31708: Make the Tor website join the Digital Climate Strike on September 20
--+--
 Reporter:  teor  |  Owner:  teor
 Type:  task  | Status:  assigned
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Isabela has approved Tor joining the Digital Climate Strike on September
 20.

 Here's more info about the Digital Climate Strike:
 https://digital.globalclimatestrike.net/


 I'll create sub-tickets for all the things we need to do to make that
 happen.

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

Re: [tor-bugs] #23818 [Core Tor/Tor]: Make v2 and v3 single onion services retry all failed intro and rend connections with a 3-hop path

2019-09-11 Thread Tor Bug Tracker & Wiki
#23818: Make v2 and v3 single onion services retry all failed intro and rend
connections with a 3-hop path
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.3-alpha
 Severity:  Normal   | Resolution:
 Keywords:  029-no-backport, 035-backport,   |  Actual Points:  0.2
  040-backport, 041-backport, v3-onion-service-  |
  feature-parity, prop224, tor-hs, single-   |
  onion, ipv6, network-team-roadmap-august,  |
  consider-backport-after-0421   |
Parent ID:   | Points:  1
 Reviewer:  asn  |Sponsor:
 |  Sponsor27-must
-+-
Changes (by teor):

 * parent:  #23493 =>


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

Re: [tor-bugs] #30172 [Core Tor/Tor]: Always send PADDING_NEGOTIATE if middle supports it

2019-09-11 Thread Tor Bug Tracker & Wiki
#30172: Always send PADDING_NEGOTIATE if middle supports it
-+-
 Reporter:  mikeperry|  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad, tor-relay, tor-cell,|  Actual Points:
  padding, circpad-researchers-maybe-want|
Parent ID:   | Points:  4
 Reviewer:   |Sponsor:
 |  Sponsor2-can
-+-
Changes (by mikeperry):

 * keywords:  wtf-pad, tor-relay, tor-cell, padding => wtf-pad, tor-relay,
 tor-cell, padding, circpad-researchers-maybe-want


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

Re: [tor-bugs] #30092 [Core Tor/Tor]: Add a probability-to-apply field for circuitpadidng machines

2019-09-11 Thread Tor Bug Tracker & Wiki
#30092: Add a probability-to-apply field for circuitpadidng machines
-+-
 Reporter:  mikeperry|  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad, tor-relay, tor-cell,|  Actual Points:  0.5
  padding, circpad-researchers-maybe-want|
Parent ID:   | Points:  2
 Reviewer:  asn  |Sponsor:
 |  Sponsor2-can
-+-
Changes (by mikeperry):

 * keywords:  wtf-pad, tor-relay, tor-cell, padding => wtf-pad, tor-relay,
 tor-cell, padding, circpad-researchers-maybe-want


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

Re: [tor-bugs] #23493 [Core Tor/Tor]: IPv6 v3 Onion Services support

2019-09-11 Thread Tor Bug Tracker & Wiki
#23493: IPv6 v3 Onion Services support
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  v3-onion-service-feature-parity- |  Actual Points:  0.7
  can, prop224, tor-hs, single-onion, ipv6,  |
  network-team-roadmap-august|
Parent ID:  #29995   | Points:  7
 Reviewer:   |Sponsor:
 |  Sponsor27-can
-+-
Changes (by teor):

 * status:  new => closed
 * resolution:   => fixed
 * milestone:  Tor: unspecified => Tor: 0.4.2.x-final


Comment:

 All the child tickets have been fixed and merged to master, closing.

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

Re: [tor-bugs] #30992 [Core Tor/Tor]: circpadding machines have shutdown sync issues (with intro circ NACKs and other cases)

2019-09-11 Thread Tor Bug Tracker & Wiki
#30992: circpadding machines have shutdown sync issues (with intro circ NACKs 
and
other cases)
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad circpad-researchers-maybe-   |  Actual Points:
  want   |
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:
-+-
Changes (by mikeperry):

 * keywords:  wtf-pad circpad 042-proposed => wtf-pad circpad-researchers-
 maybe-want


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

Re: [tor-bugs] #31636 [Core Tor/Tor]: Circuit padding: Add meta probability distribution type

2019-09-11 Thread Tor Bug Tracker & Wiki
#31636: Circuit padding: Add meta probability distribution type
-+-
 Reporter:  mikeperry|  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad, circpad-researchers-maybe-  |  Actual Points:
  want   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by mikeperry):

 * keywords:  wtf-pad => wtf-pad, circpad-researchers-maybe-want


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

[tor-bugs] #31694 [Applications/Tor Browser]: Windows Sandboxie for Tor Browser is going open source \o/

2019-09-11 Thread Tor Bug Tracker & Wiki
#31694: Windows Sandboxie for Tor Browser is going open source \o/
+--
 Reporter:  cypherpunks |  Owner:  tbb-team
 Type:  enhancement | Status:  new
 Priority:  Medium  |  Component:  Applications/Tor Browser
  Version:  |   Severity:  Normal
 Keywords:  tbb-sandboxing  |  Actual Points:
Parent ID:  #19750  | Points:
 Reviewer:  |Sponsor:
+--
 https://community.sophos.com/products/sandboxie/f/forum/115109/major-
 sandboxie-news-sandboxie-is-now-a-free-tool-with-plans-to-transition-it-
 to-an-open-source-tool

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

Re: [tor-bugs] #31691 [Applications/Tor Browser]: Go ldflags should set static build ID

2019-09-11 Thread Tor Bug Tracker & Wiki
#31691: Go ldflags should set static build ID
--+--
 Reporter:  JeremyRand|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 proof?

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

Re: [tor-bugs] #31657 [Core Tor/Tor]: Rephrase "missing descriptors" notice log to be less confusing

2019-09-11 Thread Tor Bug Tracker & Wiki
#31657: Rephrase "missing descriptors" notice log to be less confusing
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  fast-fix, log, tor-guard, tor-   |  Actual Points:  0.1
  bridge, tor-client, BugSmashFund, 042-should   |
Parent ID:  #21969   | Points:  0.1
 Reviewer:  asn  |Sponsor:
-+-

Comment (by asn):

 Replying to [comment:6 teor]:
 > How do we reliably detect pathological cases?
 > Suppress the message, until it occurs a few times within a short
 timeframe?

 That's a good question I don't have an answer for.

 Unfortunately, I don't think that's the kind of message that occurs
 multiple times, looking at #30746 (and friends) this seems to be able to
 cause havoc with just a single repeatition.

 I'm not sure why this is the case, since `router_have_minimum_dir_info()`
 seems to be called all the time and that should eventually call
 `entry_guards_get_err_str_if_dir_info_missing()` which is the source of
 the log message... Things are kinda messy between these two functions tho,
 so it's kinda hard to understand what's the issue.

 Perhaps we can merge this patch for now since it does not seem to make the
 situation worse, and we can think in the future how to improve the UX? If
 you agree, feel free to toggle this into merge_ready since the patch LGTM.

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

Re: [tor-bugs] #30126 [Applications/Tor Browser]: Make Tor Browser on macOS compatible with Apple's notarization

2019-09-11 Thread Tor Bug Tracker & Wiki
#30126: Make Tor Browser on macOS compatible with Apple's notarization
+--
 Reporter:  gk  |  Owner:  tbb-team
 Type:  task| Status:  new
 Priority:  Very High   |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-security, TorBrowserTeam201909  |  Actual Points:
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:
+--

Comment (by gk):

 Hrm, okay. Let's first test whether my signing attempts now succeed by
 following your instructions closer (I think I messed up the stapling at
 least yesterday) and appease our Gatekeeper:

 https://people.torproject.org/~gk/testbuilds/TorBrowser-9.0a6-osx64_en-
 US_30126.dmg
 https://people.torproject.org/~gk/testbuilds/TorBrowser-9.0a6-osx64_en-
 US_30126.dmg.asc

 I then thought, testing with 8.5.5 as well because maybe the crash you saw
 is esr68-based. Here is the result:

 https://people.torproject.org/~gk/testbuilds/TorBrowser-8.5.5-osx64_en-
 US_30126.dmg
 https://people.torproject.org/~gk/testbuilds/TorBrowser-8.5.5-osx64_en-
 US_30126.dmg.asc

 Note: the latter is very surprising. macOS shows both for alpha and stable
 that Apple checked for malware and the notarization succeeded, however, we
 did not backport the build changes made in #31465 yet. Will be interesting
 to see what Catalina says.

 Regarding the crash there is
 https://bugzilla.mozilla.org/show_bug.cgi?id=1578075 which we might
 somehow hit? Although it would be kind of weird why starting from bash
 would avoid 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] #27401 [Applications/Tor Browser]: RC for Tor Browser 8.0 disables JavaScript on first start and does not load onboarding

2019-09-11 Thread Tor Bug Tracker & Wiki
#27401: RC for Tor Browser 8.0 disables JavaScript on first start and does not 
load
onboarding
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Immediate|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  TorBrowserTeam201808R, AffectsTails  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by jasonroy11):

 Nice . Thanks for posting it javascript is fixed now
 https://robuxgenerators.com/

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

Re: [tor-bugs] #31671 [Applications/Tor Browser]: Firefox's integration with Cloudflare for DNS-over-HTTPS

2019-09-11 Thread Tor Bug Tracker & Wiki
#31671: Firefox's integration with Cloudflare for DNS-over-HTTPS
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:  wontfix
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

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


Comment:

 There are currently no plans to switch to a different browser as the base
 for 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

Re: [tor-bugs] #31688 [Applications/Tor Browser]: go build/install should pass -trimpath flag

2019-09-11 Thread Tor Bug Tracker & Wiki
#31688: go build/install should pass -trimpath flag
--+--
 Reporter:  JeremyRand|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-rbm   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * keywords:   => tbb-rbm


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31695 [Metrics/CollecTor]: Allow pushing Metrics to CollecTor from trusted endpoints

2019-09-11 Thread Tor Bug Tracker & Wiki
#31695: Allow pushing Metrics to CollecTor from trusted endpoints
---+--
 Reporter:  irl|  Owner:  metrics-team
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+--
 Switch from pull to push model for archiving OnionPerf data: Another
 aspect related to collecting data is that, right now, data collection
 works by periodically pulling new .tpf files from known OnionPerf
 instances. This has at least two problems: there's a delay between
 OnionPerfs producing new files and CollecTor pulling them, and adding new
 instances requires editing a config file on the CollecTor host. Maybe we
 can switch to a push model where CollecTor accepts measurements from any
 OnionPerf instance, and CollecTor clients like the Tor Metrics website
 decide which measurements to aggregate and visualize. Note that switching
 to a push model requires installing some basic authentication mechanisms
 like cryptographic identities and signatures, in order to prevent anyone
 from pushing wrong data, overwriting correct data, or even storing
 arbitrary data.

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

Re: [tor-bugs] #27493 [Applications/Tor Browser]: 'mk_add_options' or 'export' MOZILLA_OFFICIAL

2019-09-11 Thread Tor Bug Tracker & Wiki
#27493: 'mk_add_options' or 'export' MOZILLA_OFFICIAL
-+-
 Reporter:  sysrqb   |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  TorBrowserTeam201909R, tbb-9.0   |  Actual Points:
  -must-alpha|
Parent ID:  #30320   | Points:  0.1
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 #31308 is duplicate.

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

Re: [tor-bugs] #31308 [Applications/Tor Browser]: Sync mozconfig files used in tor-browser over to tor-browser-build for esr68

2019-09-11 Thread Tor Bug Tracker & Wiki
#31308: Sync mozconfig files used in tor-browser over to tor-browser-build for
esr68
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff68-esr, tbb-9.0-must-alpha, tbb-   |  duplicate
  rbm, TorBrowserTeam201909  |  Actual Points:
Parent ID:   | Points:  0.1
 Reviewer:   |Sponsor:
 |  Sponsor44-can
-+-
Changes (by gk):

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


Comment:

 I think #27493 has all we need for now. Closing this as a duplicate.

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

Re: [tor-bugs] #29945 [Webpages/Website]: fiscal documents page has missing docs, typos, and wrong labels

2019-09-11 Thread Tor Bug Tracker & Wiki
#29945: fiscal documents page has missing docs, typos, and wrong labels
--+--
 Reporter:  arma  |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #29901| Points:
 Reviewer:|Sponsor:
--+--

Comment (by ggus):

 I checked today, and second and third problems still remain.

 We should fix this asap. Let's talk about this during www meeting today.

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

Re: [tor-bugs] #31694 [Applications/Tor Browser]: Windows Sandboxie for Tor Browser is going open source \o/

2019-09-11 Thread Tor Bug Tracker & Wiki
#31694: Windows Sandboxie for Tor Browser is going open source \o/
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  enhancement   | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  invalid
 Keywords:  tbb-sandboxing|  Actual Points:
Parent ID:  #19750| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 For Mozilla?

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

Re: [tor-bugs] #31689 [Applications/Tor Browser]: Upgrade go to 1.13+

2019-09-11 Thread Tor Bug Tracker & Wiki
#31689: Upgrade go to 1.13+
--+--
 Reporter:  JeremyRand|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-rbm   |  Actual Points:
Parent ID:  #31688| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * keywords:   => tbb-rbm
 * parent:   => #31688


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

Re: [tor-bugs] #6005 [Applications/Tor Browser]: Secure download of videos from YouTube

2019-09-11 Thread Tor Bug Tracker & Wiki
#6005: Secure download of videos from YouTube
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  enhancement   | Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  wontfix
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * keywords:  needs-triage =>
 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Replying to [comment:8 cypherpunks]:
 > This is out of the scope of TBB.

 I agree.

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

Re: [tor-bugs] #31696 [Core Tor/Tor]: Assertion failure in map-anon.c:218

2019-09-11 Thread Tor Bug Tracker & Wiki
#31696: Assertion failure in map-anon.c:218
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.1.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.4.1.5
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Description changed by gk:

Old description:

> We got a bug report for tor 0.4.1.5 on x86_64 14.2 Slackware system on
> the blog:
> {{{
> Raw assertion failed at src/lib/malloc/map_anon.c:218:
> noinherit_result == tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(dump_stack_symbols_to_error_fds+0x33)
> [0x55ff75f58743] tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(tor_raw_assertion_failed_msg_+0x86)
> [0x55ff75f58e26] tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(tor_mmap_anonymous+0xca)
> [0x55ff75f57f3a] tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(crypto_fast_rng_new_from_seed+0x35)
> [0x55ff75f009f5] tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(crypto_fast_rng_new+0x2b)
> [0x55ff75f00a9b] tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(get_thread_fast_rng+0x45)
> [0x55ff75f00c35] tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(circuit_reset_sendme_randomness+0x21)[0x55ff75e02fb1]
> tor-browser_en-US/Browser/TorBrowser/Tor/tor(+0x8342b)
> [0x55ff75dd142b] tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(origin_circuit_new+0x8f)
> [0x55ff75dd3aef] tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(origin_circuit_init+0x22)
> [0x55ff75dcceb2] tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(circuit_establish_circuit+0x37)[0x55ff75dcf877]
> tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(circuit_launch_by_extend_info+0x9c)[0x55ff75de6b2c]
> tor-browser_en-US/Browser/TorBrowser/Tor/tor(+0x99859)
> [0x55ff75de7859] tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(connection_ap_handshake_attach_circuit+0x321)
> [0x55ff75de8251] tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(connection_ap_attach_pending+0x1b0)[0x55ff75dec6b0]
> ./TorBrowser/Tor/libevent-2.1.so.6(+0x22395)
> [0x7fdac04cc395]
> ./TorBrowser/Tor/libevent-2.1.so.6(event_base_loop+0x55f)
> [0x7fdac04ccc6f] tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(do_main_loop+0xe5)
> [0x55ff75dbce95] tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(tor_run_main+0x1225)
> [0x55ff75daa8d5] tor-browser_en-
> US/Browser/TorBrowser/Tor/tor(tor_main+0x3a)
> [0x55ff75da7d5a] tor-browser_en-US/Browser/TorBrowser/Tor/tor(main+0x19)
> [0x55ff75da78b9] /lib64/libc.so.6(__libc_start_main+0xf0)
> [0x7fdabf6497d0] tor-browser_en-US/Browser/TorBrowser/Tor/tor(+0x59909)
> [0x55ff75da7909]
> }}}
> 0.4.0.5 worked fine on that system.

New description:

 We got a bug report for tor 0.4.1.5 on x86_64 14.2 Slackware system on the
 blog (https://blog.torproject.org/comment/283980#comment-283980):
 {{{
 Raw assertion failed at src/lib/malloc/map_anon.c:218:
 noinherit_result == tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(dump_stack_symbols_to_error_fds+0x33)
 [0x55ff75f58743] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(tor_raw_assertion_failed_msg_+0x86)
 [0x55ff75f58e26] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(tor_mmap_anonymous+0xca)
 [0x55ff75f57f3a] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(crypto_fast_rng_new_from_seed+0x35)
 [0x55ff75f009f5] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(crypto_fast_rng_new+0x2b)
 [0x55ff75f00a9b] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(get_thread_fast_rng+0x45)
 [0x55ff75f00c35] tor-browser_en-
 
US/Browser/TorBrowser/Tor/tor(circuit_reset_sendme_randomness+0x21)[0x55ff75e02fb1]
 tor-browser_en-US/Browser/TorBrowser/Tor/tor(+0x8342b)
 [0x55ff75dd142b] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(origin_circuit_new+0x8f)
 [0x55ff75dd3aef] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(origin_circuit_init+0x22)
 [0x55ff75dcceb2] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(circuit_establish_circuit+0x37)[0x55ff75dcf877]
 tor-browser_en-
 
US/Browser/TorBrowser/Tor/tor(circuit_launch_by_extend_info+0x9c)[0x55ff75de6b2c]
 tor-browser_en-US/Browser/TorBrowser/Tor/tor(+0x99859)
 [0x55ff75de7859] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(connection_ap_handshake_attach_circuit+0x321)
 [0x55ff75de8251] tor-browser_en-
 
US/Browser/TorBrowser/Tor/tor(connection_ap_attach_pending+0x1b0)[0x55ff75dec6b0]
 ./TorBrowser/Tor/libevent-2.1.so.6(+0x22395)
 [0x7fdac04cc395] ./TorBrowser/Tor/libevent-2.1.so.6(event_base_loop+0x55f)
 [0x7fdac04ccc6f] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(do_main_loop+0xe5)
 [0x55ff75dbce95] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(tor_run_main+0x1225)
 [0x55ff75daa8d5] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(tor_main+0x3a)
 [0x55ff75da7d5a] tor-browser_en-US/Browser/TorBrowser/Tor/tor(main+0x19)
 

Re: [tor-bugs] #31641 [Webpages/Website]: Provide link to Tor Browser for Android alpha on our alpha download page

2019-09-11 Thread Tor Bug Tracker & Wiki
#31641: Provide link to Tor Browser for Android alpha on our alpha download page
---+
 Reporter:  gk |  Owner:  hiro
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Webpages/Website   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  TorBrowserTeam201909R  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by boklm):

 * status:  needs_review => 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] #31694 [Applications/Tor Browser]: Windows Sandboxie for Tor Browser is going open source \o/

2019-09-11 Thread Tor Bug Tracker & Wiki
#31694: Windows Sandboxie for Tor Browser is going open source \o/
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  enhancement   | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  invalid
 Keywords:  tbb-sandboxing|  Actual Points:
Parent ID:  #19750| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

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


Comment:

 Good stuff but not a ticket for us to work on.

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

Re: [tor-bugs] #31689 [Applications/Tor Browser]: Upgrade go to 1.13+

2019-09-11 Thread Tor Bug Tracker & Wiki
#31689: Upgrade go to 1.13+
--+--
 Reporter:  JeremyRand|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-rbm   |  Actual Points:
Parent ID:  #31688| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 Replying to [comment:1 JeremyRand]:
 > Are there any expected compatibility issues from upgrading to Go 1.13,
 or should it just be as simple as bumping the version number in the `go`
 project config?  If the latter, I'm happy to code up a patch for this one.

 Hard to say. :) Give it a try if you want?

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

[tor-bugs] #31696 [Core Tor/Tor]: Assertion failure in map-anon.c:218

2019-09-11 Thread Tor Bug Tracker & Wiki
#31696: Assertion failure in map-anon.c:218
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.1.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.4.1.5
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 We got a bug report for tor 0.4.1.5 on x86_64 14.2 Slackware system on the
 blog:
 {{{
 Raw assertion failed at src/lib/malloc/map_anon.c:218:
 noinherit_result == tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(dump_stack_symbols_to_error_fds+0x33)
 [0x55ff75f58743] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(tor_raw_assertion_failed_msg_+0x86)
 [0x55ff75f58e26] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(tor_mmap_anonymous+0xca)
 [0x55ff75f57f3a] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(crypto_fast_rng_new_from_seed+0x35)
 [0x55ff75f009f5] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(crypto_fast_rng_new+0x2b)
 [0x55ff75f00a9b] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(get_thread_fast_rng+0x45)
 [0x55ff75f00c35] tor-browser_en-
 
US/Browser/TorBrowser/Tor/tor(circuit_reset_sendme_randomness+0x21)[0x55ff75e02fb1]
 tor-browser_en-US/Browser/TorBrowser/Tor/tor(+0x8342b)
 [0x55ff75dd142b] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(origin_circuit_new+0x8f)
 [0x55ff75dd3aef] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(origin_circuit_init+0x22)
 [0x55ff75dcceb2] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(circuit_establish_circuit+0x37)[0x55ff75dcf877]
 tor-browser_en-
 
US/Browser/TorBrowser/Tor/tor(circuit_launch_by_extend_info+0x9c)[0x55ff75de6b2c]
 tor-browser_en-US/Browser/TorBrowser/Tor/tor(+0x99859)
 [0x55ff75de7859] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(connection_ap_handshake_attach_circuit+0x321)
 [0x55ff75de8251] tor-browser_en-
 
US/Browser/TorBrowser/Tor/tor(connection_ap_attach_pending+0x1b0)[0x55ff75dec6b0]
 ./TorBrowser/Tor/libevent-2.1.so.6(+0x22395)
 [0x7fdac04cc395] ./TorBrowser/Tor/libevent-2.1.so.6(event_base_loop+0x55f)
 [0x7fdac04ccc6f] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(do_main_loop+0xe5)
 [0x55ff75dbce95] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(tor_run_main+0x1225)
 [0x55ff75daa8d5] tor-browser_en-
 US/Browser/TorBrowser/Tor/tor(tor_main+0x3a)
 [0x55ff75da7d5a] tor-browser_en-US/Browser/TorBrowser/Tor/tor(main+0x19)
 [0x55ff75da78b9] /lib64/libc.so.6(__libc_start_main+0xf0)
 [0x7fdabf6497d0] tor-browser_en-US/Browser/TorBrowser/Tor/tor(+0x59909)
 [0x55ff75da7909]
 }}}
 0.4.0.5 worked fine on that system.

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

Re: [tor-bugs] #31601 [Applications/Tor Browser]: Don't let Mozilla recommend extensions again

2019-09-11 Thread Tor Bug Tracker & Wiki
#31601: Don't let Mozilla recommend extensions again
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  TorBrowserTeam201909R, tbb-9.0   |  Actual Points:
  -must-alpha, ff68-esr  |
Parent ID:   | Points:  0.25
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

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


Comment:

 Looks good. Cherry-picked onto `tor-browser-68.1.0esr-9.0-2` (commit
 e489c5048b762b3226db23b6ea9ffc440617615e).

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

Re: [tor-bugs] #24231 [Webpages/Website]: users looking for Tor Browser uninstall instructions should find the correct ones

2019-09-11 Thread Tor Bug Tracker & Wiki
#24231: users looking for Tor Browser uninstall instructions should find the
correct ones
--+--
 Reporter:  catalyst  |  Owner:  traumschule
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  website redesign
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:  #14686| Points:
 Reviewer:|Sponsor:
--+--
Changes (by ggus):

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


Comment:

 Fixed here: https://tb-manual.torproject.org/uninstalling/

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

Re: [tor-bugs] #23922 [Community/Tor Browser Manual]: The Uninstalling page does not mention the TorBrowser-Data directory on OSX

2019-09-11 Thread Tor Bug Tracker & Wiki
#23922: The Uninstalling page does not mention the TorBrowser-Data directory on 
OSX
--+
 Reporter:  boklm |  Owner:  boklm
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Community/Tor Browser Manual  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  docshackathon |  Actual Points:
Parent ID:  #24231| Points:
 Reviewer:|Sponsor:
--+
Changes (by ggus):

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


Comment:

 It's fixed here: https://tb-manual.torproject.org/uninstalling/

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

Re: [tor-bugs] #30126 [Applications/Tor Browser]: Make Tor Browser on macOS compatible with Apple's notarization

2019-09-11 Thread Tor Bug Tracker & Wiki
#30126: Make Tor Browser on macOS compatible with Apple's notarization
+--
 Reporter:  gk  |  Owner:  tbb-team
 Type:  task| Status:  new
 Priority:  Very High   |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-security, TorBrowserTeam201909  |  Actual Points:
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:
+--

Comment (by gk):

 Checking with `x86_64-apple-darwin11-otool -l Tor\
 Browser.app/Contents/MacOS/firefox` shows still
 {{{
 cmd LC_VERSION_MIN_MACOSX
   cmdsize 16
   version 10.7
   sdk 10.6
 }}}
 So, maybe Apple silently relaxed some requirements here (too)?

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

Re: [tor-bugs] #31691 [Applications/Tor Browser]: Go ldflags should set static build ID

2019-09-11 Thread Tor Bug Tracker & Wiki
#31691: Go ldflags should set static build ID
--+--
 Reporter:  JeremyRand|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-rbm   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * keywords:   => tbb-rbm


Comment:

 Interesting. I wonder why we have not hit that issue yet. I am fine adding
 that part if it really helps.

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

Re: [tor-bugs] #31621 [Applications/Tor Browser]: Fix node bug that makes large writes to stdout fail

2019-09-11 Thread Tor Bug Tracker & Wiki
#31621: Fix node bug that makes large writes to stdout fail
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-rbm, ff68-esr, tbb-9.0-must- |  Actual Points:
  alpha, TorBrowserTeam201909R,  |
  GeorgKoppen201909  |
Parent ID:  #31538   | Points:  0.25
 Reviewer:   |Sponsor:
-+-
Changes (by boklm):

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


Comment:

 Replying to [comment:2 gk]:
 >
 > Thanks! That saved me some hours of work. `bug_31621`
 (https://gitweb.torproject.org/user/gk/tor-
 browser.git/commit/?h=bug_31621=a81c439b3f490c75e0abf5a52de7927e09c3c4f5)
 in my `tor-browser` repo and `bug_31621`
 (https://gitweb.torproject.org/user/gk/tor-browser-
 build.git/commit/?h=bug_31621=5648e1499c10d2565e2cd9ca23599b532df8cff4)
 in my `tor-browser-build` one have the patches for review.

 This looks good to me. I cherry-picked the `tor-browser` patch to branch
 `tor-browser-68.1.0esr-9.0-2` as commit
 `4458b4e8a09aaa759f1735b36aec860aa61f3ba7`, and merged the `tor-browser-
 build` patch to `master` with commit
 `f08dbd57ed76faa08007608130da50c4f80a9d64`.

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

Re: [tor-bugs] #31596 [Applications/Tor Browser]: Bump mingw-w64 version to pick up fix for #31567

2019-09-11 Thread Tor Bug Tracker & Wiki
#31596: Bump mingw-w64 version to pick up fix for #31567
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  TorBrowserTeam201909R, tbb-9.0   |  Actual Points:
  -must-alpha, tbb-rbm   |
Parent ID:  #30322   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by boklm):

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


Comment:

 Replying to [comment:1 gk]:
 > `bug_31596` (https://gitweb.torproject.org/user/gk/tor-browser-
 build.git/commit/?h=bug_31596=3ea80a42a85edc5e931cd241218cc5f0f2ff5b57)
 has a fix for this bug up for review.

 This looks good to me. I merged it to master with commit
 `4e92d40f4cee86426752aa21f7ddbb102be9d0c9`.

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

Re: [tor-bugs] #28862 [Webpages]: cant log in to tor

2019-09-11 Thread Tor Bug Tracker & Wiki
#28862: cant log in to tor
---+--
 Reporter:  Fx2345 |  Owner:  (none)
 Type:  defect | Status:  closed
 Priority:  Very High  |  Milestone:
Component:  Webpages   |Version:
 Severity:  Normal | Resolution:  user disappeared
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by ggus):

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


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

Re: [tor-bugs] #31264 [Applications/rbm]: tar.gz output files contain nonreproducible timestamps

2019-09-11 Thread Tor Bug Tracker & Wiki
#31264: tar.gz output files contain nonreproducible timestamps
---+
 Reporter:  JeremyRand |  Owner:  boklm
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Applications/rbm   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  TorBrowserTeam201909R  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by boklm):

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


Comment:

 Replying to [comment:10 JeremyRand]:
 >
 > Done; updated patch at https://notabug.org/JeremyRand/rbm/src/gzip-
 timestamps , Git commit hash `5a41aae4a0d745f74b675d3c9c142b3d5fb3ca09`.

 Thanks. I merged this patch to `rbm.git` and updated the rbm submodule in
 `tor-browser-build` with commit
 `873865aa9dc3d3f734458e86dbe542db67ad1929`.

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

Re: [tor-bugs] #31596 [Applications/Tor Browser]: Bump mingw-w64 version to pick up fix for #31567

2019-09-11 Thread Tor Bug Tracker & Wiki
#31596: Bump mingw-w64 version to pick up fix for #31567
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  TorBrowserTeam201909R, tbb-9.0   |  Actual Points:
  -must-alpha, tbb-rbm   |
Parent ID:  #30322   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by boklm):

 Replying to [comment:2 cypherpunks]:
 > `   - filename: mingw-winrt.patch`?

 It doesn't look like this one was merged upstream, so we should keep 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] #31621 [Applications/Tor Browser]: Fix node bug that makes large writes to stdout fail

2019-09-11 Thread Tor Bug Tracker & Wiki
#31621: Fix node bug that makes large writes to stdout fail
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-rbm, ff68-esr, tbb-9.0-must- |  Actual Points:  0.25
  alpha, TorBrowserTeam201909R,  |
  GeorgKoppen201909  |
Parent ID:  #31538   | Points:  0.25
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * actualpoints:   => 0.25


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31697 [Internal Services/Tor Sysadmin Team]: Please update gk's PGP public key (2019 edition)

2019-09-11 Thread Tor Bug Tracker & Wiki
#31697: Please update gk's PGP public key (2019 edition)
-+-
 Reporter:  gk   |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Another year, another subkey update. Please fetch the new subkeys for
 LDAP.

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

Re: [tor-bugs] #31697 [Internal Services/Tor Sysadmin Team]: Please update gk's PGP public key (2019 edition)

2019-09-11 Thread Tor Bug Tracker & Wiki
#31697: Please update gk's PGP public key (2019 edition)
-+-
 Reporter:  gk   |  Owner:  tpa
 Type:  task | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by weasel):

 * status:  new => needs_information


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

Re: [tor-bugs] #31697 [Internal Services/Tor Sysadmin Team]: Please update gk's PGP public key (2019 edition)

2019-09-11 Thread Tor Bug Tracker & Wiki
#31697: Please update gk's PGP public key (2019 edition)
-+-
 Reporter:  gk   |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by weasel):

 $ gpg --recv 35CD74C24A9B15A19E1A81A194373AA94B7C3223
 gpg: key 94373AA94B7C3223: "Georg Koppen " not changed

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

Re: [tor-bugs] #31354 [Core Tor/Tor]: Compiler "note" in test_addr.c: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’

2019-09-11 Thread Tor Bug Tracker & Wiki
#31354: Compiler "note" in test_addr.c: variable tracking size limit exceeded 
with
‘-fvar-tracking-assignments’
---+---
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:
   |  merge_ready
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  regression, 042-should, asn-merge  |  Actual Points:
Parent ID: | Points:
 Reviewer:  catalyst   |Sponsor:
---+---
Changes (by nickm):

 * keywords:  regression, 042-should => regression, 042-should, asn-merge


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

Re: [tor-bugs] #29669 [Core Tor/Tor]: hs: ADD_ONION with NEW:BEST is still pinned on v2

2019-09-11 Thread Tor Bug Tracker & Wiki
#29669: hs: ADD_ONION with NEW:BEST is still pinned on v2
-+-
 Reporter:  dgoulet  |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.5.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, tor-control, hs-v3, tor- |  Actual Points:  0.1
  spec, security, 041-deferred-20190530  |
  042-should |
Parent ID:  #29995   | Points:  1
 Reviewer:  asn  |Sponsor:
 |  Sponsor27-must
-+-
Changes (by dgoulet):

 * status:  new => needs_review
 * reviewer:   => asn
 * actualpoints:   => 0.1


Comment:

 PR: https://github.com/torproject/tor/pull/1317
 Branch: `ticket29669_042_01`

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

Re: [tor-bugs] #31578 [Core Tor/Tor]: practracker scans build directories inside the tor/ directory

2019-09-11 Thread Tor Bug Tracker & Wiki
#31578: practracker scans build directories inside the tor/ directory
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:  fixed
 Keywords:  practracker, regression?,|  Actual Points:  0.1
  042-should, dgoulet-merge  |
Parent ID:   | Points:  0.1
 Reviewer:  asn  |Sponsor:
 |  Sponsor31-can
-+-
Changes (by dgoulet):

 * status:  merge_ready => closed
 * points:   => 0.1
 * resolution:   => fixed
 * actualpoints:  .1 => 0.1


Comment:

 I've merged `nickm/ticket31578_merged` that nickm made since it had a
 conflict with upstream.

 Diff was good from the 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] #28499 [Webpages/Support]: tb-manual: create redirects for old resources

2019-09-11 Thread 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:
--+--

Comment (by emmapeel):

 no

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

Re: [tor-bugs] #31696 [Core Tor/Tor]: Assertion failure in map-anon.c:218

2019-09-11 Thread Tor Bug Tracker & Wiki
#31696: Assertion failure in map-anon.c:218
-+-
 Reporter:  gk   |  Owner:  nickm
 Type:  defect   | Status:
 |  accepted
 Priority:  High |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.5
 Severity:  Normal   | Resolution:
 Keywords:  regression crash 041-regression  |  Actual Points:  .1
  BugSmashFund   |
Parent ID:   | Points:  .1
 Reviewer:  ahf  |Sponsor:
-+-
Changes (by nickm):

 * actualpoints:   => .1


Comment:

 Branch at `bug31696_041` ; PR at
 https://github.com/torproject/tor/pull/1318 .

 I'll put this in needs_review once CI has passed.

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

  1   2   >