Re: [tor-bugs] #33522 [Core Tor/Tor]: Add iOS support in your CI

[Tor Bug Tracker & Wiki]

#33522: Add iOS support in your CI
--+--
 Reporter:  tla   |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by teor):

 * keywords:  042-backport 043-should =>
 * milestone:  Tor: 0.4.3.x-final => Tor: unspecified


Comment:

 I opened #33837 for the compilation error.

 Let's focus on CI in this ticket.

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

[tor-bugs] #33837 [Core Tor/Tor]: Tor.framework Unknown type name 'dispatch_queue_t'

[Tor Bug Tracker & Wiki]

#33837: Tor.framework Unknown type name 'dispatch_queue_t'
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.4.3.x-final
Component:  Core |Version:
  Tor/Tor|   Keywords:  043-should, 043-backport,
 Severity:  Normal   |  042-backport, 041-backport
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 From https://trac.torproject.org/projects/tor/ticket/33522#comment:2
 >
 > Replying to [ticket:33522 tla]:
 > > It has a Travis-CI configuration, which I just updated to work on the
 latest macOS/Xcode image:
 > >
 > > https://github.com/iCepa/Tor.framework/blob/master/.travis.yml
 > >
 > >
 > > Currently, we have issues in getting past Tor 0.4.0.6 on iOS. When I
 try to use a newer core, I get this error message:
 > >
 > > > Unknown type name 'dispatch_queue_t'
 > >
 > > in CFStream of Apple's CoreFoundation framework.
 > >
 > >
 > > But "dispatch_queue_t" is actually a valid symbol from Apple's
 Foundation libraries.
 > >
 > > So somehow, it gets cancelled out through something which changed in
 Tor recently.
 >
 > This looks like a bug in tor's code, or perhaps in the Tor.framework
 embedding scripts.
 >
 > We'd be happy to help you diagnose this issue.
 >
 > Can you tell us the first release that has this issue? Is it 0.4.1,
 0.4.2, or 0.4.3 ?
 > Have you done a git bisect, to track down the commit that introduced the
 issue?
 >
 > Let's open a separate ticket, so we can fix this bug in tor's code.
 > Or help you find a workaround when you embed tor.

 I can't see dispatch_queue_t in Tor's code.

 Perhaps we're defining some preprocessor symbols, or including a header
 that conflicts with dispatch_queue_t's header.

 We don't know which release this bug was introduced in. But Tor 0.4.0.6
 does not have this error.

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

Re: [tor-bugs] #33522 [Core Tor/Tor]: Add iOS support in your CI

[Tor Bug Tracker & Wiki]

#33522: Add iOS support in your CI
-+
 Reporter:  tla  |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  042-backport 043-should  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by teor):

 Hi, I'm one of the maintainers of Tor's CI.

 There are two very different issues in this ticket, so I'll try to address
 them separately:

 Replying to [ticket:33522 tla]:
 > It has a Travis-CI configuration, which I just updated to work on the
 latest macOS/Xcode image:
 >
 > https://github.com/iCepa/Tor.framework/blob/master/.travis.yml
 >
 >
 > Currently, we have issues in getting past Tor 0.4.0.6 on iOS. When I try
 to use a newer core, I get this error message:
 >
 > > Unknown type name 'dispatch_queue_t'
 >
 > in CFStream of Apple's CoreFoundation framework.
 >
 >
 > But "dispatch_queue_t" is actually a valid symbol from Apple's
 Foundation libraries.
 >
 > So somehow, it gets cancelled out through something which changed in Tor
 recently.

 This looks like a bug in tor's code, or perhaps in the Tor.framework
 embedding scripts.

 We'd be happy to help you diagnose this issue.

 Can you tell us the first release that has this issue? Is it 0.4.1, 0.4.2,
 or 0.4.3 ?
 Have you done a git bisect, to track down the commit that introduced the
 issue?

 Let's open a separate ticket, so we can fix this bug in tor's code.
 Or help you find a workaround when you embed tor.

 > We're really stuck here, so it would be a huge help, if you could add
 Tor.framework to your Continuous Integration so you'd be able to support
 us here and detect problems earlier in the future.
 >
 > For your purposes, there's no need to have Macs and Xcode.
 > The most important files to control the build are these shell scripts:
 >
 > https://github.com/iCepa/Tor.framework/blob/master/Tor/tor.sh
 > https://github.com/iCepa/Tor.framework/blob/master/Tor/libevent.sh
 > https://github.com/iCepa/Tor.framework/blob/master/Tor/openssl.sh
 > https://github.com/iCepa/Tor.framework/blob/master/Tor/xz.sh
 >
 > Tor and the other libraries come in via Git submodules:
 > https://github.com/iCepa/Tor.framework/blob/master/.gitmodules
 >
 > So the dev process on your side would be:
 >
 > Update submodules to your latest state, let it build in Travis. If
 broken, fix above build scripts. Re-run through Travis.
 >
 >
 > Could that work for you?

 This is a CI configuration change request for Tor.

 We already struggle with the speed of Tor's CI.
 We build about 10 jobs per branch, and we support 4-6 branches.

 We've recently added stem and chutney tests to our CI, and it's taken a
 lot of time to diagnose issues.
 When stem or chutney have failures, Tor developers have to check every CI
 failures.
 And volunteers get very confused by the failures.

 So I don't think we can maintain Tor.framework in Tor's CI.

 I have an alternative proposal, based on the way that chutney and sbws do
 CI:

 Tor.framework adds a CI job for each supported Tor maint-* branch.
 You don't have to build every release, just the ones you want to support.

 Here's a list of the releases we support:
 *
 
https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases#Current

 Maybe you could skip our long-term support release (0.3.5), and start
 with:
 * maint-0.4.1
 * maint-0.4.2
 * maint-0.4.3
 * master

 Then, when one of our releases fails to build, you can log a bug in our
 bug tracker, and we'll fix it.

 You can add a cron job for your Travis CI jobs, so they run every day (or
 week), even if Tor.framework hasn't had any code changes.

 Here's how that looks for chutney and sbws:
 * https://github.com/torproject/chutney/blob/master/.travis.yml
 * https://github.com/torproject/sbws/blob/master/.travis.yml

 They use tor's pre-compiled nightly binaries. But you'd need to use git
 branches instead.

 What do you think?

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

Re: [tor-bugs] #33072 [Core Tor/Tor]: When under load, give 503 aggressively for dirport requests without compression

[Tor Bug Tracker & Wiki]

#33072: When under load, give 503 aggressively for dirport requests without
compression
-+-
 Reporter:  nickm|  Owner:  dgoulet
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-health 044-should consider-  |  Actual Points:
  backport-after-0434 042-backport 043-backport  |
Parent ID:  #33018   | Points:
 Reviewer:  teor |Sponsor:
-+-
Changes (by teor):

 * keywords:
 network-health 043-should consider-backport-after-0434 042-backport
 043-backport
 =>
 network-health 044-should consider-backport-after-0434 042-backport
 043-backport


Comment:

 This ticket is in 0.4.4, so I can't be 043-should.

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

Re: [tor-bugs] #32564 [Core Tor/Tor]: Assertion pol->magic failed

[Tor Bug Tracker & Wiki]

#32564: Assertion pol->magic failed
--+
 Reporter:  Logforme  |  Owner:  (none)
 Type:  defect| Status:
  |  needs_information
 Priority:  High  |  Milestone:  Tor:
  |  0.4.4.x-final
Component:  Core Tor/Tor  |Version:  Tor:
  |  0.4.1.6
 Severity:  Normal| Resolution:
 Keywords:  assert crash backport 044-should  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * keywords:  assert crash backport 043-must => assert crash backport
 044-should


Comment:

 This ticket is in 0.4.4, so I can't be 043-should.

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

Re: [tor-bugs] #29220 [Core Tor/Tor]: Update review guidelines to list best practices

[Tor Bug Tracker & Wiki]

#29220: Update review guidelines to list best practices
-+-
 Reporter:  nickm|  Owner:  asn
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  doc, 042-deferred, s31-docs, |  Actual Points:
  044-should |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  doc, 042-deferred, s31-docs, 043-should => doc, 042-deferred,
 s31-docs, 044-should


Comment:

 This ticket is in 0.4.4, so I can't be 043-should.

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

Re: [tor-bugs] #29546 [Core Tor/Tor]: Update Maintaining.md after new merge policy is final

[Tor Bug Tracker & Wiki]

#29546: Update Maintaining.md after new merge policy is final
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  policy, doc, 041-deferred-20190530,  |  Actual Points:
  043-deferred-20200407, 044-should  |
Parent ID:   | Points:  0.3
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  policy, doc, 041-deferred-20190530, 043-should => policy, doc,
 041-deferred-20190530, 043-deferred-20200407, 044-should
 * milestone:  Tor: 0.4.3.x-final => Tor: 0.4.4.x-final


Comment:

 Looks like we'll do this in 0.4.4.

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

Re: [tor-bugs] #30745 [Core Tor/Tor]: Document disabled CI

[Tor Bug Tracker & Wiki]

#30745: Document disabled CI
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  043-should process tor-ci doc  |  Actual Points:
Parent ID: | Points:  0.2
 Reviewer: |Sponsor:
---+---
Changes (by teor):

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


Comment:

 We do not have any disabled CI any more.

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

Re: [tor-bugs] #32804 [Core Tor/Tor]: Travis CI hangs during compile or test

[Tor Bug Tracker & Wiki]

#32804: Travis CI hangs during compile or test
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:
 Keywords:  tor-ci-fail-rarely, tor-test, hang,  |  Actual Points:
  tor-ci |
Parent ID:  #29645   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  tor-ci-fail-rarely, tor-test, hang, tor-ci, 043-should => tor-
 ci-fail-rarely, tor-test, hang, tor-ci
 * milestone:  Tor: 0.4.3.x-final => Tor: 0.4.4.x-final


Comment:

 This appears to be a Travis infrastructure issue. It shouldn't block our
 releases.

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

Re: [tor-bugs] #30589 [Applications/Tor Browser]: Tor Browser on Windows does not support Hindi or Tamil.

[Tor Bug Tracker & Wiki]

#30589: Tor Browser on Windows does not support Hindi or Tamil.
-+-
 Reporter:  clash|  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-fingerprinting-fonts, tbb-   |  Actual Points:
  fingerprinting-os  |
Parent ID:  #18097   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by Sespahitra):

 Same issue on Win 10. None of the Indic languages render properly on
 latest TOR (9.0.8)

 https://en.wikipedia.org/wiki/Brahmic_scripts

 In above page for example the alphabets (Indic script) do not render
 (blocks) while numerals do render just fine.

 https://en.wikipedia.org/wiki/Brahmic_scripts#Consonants


 https://en.wikipedia.org/wiki/Brahmic_scripts#Numerals

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

Re: [tor-bugs] #33675 [Core Tor/Chutney]: Search microdescriptor files for relay ed25519 keys

[Tor Bug Tracker & Wiki]

#33675: Search microdescriptor files for relay ed25519 keys
---+---
 Reporter:  teor   |  Owner:  anuradha1904
 Type:  enhancement| Status:
   |  needs_revision
 Priority:  Medium |  Milestone:
Component:  Core Tor/Chutney   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ipv6, prop311, outreachy-ipv6  |  Actual Points:  0.2
Parent ID:  #33428 | Points:  0.5
 Reviewer:  teor   |Sponsor:  Sponsor55-can
---+---

Comment (by teor):

 I have spoken to anuradha1904 on IRC, and they sent me these chutney logs:
 {{{
 Bootstrap failed: 120 seconds
 Node status:
 test000a :  100, done , Done
 test001a :  100, done , Done
 test002r :  100, done , Done
 test003r :  100, done , Done
 test004r :  100, done , Done
 test005c :  100, done , Done
 test006c :  100, done , Done
 test007h :  100, done , Done
 test008h :  100, done , Done
 Published dir info:
 test000a :0, all nodes, md
 , Not in dir file
 test001a :0, all nodes, md
 , Not in dir file
 test002r :0, all nodes, md
 , Not in dir file
 test003r :0, all nodes, md
 , Not in dir file
 test004r :0, all nodes, md
 , Not in dir file
 }}}

 It looks like chutney is using the new md pattern, but it doesn't match
 any of the files.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33836 [Applications/GetTor]: Require Twisted 20.3.0 in gettor's requirements.txt

[Tor Bug Tracker & Wiki]

#33836: Require Twisted 20.3.0 in gettor's requirements.txt
-+
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/GetTor  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+
 Twisted has a HTTP request splitting vulnerability, GetTor is probably
 affected.

 Please update your requirements.txt to depend on Twisted 20.3.0 or later.
 (And any downstream packages.)

 The GitHub alert is:
 
https://github.com/torproject/gettor/network/alert/requirements.txt/Twisted/open

 The relevant CVEs are:
 CVE-2020-10108
 https://github.com/advisories/GHSA-h96w-mmrf-2h6v
 CVE-2020-10109
 https://github.com/advisories/GHSA-p5xh-vx83-mxcj

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

Re: [tor-bugs] #31533 [Applications/GetTor]: Require Twisted 19.7.0 because it fixes CVE-2019-12855 in jabber

[Tor Bug Tracker & Wiki]

#31533: Require Twisted 19.7.0 because it fixes CVE-2019-12855 in jabber
-+---
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/GetTor  |Version:
 Severity:  Normal   | Resolution:  not a bug
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by teor):

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


Comment:

 This bug is about gettor's  requirements.txt, not the Debian package.

 It looks like you don't need to worry about this bug, but I'm just about
 to file another one.

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

Re: [tor-bugs] #33807 [Applications/Tor Browser]: Namecoin eTLD patch conflicted with securedrop.tor.onion

[Tor Bug Tracker & Wiki]

#33807: Namecoin eTLD patch conflicted with securedrop.tor.onion
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  TorBrowserTeam202004R |  Actual Points:
Parent ID:| Points:
 Reviewer:  sysrqb|Sponsor:
--+--
Changes (by sysrqb):

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


Comment:

 The additional index information for
 `mobile/android/app/src/main/assets/publicsuffixlist` is unfortunate
 {{{
 -index 7f834b1..6874b40 100644
 +index 7f834b1a89bd..6874b4005ae3 100644
 }}}

 But I merge it with commit `5a2948b7195d1daa2b73b3cef2ed5507a922a76e`.

 Thanks!

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

Re: [tor-bugs] #33811 [Core Tor/Tor]: vanguards: syslog as logfile output destination

[Tor Bug Tracker & Wiki]

#33811: vanguards: syslog as logfile output destination
--+--
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  task  | Status:  closed
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:  vanguards |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by mikeperry):

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


Comment:

 Filed https://github.com/mikeperry-tor/vanguards/issues/56

 That bugtracker is canonical for vanguards stuff for now.

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

Re: [tor-bugs] #33815 [Core Tor/Tor]: vanguards with meek - do or don't?

[Tor Bug Tracker & Wiki]

#33815: vanguards with meek - do or don't?
--+--
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  vanguards |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by mikeperry):

 Q1-Q2) I need to look into this more, but meek-azure is not an obviously
 bad choice, if it still works. I am pretty sure it does not have cover
 traffic protections like obs4, and the azure cloud provider gains at least
 all capabilities of the local adversary, and may also gain some network
 adversary capabilities too. I also would have to double-check the specific
 meek-azure implementation to make sure you still get a properly
 authenticated connection to a guard node, or if there is another private
 bridge on the back-end (and if so, if that bridge is authenticated with a
 fingerprint).

 Q3) I was speaking about the protocol, not who ran the bridges (or who has
 access to Azure cloud or can compel them).

 Q4). For high volume onion services, adding additional local client
 traffic is unlikely to help much. I am also reluctant to make this
 recommendation in the general case, and that README is not the right place
 to go deep into the many different traffic analysis rabbit holes, because
 they are not strongly solved. The only reason that README goes as far as
 it does is because such a treatment is necessary to understand the effect
 and interaction of many options, protocols, other addons, and other
 components already provided by the Tor Project.

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

Re: [tor-bugs] #33815 [Core Tor/Tor]: vanguards with meek - do or don't?

[Tor Bug Tracker & Wiki]

#33815: vanguards with meek - do or don't?
--+--
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  task  | Status:  closed
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:  vanguards |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by mikeperry):

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


Comment:

 Such doc questions also belong here: https://github.com/mikeperry-
 tor/vanguards/issues. Specifically, https://github.com/mikeperry-
 tor/vanguards/issues/55 for doc updates.

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

Re: [tor-bugs] #33119 [Core Tor/Tor]: Resolve TROVE-2020-001

[Tor Bug Tracker & Wiki]

#33119: Resolve TROVE-2020-001
---+---
 Reporter:  nickm  |  Owner:  ahf
 Type:  defect | Status:  needs_review
 Priority:  High   |  Milestone:  Tor:
   |  0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  043-must   |  Actual Points:
Parent ID: | Points:  1-5?
 Reviewer:  asn, catalyst, dgoulet, nickm  |Sponsor:
---+---

Comment (by catalyst):

 I sent some preliminary comments to the list.

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

Re: [tor-bugs] #31634 [Core Tor/Tor]: Check .may_include order and tor subsystem init order are compatible

[Tor Bug Tracker & Wiki]

#31634: Check .may_include order and tor subsystem init order are compatible
--+
 Reporter:  teor  |  Owner:  nickm
 Type:  enhancement   | Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  diagnostics, practracker  |  Actual Points:  1
Parent ID:| Points:  2
 Reviewer:  teor  |Sponsor:
--+
Changes (by teor):

 * status:  needs_review => merge_ready


Comment:

 Replying to [comment:19 nickm]:
 > Relpath wasn't quite right -- it wants to look at the actual filesystem
 and we didn't want that.

 If you pass "start" to relpath(), it shouldn't look at the filesystem at
 all:
 "This is a path computation: the filesystem is not accessed to confirm the
 existence or nature of path or start."
 https://docs.python.org/3/library/os.path.html#os.path.relpath

 > I went with a harsher approach, and now CI is passing

 Great! The new code looks good.

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

Re: [tor-bugs] #33702 [Core Tor/Tor]: RSA_get0_d could not be located in the dynamic link library tor.exe

[Tor Bug Tracker & Wiki]

#33702: RSA_get0_d could not be located in the dynamic link library tor.exe
--+--
 Reporter:  ner0  |  Owner:  (none)
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 Replying to [comment:33 cypherpunks]:
 > Replying to gk:
 > > Sounds like a tor ticket now, no?
 > FWIW, tor runs in Tor Browser with Virtualized UAC Disabled when it's on
 Windows 10.

 Can you help me understand how Virtualised UAC relates to this issue?

 > According to #22450, they won't fix Windows issues anytime soon.

 We don't have a lot of Windows developers working on tor.
 So we prioritise issues based on their impact on users.

 I'm not sure that using a compatibility mode is actually a bug.
 Does it cause any user-visible issues?

 We'd love more people to help us patch and test Windows 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] #22450 [Core Tor/Tor]: Tor works in compatibility mode on Windows 7 and later

[Tor Bug Tracker & Wiki]

#22450: Tor works in compatibility mode on Windows 7 and later
-+-
 Reporter:  cypherpunks  |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Minor| Resolution:  wontfix
 Keywords:  tor-client, windows, win32 needs-|  Actual Points:
  windows|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

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


Comment:

 It's been a few years, and these compatibility modes isn't actually
 causing us any problems. So I'm going to close as "wontfix".

 If there are any bugs caused by these compatibility modes, please open a
 separate ticket, and reference this ticket.

 We don't actually package tor for Windows. (But Tor Browser does, as do
 other apps.)
 Packagers should feel free to distribute tor with a manifest, if they
 would like to.
 Let us know if there are any problems during testing.

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

Re: [tor-bugs] #33826 [Core Tor/Tor]: Add a testing-only option that turns off IPv4 extends

[Tor Bug Tracker & Wiki]

#33826: Add a testing-only option that turns off IPv4 extends
+
 Reporter:  teor|  Owner:  (none)
 Type:  enhancement | Status:  assigned
 Priority:  Medium  |  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  ipv6, prop311, testing  |  Actual Points:
Parent ID:  #33220  | Points:  1
 Reviewer:  |Sponsor:  Sponsor55-can
+
Changes (by teor):

 * owner:  teor => (none)
 * sponsor:  Sponsor55-must => Sponsor55-can


Comment:

 Useful, but not required. We can do similar checks using tor's logs.

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

Re: [tor-bugs] #30941 [Circumvention/BridgeDB]: Need better instructions for requesting bridges via email

[Tor Bug Tracker & Wiki]

#30941: Need better instructions for requesting bridges via email
-+-
 Reporter:  pili |  Owner:  phw
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  ux-team, s30-o22a2, anti-|  Actual Points:  1
  censorship-roadmap-2020Q1  |
Parent ID:  #31279   | Points:  1
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30
-+-
Changes (by phw):

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


Comment:

 Thanks,
 
[https://gitweb.torproject.org/bridgedb.git/commit/?h=develop=bca64964a255cf959489c7049c66e5eb70b5291c
 merged into develop].

 While inspecting BridgeDB's logs, I noticed that the autoresponder breaks
 when dealing with a quoted response from Gmail's web interface.  I filed
 #33835 to get that 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

[tor-bugs] #33835 [Circumvention/BridgeDB]: Gmail's quoted response confuses BridgeDB's email autoresponder

[Tor Bug Tracker & Wiki]

#33835: Gmail's quoted response confuses BridgeDB's email autoresponder
+---
 Reporter:  phw |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  |   Keywords:  s30-o22a2
Actual Points:  |  Parent ID:  #31279
   Points:  1   |   Reviewer:
  Sponsor:  Sponsor30-can   |
+---
 When replying to a BridgeDB email in Gmail's web interface, one ends up
 sending an email like this:
 {{{
 On Mon, Apr 6, 2020 at 2:12 PM  wrote:

 >
 > [This is an automated email.  Please do not reply.]
 >
 > Here are your bridges:
 >
 >   [redacted]
 >
 > Add these bridges to your Tor Browser by opening your browser
 > preferences, clicking on "Tor", and then adding them to the "Provide a
 > bridge" field.
 >
 > If these bridges are not what you need, reply to this email with one of
 > the following commands in the message body:
 >
 >   get bridges(Request unobfuscated Tor bridges.)
 >   get ipv6   (Request IPv6 bridges.)
 >   get transport TYPE (Request obfuscated bridges. Replace TYPE with
 > 'obfs4'.)
 >   get key(Get a copy of BridgeDB's public GnuPG key.)
 >
 >
 >

 --dde1a205a2a60f3e
 Content-Type: text/html; charset="UTF-8"
 Content-Transfer-Encoding: quoted-printable

 get transport obfs4On Mon, Apr 6, 2020 at 2:12 PM
 =
 mailto:brid...@torproject.org;>brid...@torproject.org
 wr=
 ote:
 [This is an automated email.=C2=A0 Please do not reply.]
 
 Here are your bridges:
 
 =C2=A0 [redacted]
 
 Add these bridges to your Tor Browser by opening your browser
 preferences, clicking on Tor, and then adding them to the
 =
 ;Provide a
 bridge field.
 
 If these bridges are not what you need, reply to this email with one
 of
 the following commands in the message body:
 
 =C2=A0 get bridges=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (Request
 unobfu=
 scated Tor bridges.)
 =C2=A0 get ipv6=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0
 =C2=A0(Requ=
 est IPv6 bridges.)
 =C2=A0 get transport TYPE=C2=A0 =C2=A0 =C2=A0(Request obfuscated bridges.
 R=
 eplace TYPE with obfs4.)
 =C2=A0 get key=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (Get
 =
 a copy of BridgeDBs public GnuPG key.)
 
 
 

 --dde1a205a2a60f3e--
 }}}

 BridgeDB correctly ignores the commands that start with `>` but it doesn't
 ignore the commands that are encoded in quoted-printable. BridgeDB's email
 parser ends up
 
[https://gitweb.torproject.org/bridgedb.git/tree/bridgedb/distributors/email/request.py?h=develop=bca64964a255cf959489c7049c66e5eb70b5291c#n87
 interpreting each line as command], ending in "get key", which raises an
 exception, resulting in BridgeDB sending no response at all.

 We should make sure that BridgeDB doesn't get confused by Gmail's quoted-
 printable response.

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

Re: [tor-bugs] #33809 [Applications/Tor Browser]: Fast-Forward Tor Browser Versions

[Tor Bug Tracker & Wiki]

#33809: Fast-Forward Tor Browser Versions
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #33808| Points:
 Reviewer:|Sponsor:
--+--

Comment (by brade):

 This is an interesting idea. Mark and I wonder if we can just add another
 version part instead of multiplying the last part of the Firefox version
 by 100, e.g., Tor Browser based on Firefox 90.0 would use 90.0.0, the
 first TB patch would use 90.0.1, etc.  Another example: Tor Browser with a
 third patch and based on Firefox 91.0b1 would use 91.0b1.3.  We are not
 sure which scheme is the best choice, but it looks like Mozilla's version
 comparison code can handle any number of version parts.

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

Re: [tor-bugs] #25102 [Applications/Tor Browser]: Add script to sign nightly build mar files, generate update-responses xml and publish the new version

[Tor Bug Tracker & Wiki]

#25102: Add script to sign nightly build mar files, generate update-responses 
xml
and publish the new version
-+-
 Reporter:  boklm|  Owner:  boklm
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-rbm, tbb-update, |  Actual Points:  4.5
  TorBrowserTeam202004R  |
Parent ID:  #18867   | Points:  3.5
 Reviewer:  gk   |Sponsor:
-+-

Comment (by gk):

 Replying to [comment:20 boklm]:
 > GeKo was asking on IRC why we are hardcoding the version of martools we
 are using for signing the mar files, and why we are not just using the
 martools from the nightly builds.
 >
 > The reason to do that is to isolate the signing VM from the build VM.
 The nightly setup looks like this:
 > - the nightly build VM is building the nightly, and makes the builds
 available through http on an onion address. The nightly build is using the
 git master branch from several components, which means that an attacker
 who manages to get root access to the git server would also be able to
 access the build VM.

 Hey, another attacker is coming out of the weeds, good! Keep 'em coming.
 :)

 > - the signing VM fetches the mar files from the build VM through the
 onion address, sign them (using the martools from a stable Tor Browser
 version), and upload the signed mars to
 https://nightlies.tbb.torproject.org/ (using an ssh key). If we were using
 the martools from the nightly build, an attacker who got access to the
 build VM could get access to the signing VM too and steal the signing key,
 and the ssh key to upload malicious mar files to
 nightlies.tbb.torproject.org.
 >
 > So I think it is useful to try to keep the build and signing VMs
 separate. Unfortunately this is not enough to avoid the case where an
 attacker uses their access to the build VM to produce malicious builds for
 nightly users. To mitigate this I think what we can do:
 > - reinstall the build VM frequently. Keeping build and signing VMs
 separate means we don't have to rotate mar signing and ssh keys at the
 same time.
 > - require all commits (or at least the top commit on the master branch)
 to be signed
 > - have a second build VM, and check that the builds are matching before
 signing them.

 Thanks for writing this up, really appreciated. Yes, the last three steps
 are good things to do. Could you open bugs for the last two (signed
 commits which we probably should enforce with a git hook and some means on
 the nightly side to only start building if commits are properly signed;
 and the second build VM) items so we don't forget about them?

 Unfortunately, I fear the issue with mar signing tools breaking will
 happen in situations where we need that least, that is during transition
 to a new major release once we do our first nightly builds with the new
 code. In that moment we do not want to deal with broken mar signing tools,
 too, so that the whole team is blocked on that. So, how about the
 following:

 a) We do use a hardcoded martools version as you propose, but

 b) if that fails, e.g. due to a new major upcoming release, we use the
 martools that gets shipped with the nightly so that other folks on the
 team can work on that new upcoming major release while someone from the
 team fixes the mar signing issue (the former do not get blocked anymore on
 the latter) (we can then rotate the signing key afterwards and set the VMs
 newly up to be on the safe 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] #32864 [Community/Relays]: Reproduce Arthur's exit failures and then contact or badexit the relays

[Tor Bug Tracker & Wiki]

#32864: Reproduce Arthur's exit failures and then contact or badexit the relays
-+-
 Reporter:  arma |  Owner:  gk
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Community/Relays |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-health, network-health-  |  Actual Points:  3.5
  roadmap-2020Q1, GeorgKoppen202003  |
Parent ID:   | Points:  2
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by dgoulet):

 * status:  needs_review => merge_ready


Comment:

 Good to go.

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

Re: [tor-bugs] #29399 [Internal Services/Tor Sysadmin Team]: Retire host and services for tordnsel and check (chiwui)

[Tor Bug Tracker & Wiki]

#29399: Retire host and services for tordnsel and check (chiwui)
-+-
 Reporter:  ln5  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 following https://help.torproject.org/tsa/howto/retire-a-host/

  1. announced here and elsewhere numerous times before
  2. removed from nagios
  3. stopped chiwui in the ganeti cluster

 Will wait a few days to see if things blow up. Service is now stopped, and
 the rest of the retirement process will follow soon.

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

Re: [tor-bugs] #29399 [Internal Services/Tor Sysadmin Team]: Retire host and services for tordnsel and check (chiwui)

[Tor Bug Tracker & Wiki]

#29399: Retire host and services for tordnsel and check (chiwui)
-+-
 Reporter:  ln5  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * status:  assigned => accepted
 * owner:  irl => anarcat


Comment:

 great, will start the retirement process now.

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

Re: [tor-bugs] #33834 [Internal Services/Tor Sysadmin Team]: nevii IP address change planned for Ganeti migration

[Tor Bug Tracker & Wiki]

#33834: nevii IP address change planned for Ganeti migration
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Major| Resolution:
 Keywords:  tpa-roadmap-march|  Actual Points:
Parent ID:  #33082   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 first test adoption tells me:

 {{{
 Mon Apr  6 19:24:35 2020  - INFO: Chose IP 49.12.57.130 from network gnt-
 fsn13-02
 }}}

 i also had a crash in `renumber-instances` because the new network (`gnt-
 fsn13-02`) did not have an IPv6 configuration. i hacked around that
 problem by reassigning the same /64 than inside the `gnt-fsn` network, but
 that seems totally gross right now. i also improved error handling (in
 `cd31b77`) so that it would warn the user instead of just crashing on such
 situations in the future.

 still, it worked as far as ganeti/debian is concerned and yielded a diff
 like this:

 {{{
 --- /mnt/etc/network/interfaces.bak 2020-04-06 19:30:55.884709093
 +
 +++ /mnt/etc/network/interfaces 2020-04-06 19:30:57.076699317 +
 @@ -6,11 +6,11 @@
  iface lo inet loopback

  # The primary network interface
 -allow-hotplug eth0
 +auto eth0
  iface eth0 inet static
 -address 138.201.212.229/28
 -gateway 138.201.212.225
 +address 49.12.57.130/27
 +gateway 49.12.57.129
  iface eth0 inet6 static
  accept_ra 0
 -address 2a01:4f8:172:39ca:0:dad3:5:1/96
 -gateway 2a01:4f8:172:39ca:0:dad3:0:1
 +address 2a01:4f8:fff0:4f:266:37ff:febd:dd6/64
 +gateway 2a01:4f8:fff0:4f::1
 copying /mnt/etc/hosts to /mnt/etc/hosts.bak on fsn-node-05.torproject.org
 rewriting host file /mnt/etc/hosts on 
 --- /mnt/etc/hosts.bak  2020-04-06 19:31:00.600670406 +
 +++ /mnt/etc/hosts  2020-04-06 19:31:02.688653278 +
 @@ -3,7 +3,7 @@
  ##

  127.0.0.1   localhost
 -138.201.212.229nevii.torproject.org nevii
 +49.12.57.130 nevii.torproject.org nevii

  # The following lines are desirable for IPv6 capable hosts
  ::1 localhost ip6-localhost ip6-loopback
 @@ -12,3 +12,4 @@
  ff02::1 ip6-allnodes
  ff02::2 ip6-allrouters
  ff02::3 ip6-allhosts
 +2a01:4f8:fff0:4f:266:37ff:febd:dd6 nevii.torproject.org nevii
 }}}

 ipv6 networking seems to work, so i think we're all clear for a live
 migration next.

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

Re: [tor-bugs] #33082 [Internal Services/Tor Sysadmin Team]: decomission kvm3 AKA macrum, 7 VMs to migrate

[Tor Bug Tracker & Wiki]

#33082: decomission kvm3 AKA macrum, 7 VMs to migrate
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tpa-roadmap-march|  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Old description:

> * [ ] crm-ext-01.torproject.org (part of #32198) test server ready (but
> shutdown) at `116.202.120.186`
>  * [ ] crm-int-01.torproject.org (also part of #32198) test server ready
> (but shutdown) `116.202.120.190`
>  * [x] forrestii.torproject.org (fpcentral, #33729) server migrated to
> `116.202.120.185`
>  * [ ] nevii.torproject.org (DNS master) - not migrated, ran out of IP,
> opened Ticket#2020032503025825 with hetzner to followup
>  * [x] rude.torproject.org (RT) - migrated to `116.202.120.187`
>  * [x] troodi.torproject.org (Trac, #33731) - migrated to
> `116.202.120.188`
>  * [x] vineale.torproject.org (gitweb, #33730) - done, new IP is
> `116.202.120.189`
>
> The CRM machines might have already been migrated by the time we start
> this, see #32198.
>
> Will require a new Ganeti node (#33083).

New description:

 * [ ] crm-ext-01.torproject.org (part of #32198) test server ready (but
 shutdown) at `116.202.120.186`
  * [ ] crm-int-01.torproject.org (also part of #32198) test server ready
 (but shutdown) `116.202.120.190`
  * [x] forrestii.torproject.org (fpcentral, #33729) server migrated to
 `116.202.120.185`
  * [ ] nevii.torproject.org (DNS master) - #33834
  * [x] rude.torproject.org (RT) - migrated to `116.202.120.187`
  * [x] troodi.torproject.org (Trac, #33731) - migrated to
 `116.202.120.188`
  * [x] vineale.torproject.org (gitweb, #33730) - done, new IP is
 `116.202.120.189`

 The CRM machines might have already been migrated by the time we start
 this, see #32198.

 Will require a new Ganeti node (#33083).

--

Comment (by anarcat):

 create a ticket for nevii, as it's more complicated than the others

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

Re: [tor-bugs] #33834 [Internal Services/Tor Sysadmin Team]: nevii IP address change planned for Ganeti migration

[Tor Bug Tracker & Wiki]

#33834: nevii IP address change planned for Ganeti migration
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Major| Resolution:
 Keywords:  tpa-roadmap-march|  Actual Points:
Parent ID:  #33082   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * owner:  tpa => anarcat
 * status:  new => accepted


Comment:

 this is the current DNS landscape:

  * ns1.torproject.org, 38.229.72.12, fallax.torproject.org, cymru, in
 Puppet
  * ns2, 95.216.159.212, hetzner-hel1-02.torproject.org, hetzner cloud, in
 Puppet
  * ns3, 95.216.159.212, *also* hetzner-hel1-02.torproject.org.
  * ns4, 94.130.28.203, neriniflorum.torproject.org., kvm4@hetzner, in
 puppet
  * nsp.dnsnode.net, 194.58.198.32, DNSNODE, needs manual configuration

 So I will, in theory, only need to update the latter nameserver by hand:
 all others should follow happily without a problem.

 That is, of course, unless some other server hardcodes the IP address, but
 I couldn't find anything nasty in /etc so far so we should be good.

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

[tor-bugs] #33834 [Internal Services/Tor Sysadmin Team]: nevii IP address change planned for Ganeti migration

[Tor Bug Tracker & Wiki]

#33834: nevii IP address change planned for Ganeti migration
-+-
 Reporter:  anarcat  |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin   |Version:
  Team   |   Keywords:  tpa-
 Severity:  Major|  roadmap-march
Actual Points:   |  Parent ID:  #33082
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 I'm migrating nevii, our primary DNS server, to the Ganeti cluster. this
 implies an IP address change, and therefore all sorts of shenanigans.

 after inspection, the changes are fairly "minimal": glue records should
 not change as the primary DNS server is not publicly exposed. we will need
 to change all secondary servers, but most of those are in Puppet.

 we did have to request extra address space from Hetzner, but this was done
 in ticket 2020032503025825.

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

Re: [tor-bugs] #32476 [Applications/Tor Browser]: Support Launching TorService Using JNI

[Tor Bug Tracker & Wiki]

#32476: Support Launching TorService Using JNI
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  Android, tbb-mobile, |  Actual Points:
  TorBrowserTeam202004   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by sisbell):

 This is still going to be supported. The prerequisite is that we get all
 the issues related to getting tor built in tbb. Once that is done, we can
 either patch the tor project or commit needed changes directly to support
 JNI.

 #28704

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

Re: [tor-bugs] #32476 [Applications/Tor Browser]: Support Launching TorService Using JNI

[Tor Bug Tracker & Wiki]

#32476: Support Launching TorService Using JNI
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  Android, tbb-mobile, |  Actual Points:
  TorBrowserTeam202004   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by eighthave):

 Personally, I have no funding to work on Tor things at the moment.  But I
 can say that we have a working build based on this work.  And we'd like to
 see this approach merged and adopted.

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

Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server

[Tor Bug Tracker & Wiki]

#33824: relay measures low / high on same network and same server
---+
 Reporter:  niftybunny |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #33775 | Points:
 Reviewer: |Sponsor:
---+

Comment (by juga):

 Thanks for the info.

 i'm adding mostly the same info but in csv and ordered by name, then ip,
 since i wanted to check whether some ips change ip, which would make them
 more likely to get excluded or bw not updated so often.

 Something that would be even more useful if it's easy for you, is to get
 that data directly from the bandwidth files, including info about which is
 the bwauth that publish it, the date/time it was published and all the
 bandwidth values.

 But i could also calculate it myself or might not be really needed.

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

Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server

[Tor Bug Tracker & Wiki]

#33824: relay measures low / high on same network and same server
---+
 Reporter:  niftybunny |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #33775 | Points:
 Reviewer: |Sponsor:
---+
Changes (by juga):

 * Attachment "nifty_ordered.csv" added.


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

Re: [tor-bugs] #33776 [Internal Services/Tor Sysadmin Team]: Please change email forwarding for jon@

[Tor Bug Tracker & Wiki]

#33776: Please change email forwarding for jon@
-+-
 Reporter:  ewyatt   |  Owner:  anarcat
 Type:  task | Status:
 |  needs_revision
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * status:  accepted => needs_revision


Comment:

 i changed jon@ but that email is also on a bunch of other aliases, i asked
 erin in private what to do about those.

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

Re: [tor-bugs] #33760 [Applications/Tor Browser]: Update rbm.conf to match NDK 21

[Tor Bug Tracker & Wiki]

#33760: Update rbm.conf to match NDK 21
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, Android, |  Actual Points:
  TorBrowserTeam202004R  |
Parent ID:  #33184   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by sisbell):

 Updated CC variable to point to latest NDK clang

 https://github.com/sisbell/tor-browser-build/commits/bug-33760a

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

Re: [tor-bugs] #30199 [Applications/Tor Browser]: tor-android-service: Review 2019/04/16

[Tor Bug Tracker & Wiki]

#30199: tor-android-service: Review 2019/04/16
-+-
 Reporter:  sysrqb   |  Owner:  sisbell
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-8.5, |  Actual Points:
  TorBrowserTeam202004   |
Parent ID:   | Points:  0.5
 Reviewer:  sysrqb   |Sponsor:
-+-
Changes (by boklm):

 * cc: tbb-team (added)


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

Re: [tor-bugs] #30199 [Applications/Tor Browser]: tor-android-service: Review 2019/04/16

[Tor Bug Tracker & Wiki]

#30199: tor-android-service: Review 2019/04/16
-+-
 Reporter:  sysrqb   |  Owner:  sisbell
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-8.5, |  Actual Points:
  TorBrowserTeam202004   |
Parent ID:   | Points:  0.5
 Reviewer:  sysrqb   |Sponsor:
-+-
Changes (by pili):

 * owner:  tbb-team => sisbell
 * status:  needs_revision => assigned


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

Re: [tor-bugs] #33298 [Applications/Tor Browser]: HTTP onion sites do not give a popup warning when submiting form data to non-onion HTTP sites

[Tor Bug Tracker & Wiki]

#33298: HTTP onion sites do not give a popup warning when submiting form data to
non-onion HTTP sites
---+---
 Reporter:  pospeselr  |  Owner:  pospeselr
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ux-team, TorBrowserTeam202007  |  Actual Points:
Parent ID:  #30025 | Points:
 Reviewer: |Sponsor:
   |  Sponsor27-must
---+---
Changes (by pili):

 * keywords:  ux-team, TorBrowserTeam202004 => ux-team, TorBrowserTeam202007


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

Re: [tor-bugs] #33671 [Applications/Tor Browser]: Update "Get Involved" url in about:tor

[Tor Bug Tracker & Wiki]

#33671: Update "Get Involved" url in about:tor
--+--
 Reporter:  ggus  |  Owner:  mcs
 Type:  enhancement   | Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam202004  |  Actual Points:
Parent ID:| Points:  0.2
 Reviewer:  acat  |Sponsor:
--+--
Changes (by mcs):

 * status:  new => assigned
 * owner:  tbb-team => mcs
 * points:   => 0.2
 * cc: tbb-team (added)
 * reviewer:   => acat


Comment:

 Kathy and I will take this ticket.

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

Re: [tor-bugs] #33414 [Core Tor/Tor]: Split router.c, and disable it (mostly) when building without relay support.

[Tor Bug Tracker & Wiki]

#33414: Split router.c, and disable it (mostly) when building without relay
support.
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-design, network-team-roadmap-|  Actual Points:  0.5
  2020Q1, 043-deferred   |
Parent ID:  #31851   | Points:  0.5
 Reviewer:  catalyst |Sponsor:
-+-
Changes (by catalyst):

 * status:  needs_review => needs_revision


Comment:

 Mostly looks good!

 Replying to [comment:8 teor]:
 > >  I've answered the comment about the missing lock: that lock is only
 used to protect onion keys, which clients don't have.
 >
 > Thanks!
 >
 > Can we add some comments that document this information?
 +1
 > init_keys_common() and init_keys_client() don't have function comments,
 and init_keys_common() is a really confusing name for a relay-only
 function.
 It looks like `init_keys_client()` has a function comment. (It was
 previously in the header file.) I'm not sure I understand how
 `init_keys_common()` is a relay-only function, though. It looks like
 `init_keys_client()` calls it?

 OK I looked a bit more closely and it's more confusing than I thought. I
 think it really could use better documentation in comments.

 The `init_keys_common()` definition in router.c is not built on clients,
 because router.c is not built on clients. However, clientkey.c includes
 router.h, which has a macro to stub out `init_keys_common()`. Also oddly
 enough, these patches change `init_keys_common()` to remove the `static`
 qualifier, which seems unnecessary to change?

 Or maybe rewrite things so that the naming isn't so confusing?

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

Re: [tor-bugs] #33760 [Applications/Tor Browser]: Update rbm.conf to match NDK 21

[Tor Bug Tracker & Wiki]

#33760: Update rbm.conf to match NDK 21
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, Android, |  Actual Points:
  TorBrowserTeam202004R  |
Parent ID:  #33184   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-mobile, Android => tbb-mobile, Android,
 TorBrowserTeam202004R


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

Re: [tor-bugs] #33833 [Applications/Tor Browser]: Upgrade Rust To Use Android NDK 21

[Tor Bug Tracker & Wiki]

#33833: Upgrade Rust To Use Android NDK 21
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, Android, |  Actual Points:  .5
  TorBrowserTeam202004R  |
Parent ID:  #33184   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-mobile, Android => tbb-mobile, Android,
 TorBrowserTeam202004R


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

Re: [tor-bugs] #33559 [Applications/Tor Browser]: Update tor-android-service To Use Updated Android Toolchain

[Tor Bug Tracker & Wiki]

#33559: Update tor-android-service To Use Updated Android Toolchain
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, Android, |  Actual Points:  .5
  TorBrowserTeam202004R  |
Parent ID:  #33184   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor58-must
-+-
Changes (by gk):

 * keywords:  tbb-mobile, Android => tbb-mobile, Android,
 TorBrowserTeam202004R


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

Re: [tor-bugs] #33561 [Applications/Tor Browser]: Upgrade openssl to use Android NDK 21

[Tor Bug Tracker & Wiki]

#33561: Upgrade openssl to use Android NDK 21
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, Android, |  Actual Points:
  TorBrowserTeam202004R  |
Parent ID:  #33184   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor58-must
-+-
Changes (by gk):

 * keywords:  tbb-mobile, Android => tbb-mobile, Android,
 TorBrowserTeam202004R


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

Re: [tor-bugs] #33564 [Applications/Tor Browser]: Upgrade ZSTD to use Android NDK 21

[Tor Bug Tracker & Wiki]

#33564: Upgrade ZSTD to use Android NDK 21
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, Android, |  Actual Points:  .1
  TorBrowserTeam202004R  |
Parent ID:  #33184   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor58-must
-+-
Changes (by gk):

 * keywords:  tbb-mobile, Android => tbb-mobile, Android,
 TorBrowserTeam202004R


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

Re: [tor-bugs] #29686 [Circumvention/BridgeDB]: filenames conflict on case-insensitive filesystems

[Tor Bug Tracker & Wiki]

#29686: filenames conflict on case-insensitive filesystems
--+---
 Reporter:  catalyst  |  Owner:  phw
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Circumvention/BridgeDB|Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  ex-sponsor-19, s30-o24a4  |  Actual Points:  0.7
Parent ID:  #31281| Points:  0.5
 Reviewer:  cohosh|Sponsor:  Sponsor30-can
--+---
Changes (by phw):

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


Comment:

 Replying to [comment:6 cohosh]:
 > Only one minor comment:
 > - It looks like the `Bridge` class
 
[https://github.com/NullHypothesis/bridgedb/compare/develop...defect/29686?expand=1
 #diff-8139a954d554326b0bd0a384205521f3R297 here] should be in
 `bridgedb.bridges.Bridge`? There's not `Bridge` class in
 `bridgedb.bridgerings`.
 >
 > Otherwise, this looks good to me!
 [[br]]
 Oh, good catch! I fixed the issue and
 
[https://gitweb.torproject.org/bridgedb.git/commit/?h=develop=7afbe7e2866c7628bc5e40b15618105843486c80
 merged branch defect/29686].

 This fix took a bit longer than expected because it broke a unit test that
 seems to have relied on the alphabetic ordering of unit tests – which we
 changed in this patch.
 
[https://gitweb.torproject.org/user/phw/bridgedb.git/commit/?h=develop=8105032e2ab876d1c7d31471b828a0690f2bf6f3
 Giving BridgeDB a bit more time to start] should have fixed this issue.

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

Re: [tor-bugs] #33556 [Applications/Tor Browser]: Add TBB project for android-components

[Tor Bug Tracker & Wiki]

#33556: Add TBB project for android-components
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, Android, |  Actual Points:
  TorBrowserTeam202004R  |
Parent ID:  #33184   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor58-must
-+-
Changes (by gk):

 * keywords:  tbb-mobile, Android => tbb-mobile, Android,
 TorBrowserTeam202004R


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

Re: [tor-bugs] #33558 [Applications/Tor Browser]: Update TOPL To Use Updated Android Toolchain

[Tor Bug Tracker & Wiki]

#33558: Update TOPL To Use Updated Android Toolchain
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, Android, |  Actual Points:  .5
  TorBrowserTeam202004R  |
Parent ID:  #33184   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor58-must
-+-
Changes (by gk):

 * keywords:  tbb-mobile, Android => tbb-mobile, Android,
 TorBrowserTeam202004R


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

Re: [tor-bugs] #33801 [Applications/Tor Browser]: Upgrade Go Project to use new Android Toolchain

[Tor Bug Tracker & Wiki]

#33801: Upgrade Go Project to use new Android Toolchain
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, Android, |  Actual Points:  .1
  TorBrowserTeam202004R  |
Parent ID:  #33184   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-mobile, Android => tbb-mobile, Android,
 TorBrowserTeam202004R


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

Re: [tor-bugs] #33469 [Core Tor/Tor]: INTERNAL ERROR: Raw assertion failed at src/lib/malloc/map_anon.c:239: lock_result == 0

[Tor Bug Tracker & Wiki]

#33469: INTERNAL ERROR: Raw assertion failed at src/lib/malloc/map_anon.c:239:
lock_result == 0
-+-
 Reporter:  m95d |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:  0.4.2.6
 Severity:  Normal   | Resolution:
 Keywords:  malloc map_anon windows  |  Actual Points:
  042-backport   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  malloc map_anon windows 042-backport 043-must => malloc
 map_anon windows 042-backport
 * milestone:  Tor: 0.4.3.x-final => Tor: 0.4.4.x-final


Comment:

 Okay. We should fix this if we can, but if it _only_ affects windows
 server 2003, then it is not critical for 0.4.3.  (MS hasn't supported
 WS2003 since 2015)

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

Re: [tor-bugs] #33804 [Core Tor/Tor]: Defer "PreferIPv6 by default" to 0.4.4

[Tor Bug Tracker & Wiki]

#33804: Defer "PreferIPv6 by default" to 0.4.4
+--
 Reporter:  teor|  Owner:  dgoulet
 Type:  defect  | Status:  assigned
 Priority:  Very High   |  Milestone:  Tor:
|  0.4.3.x-final
Component:  Core Tor/Tor|Version:  Tor:
|  0.4.3.1-alpha
 Severity:  Normal  | Resolution:
 Keywords:  tor-dns torsocks ipv6 043-must  |  Actual Points:
Parent ID:  #33796  | Points:  0.1
 Reviewer:  teor|Sponsor:
+--
Changes (by nickm):

 * priority:  Medium => Very High


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

Re: [tor-bugs] #33833 [Applications/Tor Browser]: Upgrade Rust To Use Android NDK 21

[Tor Bug Tracker & Wiki]

#33833: Upgrade Rust To Use Android NDK 21
--+--
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, Android   |  Actual Points:  .5
Parent ID:  #33184| Points:
 Reviewer:|Sponsor:
--+--
Changes (by sisbell):

 * status:  new => needs_review
 * actualpoints:   => .5


Comment:

 gcc is no longer supported in the Android NDK so I moved this to use
 clang.

 Rust was no longer able to find the ar command. This occurs since the
 clang executable has the android API level in the file name.

 {{{
 i686-linux-android29-clang
 }}}
 Rust tries to use the name of the clang command, with API, to infer the
 target as

 {{{
 i686-linux-android29-ar
 }}}

 However, ar is

 {{{
 i686-linux-android-ar
 }}}

 I add the correct ar in options to solve this issue.

 There is an oddity for arm, which doesn't occur in other platform
 variants. As ar is


 {{{
 arm-linux-androideabi-ar
 }}}

 while clang is

 {{{
 armv7a-linux-androideabi29-clang
 }}}


 so arm ar doesn't contain any portion of the correct host. So the options
 are a little different here.

 https://github.com/sisbell/tor-browser-build/commits/bug-33833

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33833 [Applications/Tor Browser]: Upgrade Rust To Use Android NDK 21

[Tor Bug Tracker & Wiki]

#33833: Upgrade Rust To Use Android NDK 21
--+
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-mobile,
  |  Android
Actual Points:|  Parent ID:  #33184
   Points:|   Reviewer:
  Sponsor:|
--+
 Upgrade rust to use latest toolchain

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

Re: [tor-bugs] #33626 [Applications/Tor Browser]: Add TBB project for GeckoView

[Tor Bug Tracker & Wiki]

#33626: Add TBB project for GeckoView
--+
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, Android   |  Actual Points:
Parent ID:  #33184| Points:
 Reviewer:|Sponsor:  Sponsor58-must
--+
Changes (by sisbell):

 * cc: acat (added)


Comment:

 I'm working off of this branch

 https://github.com/acatarineu/tor-browser/commits/33533+2

 I get various errors around config options in the 'mach build'


 {{{
 mozbuild.configure.ConfigureError: `MOZ_ANDROID_DOWNLOAD_CONTENT_SERVICE`,
 emitted from `/var/tmp/build/firefox-
 997e76c0a91b/mobile/android/torbrowser.configure` line 13,
 }}}

 OR

 {{{
  0:01.14 mozbuild.configure.options.InvalidOptionError: Unknown option:
 --disable-signmar
 }}}

 It looks like we still need patches for AppConfig. I'm working through
 these issues to decide which we need (geckoview specific) and which ones
 would go to the latest fenix app.

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

Re: [tor-bugs] #33832 [Core Tor/sbws]: For relays that change ip, only the measurements with the last ip are kept

[Tor Bug Tracker & Wiki]

#33832: For relays that change ip, only the measurements with the last ip are 
kept
---+---
 Reporter:  juga   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  sbws: 1.1.x-final
Component:  Core Tor/sbws  |Version:  sbws: 1.1.0
 Severity:  Normal | Resolution:
 Keywords:  sbws-roadmap   |  Actual Points:
Parent ID:  #33121 | Points:
 Reviewer: |Sponsor:
---+---

Comment (by juga):

 As commented in
 
https://gitweb.torproject.org/sbws.git/tree/sbws/lib/resultdump.py?h=maint-1.1#n111

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

Re: [tor-bugs] #33559 [Applications/Tor Browser]: Update tor-android-service To Use Updated Android Toolchain

[Tor Bug Tracker & Wiki]

#33559: Update tor-android-service To Use Updated Android Toolchain
--+
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, Android   |  Actual Points:  .5
Parent ID:  #33184| Points:
 Reviewer:|Sponsor:  Sponsor58-must
--+
Changes (by sisbell):

 * cc: eighthave (removed)
 * actualpoints:   => .5


Comment:

 Upgraded tor-android-service to use new gradle and android dependencies.
 tbb tor-android-service projects gradle dependencies and versions.

 https://github.com/sisbell/tor-browser-build/commits/bug-33559

 https://github.com/sisbell/tor-android-service/commits/bug-33559

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

Re: [tor-bugs] #33559 [Applications/Tor Browser]: Update tor-android-service To Use Updated Android Toolchain

[Tor Bug Tracker & Wiki]

#33559: Update tor-android-service To Use Updated Android Toolchain
--+
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, Android   |  Actual Points:  .5
Parent ID:  #33184| Points:
 Reviewer:|Sponsor:  Sponsor58-must
--+
Changes (by sisbell):

 * status:  new => needs_review


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

Re: [tor-bugs] #33119 [Core Tor/Tor]: Resolve TROVE-2020-001

[Tor Bug Tracker & Wiki]

#33119: Resolve TROVE-2020-001
---+---
 Reporter:  nickm  |  Owner:  ahf
 Type:  defect | Status:  needs_review
 Priority:  High   |  Milestone:  Tor:
   |  0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  043-must   |  Actual Points:
Parent ID: | Points:  1-5?
 Reviewer:  asn, catalyst, dgoulet, nickm  |Sponsor:
---+---
Changes (by dgoulet):

 * reviewer:   => asn, catalyst, dgoulet, nickm


Comment:

 Awaiting comments from most of the network team. People in the Reviewer
 field have not commented.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33832 [Core Tor/sbws]: For relays that change ip, only the measurements with the last ip are kept

[Tor Bug Tracker & Wiki]

#33832: For relays that change ip, only the measurements with the last ip are 
kept
---+---
 Reporter:  juga   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  sbws: 1.1.x-final
Component:  Core Tor/sbws  |Version:  sbws: 1.1.0
 Severity:  Normal |   Keywords:  sbws-roadmap
Actual Points: |  Parent ID:  #33121
   Points: |   Reviewer:
  Sponsor: |
---+---
 which makes those relays more likely to don't be "eligible" cause don't
 have enough results and therefore, sbws voting in less relays.

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

Re: [tor-bugs] #33778 [Core Tor/Tor]: TestingTorNetwork options in the man page are out of date

[Tor Bug Tracker & Wiki]

#33778: TestingTorNetwork options in the man page are out of date
--+
 Reporter:  opara |  Owner:  (none)
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  doc   |  Actual Points:
Parent ID:| Points:
 Reviewer:  asn   |Sponsor:
--+
Changes (by dgoulet):

 * reviewer:   => asn


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

Re: [tor-bugs] #33679 [Core Tor/Tor]: Make sure every address function that takes for_listening supports IPv6

[Tor Bug Tracker & Wiki]

#33679: Make sure every address function that takes for_listening supports IPv6
-+-
 Reporter:  teor |  Owner:
 |  MrSquanchee
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  extra-review, prop312, ipv6, |  Actual Points:  0.3
  outreachy-ipv6, network-team-roadmap-2020Q1|
Parent ID:  #33049   | Points:  0.5
 Reviewer:  dgoulet  |Sponsor:
 |  Sponsor55-must
-+-
Changes (by dgoulet):

 * reviewer:   => dgoulet


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

Re: [tor-bugs] #33558 [Applications/Tor Browser]: Update TOPL To Use Updated Android Toolchain

[Tor Bug Tracker & Wiki]

#33558: Update TOPL To Use Updated Android Toolchain
--+
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, Android   |  Actual Points:  .5
Parent ID:  #33184| Points:
 Reviewer:|Sponsor:  Sponsor58-must
--+
Changes (by sisbell):

 * cc: eighthave (removed)
 * status:  new => needs_review
 * actualpoints:   => .5


Comment:

 I made changes to TOPL project to use latest gradle and android
 dependencies. It required removing the publishing and jar sources section
 (which we don't use). The ttb tor-onion-proxy library uses this branched
 version of TOPL and upgrades gradle version. Regenerated gradle
 dependencies.

 https://github.com/sisbell/tor-browser-build/commits/bug-33558

 https://github.com/sisbell/Tor_Onion_Proxy_Library/commits/bug-33558

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

Re: [tor-bugs] #33342 [Applications/Tor Browser]: Disconnect search addon causes error at startup

[Tor Bug Tracker & Wiki]

#33342: Disconnect search addon causes error at startup
--+
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  defect| Status:
  |  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-9.5a9, TorBrowserTeam202004R  |  Actual Points:  0.5
Parent ID:| Points:
 Reviewer:  brade,mcs |Sponsor:
--+
Changes (by pili):

 * keywords:  TorBrowserTeam202003R, tbb-9.5a9, TorBrowserTeam202004 =>
 tbb-9.5a9, TorBrowserTeam202004R


Comment:

 I'm a bit confused whether this is reviewed or it needs revisions or can
 be closed (I see a patch was merged already.)

 Can someone who knows better please update :) Thanks!

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

Re: [tor-bugs] #33801 [Applications/Tor Browser]: Upgrade Go Project to use new Android Toolchain

[Tor Bug Tracker & Wiki]

#33801: Upgrade Go Project to use new Android Toolchain
--+--
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, Android   |  Actual Points:  .1
Parent ID:  #33184| Points:
 Reviewer:|Sponsor:
--+--
Changes (by sisbell):

 * status:  new => needs_review
 * actualpoints:   => .1


Comment:

 We don't need to specify the API_VERSION for android since this is
 included in the clang command (shell variant for android)

 !https://github.com/sisbell/tor-browser-build/commits/bug-33801

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

Re: [tor-bugs] #32624 [Applications/Tor Browser]: localStorage is not shared between tabs

[Tor Bug Tracker & Wiki]

#32624: localStorage is not shared between tabs
-+-
 Reporter:  nDe15o   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff78-esr-will-have,  |  Actual Points:
  TorBrowserTeam202007   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by pili):

 * keywords:  ff78-esr-will-have, TorBrowserTeam202004 => ff78-esr-will-
 have, TorBrowserTeam202007


Comment:

 Moving to July

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

Re: [tor-bugs] #33590 [Core Tor/sbws]: total consensus weight too high

[Tor Bug Tracker & Wiki]

#33590: total consensus weight too high
---+---
 Reporter:  starlight  |  Owner:  (none)
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:  sbws: unspecified
Component:  Core Tor/sbws  |Version:  sbws: 1.1.0
 Severity:  Normal | Resolution:  duplicate
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by juga):

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


Comment:

 Moving the info of this ticket to #33590 cause i'm more convinced it's a
 duplicated

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

Re: [tor-bugs] #33076 [Metrics/Analysis]: Graph onionperf and consensus information from Rob's experiments

[Tor Bug Tracker & Wiki]

#33076: Graph onionperf and consensus information from Rob's experiments
-+-
 Reporter:  mikeperry|  Owner:
 |  metrics-team
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Analysis |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-team-roadmap-2020Q1, sbws-   |  Actual Points:  3
  roadmap|
Parent ID:  #33327   | Points:  6
 Reviewer:   |Sponsor:
 |  Sponsor59
-+-
Changes (by pastly):

 * cc: pastly (added)


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

Re: [tor-bugs] #32574 [Internal Services/Service - github tpo]: set up mirror repo on GitHub torproject/jtorctl

[Tor Bug Tracker & Wiki]

#32574: set up mirror repo on GitHub torproject/jtorctl
+--
 Reporter:  eighthave   |  Owner:  hiro
 Type:  task| Status:  new
 Priority:  Medium  |  Milestone:
Component:  Internal Services/Service - github tpo  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  Android, tbb-mobile, jtorctl|  Actual Points:
Parent ID:  #32534  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by pili):

 * keywords:  Android, tbb-mobile, jtorctl, TorBrowserTeam202004 => Android,
 tbb-mobile, jtorctl


Comment:

 Where are we with this one? Is it working correctly? Can this be closed
 now?

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

Re: [tor-bugs] #33350 [Core Tor/sbws]: Is sbws weighting some relays too high?

[Tor Bug Tracker & Wiki]

#33350: Is sbws weighting some relays too high?
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  sbws:
  |  1.1.x-final
Component:  Core Tor/sbws |Version:
 Severity:  Normal| Resolution:
 Keywords:  sbws-roadmap, network-health  |  Actual Points:
Parent ID:  #33121| Points:  2
 Reviewer:|Sponsor:
--+
Changes (by juga):

 * cc: starlight (added)


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

Re: [tor-bugs] #33350 [Core Tor/sbws]: Is sbws weighting some relays too high?

[Tor Bug Tracker & Wiki]

#33350: Is sbws weighting some relays too high?
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  sbws:
  |  1.1.x-final
Component:  Core Tor/sbws |Version:
 Severity:  Normal| Resolution:
 Keywords:  sbws-roadmap, network-health  |  Actual Points:
Parent ID:  #33121| Points:  2
 Reviewer:|Sponsor:
--+

Comment (by juga):

 Since XX is a duplicate of this, adding here the info starlight added and
 closing it:

 ​https://metrics.torproject.org/totalcw.png?start=2019-12-18

 {{{
  tingpo
 bastet---  3600 0.0150 +0.4605 0 39
 Faravahar  4980 0.0208 +1.0203 0 39
 maatuska- 2275652 9.4867 +922.1891 0 39

  NLRelay05
 bastet--- 1 0. -0.9998 34 1747
 moria1---  5770 0.0239 +0.1819 34 1747
 maatuska- 1870361 7.7590 +382.1240 34 1747
 }}}

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

Re: [tor-bugs] #32476 [Applications/Tor Browser]: Support Launching TorService Using JNI

[Tor Bug Tracker & Wiki]

#32476: Support Launching TorService Using JNI
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  Android, tbb-mobile, |  Actual Points:
  TorBrowserTeam202004   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by pili):

 I'm a bit lost on the status of this ticket and whether this is actively
 being worked on by anyone :)

 Can someone who knows better than me update the owner and status of this
 ticket?

 Thank 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] #33350 [Core Tor/sbws]: Is sbws weighting some relays too high?

[Tor Bug Tracker & Wiki]

#33350: Is sbws weighting some relays too high?
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  sbws:
  |  1.1.x-final
Component:  Core Tor/sbws |Version:
 Severity:  Normal| Resolution:
 Keywords:  sbws-roadmap, network-health  |  Actual Points:
Parent ID:  #33121| Points:  2
 Reviewer:|Sponsor:
--+

Comment (by juga):

 i think the main reason why this is happening is because:
 - #33831: relays without observed or average bandwidth in the descriptors
 are not scaled, but still added to the bwlines without vote=0
 - relays without that bandwidth in the descriptor but bandwidth burst
 (dunno why they have bandwidth burst and not the other, but i've seen it
 happening), would scale against bandwidth burst, which is higher

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

Re: [tor-bugs] #32544 [Applications/Tor Browser]: Create Style Guides

[Tor Bug Tracker & Wiki]

#32544: Create Style Guides
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam202008  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by pili):

 * keywords:  TorBrowserTeam202004 => TorBrowserTeam202008


Comment:

 This is unfortunately not a priority right now :(

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

Re: [tor-bugs] #32331 [Applications/Tor Browser]: Tor Browser 9 on Lineage OS 14.1 stalls during start-up

[Tor Bug Tracker & Wiki]

#32331: Tor Browser 9 on Lineage OS 14.1 stalls during start-up
-+-
 Reporter:  gk   |  Owner:  sisbell
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-9.0-issues, tbb-regression,  |  Actual Points:
  tbb-9.0.4-can, tbb-9.5a4-must, |
  TorBrowserTeam202004   |
Parent ID:   | Points:  0.25
 Reviewer:  sysrqb   |Sponsor:
-+-
Changes (by pili):

 * status:  assigned => needs_information


Comment:

 We need a volunteer to test the fix out

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

Re: [tor-bugs] #32006 [Applications/Tor Browser]: Add key shortcut tooltips for new identity toolbar button

[Tor Bug Tracker & Wiki]

#32006: Add key shortcut tooltips for new identity toolbar button
-+-
 Reporter:  acat |  Owner:  acat
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-newnym, ux-team, |  Actual Points:
  TorBrowserTeam202007   |
Parent ID:   | Points:  1
 Reviewer:  pospeselr|Sponsor:
-+-
Changes (by pili):

 * keywords:  tbb-newnym, ux-team, TorBrowserTeam202004 => tbb-newnym, ux-
 team, TorBrowserTeam202007


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

Re: [tor-bugs] #32361 [Applications/Tor Browser]: Unresponsive script error when I start Tor browser

[Tor Bug Tracker & Wiki]

#32361: Unresponsive script error when I start Tor browser
--+---
 Reporter:  LokiAstaroth  |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam202004  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by pili):

 Is this still happening with the latest noscript and httpse updates?

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

Re: [tor-bugs] #32198 [Internal Services/Services Admin Team]: upgrade CRM* machines to buster

[Tor Bug Tracker & Wiki]

#32198: upgrade CRM* machines to buster
-+-
 Reporter:  anarcat  |  Owner:  hiro
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Services Admin |Version:
  Team   |
 Severity:  Normal   | Resolution:
 Keywords:  tpa-roadmap-february tpa-roadmap-|  Actual Points:
  march  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by hiro):

 This is a possible timeline for migrating the CRM machine (to be confirmed
 with GR)

  1. libvirt-import, renumber-instances, DNS TTL, DRBD change, implies few
 minutes downtime, anarcat, wed 8th
  2. hack at ipsec, anarcat, wed 8th
  3. test, anarcat, wed 8th
  4. buster upgrade, hiro, thu 9th
  5. test, hiro, thu 9th
  6. put Drupal in maintenance mode on old CRMs, GR, wed 15th
  7. sync mysql and uploads, GR, wed 15th
  8. shutdown old CRM, hiro/anarcat, thu 16th (step 8 in the ganeti
 procedure)
  9. final DNS change, hiro/anarcat, thu 16th (step 11 and 12 in the ganeti
 procedure)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33831 [Core Tor/sbws]: Relays without descriptors are not scaled, but still added to the bwlines without vote=0

[Tor Bug Tracker & Wiki]

#33831: Relays without descriptors are not scaled, but still added to the 
bwlines
without vote=0
---+---
 Reporter:  juga   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  sbws: 1.1.x-final
Component:  Core Tor/sbws  |Version:  sbws: 1.1.0
 Severity:  Normal |   Keywords:  sbws-roadmap
Actual Points: |  Parent ID:  #33121
   Points:  1  |   Reviewer:
  Sponsor: |
---+---
 As can be seen in:
 
https://gitweb.torproject.org/sbws.git/tree/sbws/lib/v3bwfile.py?h=maint-1.1#n1317

 As a result, some relays (in sample data  counted ~800) are included in
 the bandwidth file without its bandwidth scaled, which could be quite
 different (higher or lower) than the scaled bandwidth.

 This is one of the several reasons of #33775.

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

Re: [tor-bugs] #32297 [Applications/Tor Browser]: Version 9 problem (regular and alpha) when some Exit Nodes are blocked by a website firewall

[Tor Bug Tracker & Wiki]

#32297: Version 9 problem (regular and alpha) when some Exit Nodes are blocked 
by a
website firewall
-+-
 Reporter:  mwolfe   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-9.0-issues, tbb-regression,  |  Actual Points:
  TorBrowserTeam202008   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by sysrqb):

 * keywords:  tbb-9.0-issues, tbb-regression, TorBrowserTeam202004 =>
 tbb-9.0-issues, tbb-regression, TorBrowserTeam202008


Comment:

 Replying to [comment:18 mwolfe]:
 > Replying to [comment:16 mwolfe]:
 > Finally managed to get a clean copy of Tor 9.0 on OSX10.11.6 El Capitan
 and no problem of the New Circuit for the Site. Problem is only on my
 version of Windows, 10 1903.

 Are you still able to reproduce this problem on Windows 10 with Tor
 Browser 9.5?

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

Re: [tor-bugs] #32173 [Applications/Tor Browser]: Update signing infrastructure to work with Apple's notarization process

[Tor Bug Tracker & Wiki]

#32173: Update signing infrastructure to work with Apple's notarization process
-+-
 Reporter:  gk   |  Owner:  sysrqb
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-sign, ReleaseTrainMigration, |  Actual Points:  1
  TorBrowserTeam202004   |
Parent ID:   | Points:  1
 Reviewer:  gk   |Sponsor:
 |  Sponsor58
-+-
Changes (by pili):

 * reviewer:   => gk


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

Re: [tor-bugs] #32119 [Applications/Tor Browser]: onboarding for "Goodbye Onion Button" could be better

[Tor Bug Tracker & Wiki]

#32119: onboarding for "Goodbye Onion Button" could be better
-+-
 Reporter:  catalyst |  Owner:  brade
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:  ux-team, tbb-onboarding, |  Actual Points:
  tbb-9.0-issues, TorBrowserTeam202004,  |
  ReleaseTrainMigration  |
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:
-+-
Changes (by pili):

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


Comment:

 We will revisit this as part of the new onboarding review. Closing for now

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

Re: [tor-bugs] #31992 [Applications/Tor Browser]: Remove apktool workaround in #31564

[Tor Bug Tracker & Wiki]

#31992: Remove apktool workaround in #31564
-+-
 Reporter:  gk   |  Owner:  sisbell
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-rbm, ReleaseTrainMigration,  |  Actual Points:
  TorBrowserTeam202004   |
Parent ID:   | Points:  0.25
 Reviewer:  sysrqb   |Sponsor:
 |  Sponsor58-can
-+-
Changes (by pili):

 * reviewer:   => sysrqb


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

Re: [tor-bugs] #31918 [Applications/Tor Browser]: Rebase and squash mobile/android patches into desktop

[Tor Bug Tracker & Wiki]

#31918: Rebase and squash mobile/android patches into desktop
-+-
 Reporter:  sysrqb   |  Owner:  sysrqb
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-9.5, ReleaseTrainMigration,  |  Actual Points:
  TorBrowserTeam202004   |
Parent ID:   | Points:  1
 Reviewer:  acat |Sponsor:
 |  Sponsor58
-+-
Changes (by pili):

 * reviewer:   => acat


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

Re: [tor-bugs] #33176 [Metrics]: Check whether all of our growth stats we want are collected and accurate

[Tor Bug Tracker & Wiki]

#33176: Check whether all of our growth stats we want are collected and accurate
-+-
 Reporter:  gk   |  Owner:
 |  metrics-team
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-health, network-health-  |  Actual Points:
  roadmap-2020Q1 |
Parent ID:  #33178   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by gaba):

 * keywords:
 network-health, network-health-roadmap-2020Q1, metrics-team-roadmap-
 2020April
 => network-health, network-health-roadmap-2020Q1


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

Re: [tor-bugs] #29615 [Applications/Tor Browser]: Adjust creation of buildID script

[Tor Bug Tracker & Wiki]

#29615: Adjust creation of buildID script
---+---
 Reporter:  gk |  Owner:  boklm
 Type:  task   | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam202005  |  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:  Sponsor58
---+---

Comment (by sysrqb):

 See Also: #33809

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

Re: [tor-bugs] #33178 [Metrics]: Figure out specific baselines we are interested in from a network health perspective

[Tor Bug Tracker & Wiki]

#33178: Figure out specific baselines we are interested in from a network health
perspective
-+-
 Reporter:  gk   |  Owner:
 |  metrics-team
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-health, network-health-  |  Actual Points:
  roadmap-2020Q1 |
Parent ID:   | Points:  5
 Reviewer:   |Sponsor:
-+-
Changes (by gaba):

 * keywords:
 network-health, network-health-roadmap-2020Q1, metrics-team-roadmap-
 2020April
 => network-health, network-health-roadmap-2020Q1


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

Re: [tor-bugs] #31499 [Applications/Tor Browser]: Update libevent to 2.1.11-stable

[Tor Bug Tracker & Wiki]

#31499: Update libevent to 2.1.11-stable
---+---
 Reporter:  cypherpunks|  Owner:  sisbell
 Type:  defect | Status:
   |  needs_revision
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam202004  |  Actual Points:
Parent ID: | Points:  1
 Reviewer:  boklm, gk  |Sponsor:
---+---
Changes (by pili):

 * points:   => 1


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

Re: [tor-bugs] #29615 [Applications/Tor Browser]: Adjust creation of buildID script

[Tor Bug Tracker & Wiki]

#29615: Adjust creation of buildID script
---+---
 Reporter:  gk |  Owner:  boklm
 Type:  task   | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam202005  |  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:  Sponsor58
---+---
Changes (by pili):

 * keywords:  tbb-rbm, TorBrowserTeam202004 => tbb-rbm, TorBrowserTeam202005


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

Re: [tor-bugs] #30199 [Applications/Tor Browser]: tor-android-service: Review 2019/04/16

[Tor Bug Tracker & Wiki]

#30199: tor-android-service: Review 2019/04/16
-+-
 Reporter:  sysrqb   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-8.5, |  Actual Points:
  TorBrowserTeam202004   |
Parent ID:   | Points:  0.5
 Reviewer:  sysrqb   |Sponsor:
-+-
Changes (by pili):

 * reviewer:   => sysrqb


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

Re: [tor-bugs] #27590 [Applications/Tor Browser]: Display .onion alt-svc route in the circuit display

[Tor Bug Tracker & Wiki]

#27590: Display .onion alt-svc route in the circuit display
-+-
 Reporter:  mahrud   |  Owner:  acat
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-circuit-display, ux-team,|  Actual Points:
  TorBrowserTeam202008   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor27-must
-+-
Changes (by pili):

 * keywords:  tbb-circuit-display, ux-team, TorBrowserTeam202004 => tbb-
 circuit-display, ux-team, TorBrowserTeam202008


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

Re: [tor-bugs] #27045 [Applications/Tor Browser]: Add option for firefox incremental builds

[Tor Bug Tracker & Wiki]

#27045: Add option for firefox incremental builds
---+--
 Reporter:  boklm  |  Owner:  boklm
 Type:  task   | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam202005  |  Actual Points:
Parent ID: | Points:
 Reviewer:  gk |Sponsor:
---+--
Changes (by boklm):

 * cc: tbb-team (added)


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

Re: [tor-bugs] #24527 [Applications/Tor Launcher]: Inform users in Tor Launcher of which settings are best for them based on their country

[Tor Bug Tracker & Wiki]

#24527: Inform users in Tor Launcher of which settings are best for them based 
on
their country
-+-
 Reporter:  hellais  |  Owner:  mcs
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Launcher|Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s32-o32a2,  |  Actual Points:
  TorBrowserTeam202005   |
Parent ID:  #31283   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor30-can
-+-
Changes (by boklm):

 * cc: tbb-team (added)


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

Re: [tor-bugs] #33830 [Applications/Tor Browser]: Language Error

[Tor Bug Tracker & Wiki]

#33830: Language Error
--+--
 Reporter:  akshaylandge1011  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by ggus):

 * cc: ggus (removed)
 * cc: emmapeel (added)
 * owner:  (none) => tbb-team
 * component:  Webpages => Applications/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] #27045 [Applications/Tor Browser]: Add option for firefox incremental builds

[Tor Bug Tracker & Wiki]

#27045: Add option for firefox incremental builds
---+--
 Reporter:  boklm  |  Owner:  boklm
 Type:  task   | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam202005  |  Actual Points:
Parent ID: | Points:
 Reviewer:  gk |Sponsor:
---+--
Changes (by pili):

 * owner:  tbb-team => boklm
 * keywords:  tbb-rbm, TorBrowserTeam202004 => tbb-rbm, TorBrowserTeam202005
 * status:  needs_revision => assigned


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

Re: [tor-bugs] #25021 [Applications/Tor Browser]: Update Tor Browser spec for 9.0

[Tor Bug Tracker & Wiki]

#25021: Update Tor Browser spec for 9.0
-+-
 Reporter:  gk   |  Owner:  gk
 Type:  defect   | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-spec, GeorgKoppen202004, |  Actual Points:
  TorBrowserTeam202004   |
Parent ID:   | Points:  5
 Reviewer:  sysrqb   |Sponsor:
-+-
Changes (by pili):

 * reviewer:   => sysrqb


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

Re: [tor-bugs] #24527 [Applications/Tor Launcher]: Inform users in Tor Launcher of which settings are best for them based on their country

[Tor Bug Tracker & Wiki]

#24527: Inform users in Tor Launcher of which settings are best for them based 
on
their country
-+-
 Reporter:  hellais  |  Owner:  mcs
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Launcher|Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, s32-o32a2,  |  Actual Points:
  TorBrowserTeam202005   |
Parent ID:  #31283   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor30-can
-+-
Changes (by pili):

 * keywords:  ux-team, s32-o32a2, TorBrowserTeam202004 => ux-team,
 s32-o32a2, TorBrowserTeam202005


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