Re: [tor-bugs] #28755 [Core Tor/Tor]: Implement a K/V parser library

[Tor Bug Tracker & Wiki]

#28755: Implement a K/V parser library
--+
 Reporter:  dgoulet   |  Owner:  nickm
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  .3
Parent ID:  #25502| Points:
 Reviewer:  ahf, dgoulet  |Sponsor:
--+

Comment (by teor):

 We could test this branch by moving all our K=V parsing over to it, and
 running the unit and integration tests.

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

Re: [tor-bugs] #28757 [Core Tor/Tor]: Remove deprecated ControlPort commands from GETINFO info/names listing

[Tor Bug Tracker & Wiki]

#28757: Remove deprecated ControlPort commands from GETINFO info/names listing
-+-
 Reporter:  wagon|  Owner:  atagar
 Type:  defect   | Status:  reopened
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor: 0.3.4.9
 Severity:  Normal   | Resolution:
 Keywords:  tor-control, tor-spec, easy  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  tor-control, tor-spec => tor-control, tor-spec, easy
 * milestone:   => Tor: unspecified


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

Re: [tor-bugs] #28760 [Core Tor/Tor]: Option/* format for ControlPort options needs to be homogeneous

[Tor Bug Tracker & Wiki]

#28760: Option/* format for ControlPort options needs to be homogeneous
--+
 Reporter:  wagon |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor:
  |  unspecified
Component:  Core Tor/Tor  |Version:  Tor:
  |  0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:  tor-control, tor-spec, easy, doc  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * keywords:  tor-control, tor-spec => tor-control, tor-spec, easy, doc
 * milestone:   => Tor: unspecified


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

Re: [tor-bugs] #28733 [Core Tor/Tor]: {CONSDIFF} Refusing to apply consensus diff

[Tor Bug Tracker & Wiki]

#28733: {CONSDIFF} Refusing to apply consensus diff
--+---
 Reporter:  traumschule   |  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  consensus |  Actual Points:
Parent ID:  #26310| Points:
 Reviewer:|Sponsor:
--+---
Changes (by teor):

 * status:  new => needs_information
 * milestone:   => Tor: unspecified


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

Re: [tor-bugs] #28358 [Core Tor/Tor]: Nyx forces Tor error: sandbox_getaddrinfo(): Bug: (Sandbox) failed to get address

[Tor Bug Tracker & Wiki]

#28358: Nyx forces Tor error: sandbox_getaddrinfo(): Bug: (Sandbox) failed to 
get
address
--+
 Reporter:  wagon |  Owner:  (none)
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:  sandbox   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * status:  new => needs_review
 * milestone:  Tor: unspecified => Tor: 0.4.0.x-final


Comment:

 This ticket has a patch, so it belongs in 0.4.0.

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

Re: [tor-bugs] #28676 [Core Tor/Tor]: Tor versions of Tor nodes should be accessible through ControlPort

[Tor Bug Tracker & Wiki]

#28676: Tor versions of Tor nodes should be accessible through ControlPort
--+--
 Reporter:  wagon |  Owner:  arma
 Type:  enhancement   | Status:  assigned
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #24110| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 Replying to [comment:10 wagon]:
 > > There are millions of tor clients, and they use microdescriptors and
 the microdesc consensus (md) by default. So we need to minimise the size
 of md documents.
 > OK. However, most of these clients download consensus files from mirrors
 on other relays, i.e. not from authorities.

 The tor network is often overloaded. This overload makes tor client
 traffic slow. So we want to reduce the overall directory load on the
 network, because bandwidth that is used for directory mirror downloads
 can't be used for client traffic.

 Smaller directory documents also decrease the client and directory mirror
 load on authorities. (Authorities don't carry much client traffic at all,
 but they do serve a lot of directory documents.)

 > > We have proposals that would create a new consensus flavour (picodesc
 consensus? pd?) with fewer fields. Once all supported Tor versions use the
 pd consensus, we can stop distributing the microdesc consensus.
 > Ok. I see Tor development is moving in opposite direction than that I
 thought about. I hope Tor people make right decisions.

 In this case, network load is more important than simplicity.

 In general, that's why we have a proposals process.

 > > Or, more likely, distribute a md consensus containing no relays.
 > What does it mean? What is the point of having consensus which contain
 no information about relays?

 When we disable a feature in Tor, some really old tor clients have bugs
 that overload the network (#4580). So we give them a fake empty
 replacement for that feature.

 > > You can bind `ControlPort` to a non-local port, but you must have
 authentication on
 > How I can do this technically? I cannot see any option in `man torrc`
 about that. According to `man` page `ControlPort` specifies only port and
 not `IP:port`.

 `tor ControlPort 192.0.2.1:9090` works for me.

 That's probably another bug, or we might have decided to discourage people
 from using IP addresses.

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

Re: [tor-bugs] #28555 [Metrics/Analysis]: Assess methodology for modern privcount Tor user counts

[Tor Bug Tracker & Wiki]

#28555: Assess methodology for modern privcount Tor user counts
--+--
 Reporter:  arma  |  Owner:  metrics-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Metrics/Analysis  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor19
--+--

Comment (by teor):

 I just wrote about this in #tor-project:

 The 8 million user figure was measured using PSC, which does unique counts
 across multiple relays. We won't be implementing unique counts in
 PrivCount in Tor, because it's an entirely different protocol, which takes
 ~24 hours to aggregate the counts.

 Pages 8-11 of https://export.arxiv.org/pdf/1809.08481 give a few more
 details about the methods we used to calculate the 8 million figure.

 The best way to get a better estimate out of metrics, is to measure how
 many consensuses a client downloads in 24 hours, and update metrics'
 estimate. (We can't really do anything to measure clients that move IP
 addresses, or clients that are only online for part of a day.)

 Maybe we could measure the average number of consensuses per day per IP
 address using PrivCount? But then we'd be keeping sensitive info in RAM
 (IP addresses).

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

Re: [tor-bugs] #28725 [Applications/Tor Browser]: Upgrade go-webrtc to dcbfc825aa33471253a5da1834d499257e05d557

[Tor Bug Tracker & Wiki]

#28725: Upgrade go-webrtc to dcbfc825aa33471253a5da1834d499257e05d557
-+-
 Reporter:  dcf  |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake tbb-rbm,   |  Actual Points:
  TorBrowserTeam201812R  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  snowflake tbb-rbm, TorBrowserTeam201812 => snowflake tbb-rbm,
 TorBrowserTeam201812R


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

Re: [tor-bugs] #28725 [Applications/Tor Browser]: Upgrade go-webrtc to dcbfc825aa33471253a5da1834d499257e05d557

[Tor Bug Tracker & Wiki]

#28725: Upgrade go-webrtc to dcbfc825aa33471253a5da1834d499257e05d557
-+-
 Reporter:  dcf  |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake tbb-rbm,   |  Actual Points:
  TorBrowserTeam201812   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by dcf):

 * status:  needs_revision => needs_review


Comment:

 Here's another. I haven't tested it but the only difference is
 {{{
 -  mkdir -p "$INCLUDE_DIR/$(dirname $h)"
 +  mkdir -p "$INCLUDE_DIR/$(dirname "$h")"
 }}}

 Replying to [comment:6 gk]:
 > I have both `third-party/llvm` and `third-party/llvm-build` for what
 it's worth. `git status` run in `gclient/webrtc/src/third_party` gives
 > {{{
 > gk@stefan:~/tor-browser-build/gclient/webrtc/src/third_party$ git status
 > HEAD detached at 6a94dad
 > Untracked files:
 >   (use "git add ..." to include in what will be committed)
 >
 >   gtest-parallel/
 >   llvm-build-tools/
 >   winsdk_samples/
 > }}}
 > Does that ring some bell?

 Mine is different:
 {{{
 ~/tor-browser-build/gclient/webrtc/src/third_party$ git status
 HEAD detached at 6a94dad699
 Untracked files:
   (use "git add ..." to include in what will be committed)

 gflags/
 gtest-parallel/
 }}}

 `/llvm` is in `gclient/webrtc/src/third_party/.gitignore`, so I guess
 because your checkout is older than mine you have some old leftover files.
 Since upstream changed from storing all their headers under `webrtc/` to
 storing them all under `./`, I suppose some extraneous cruft like that
 gets included. I think it should be harmless.

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

Re: [tor-bugs] #28771 [Applications/Tor Browser]: Does the build still require libfile-slurp-perl?

[Tor Bug Tracker & Wiki]

#28771: Does the build still require libfile-slurp-perl?
+--
 Reporter:  dcf |  Owner:  tbb-team
 Type:  defect  | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201812R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by gk):

 * cc: boklm (added)
 * keywords:   => tbb-rbm, TorBrowserTeam201812R


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

Re: [tor-bugs] #28725 [Applications/Tor Browser]: Upgrade go-webrtc to dcbfc825aa33471253a5da1834d499257e05d557

[Tor Bug Tracker & Wiki]

#28725: Upgrade go-webrtc to dcbfc825aa33471253a5da1834d499257e05d557
-+-
 Reporter:  dcf  |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake tbb-rbm,   |  Actual Points:
  TorBrowserTeam201812   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by dcf):

 * Attachment "bug28725_3.patch" added.


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

Re: [tor-bugs] #28766 [Applications/Tor Browser]: Tor Build for Android

[Tor Bug Tracker & Wiki]

#28766: Tor Build for Android
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:
  TorBrowserTeam201812   |
Parent ID:  #28704   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 Replying to [comment:2 boklm]:
 > For the linux nightly build, we build rust 1.28.0. Maybe we can do the
 same.
 >
 > We can also start by building Tor without rust (like on Windows and
 macOS).

 Yes, let's start without building Tor on Android with the newer Rust.

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

Re: [tor-bugs] #24786 [Core Tor/Fallback Scripts]: Rebuild the fallback list in 2018

[Tor Bug Tracker & Wiki]

#24786: Rebuild the fallback list in 2018
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Fallback Scripts|Version:
 Severity:  Normal   | Resolution:
 Keywords:  s8-bootstrap, fallback, 035  |  Actual Points:
  -roadmap-master, 029-backport, 033-backport,   |
  034-backport, 034-roadmap-master,  |
  034-triage-20180328, 034-included-20180328,|
  031-unreached-backport-maybe, 035-triaged- |
  in-20180711, 035-can, 032-unreached-backport-  |
  maybe  |
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by teor):

 * keywords:
 fallback, 035-roadmap-master, 029-backport, 033-backport,
 034-backport, 034-roadmap-master, 034-triage-20180328,
 034-included-20180328, 031-unreached-backport-maybe, 035-triaged-
 in-20180711, 035-can, 032-unreached-backport-maybe
 =>
 s8-bootstrap, fallback, 035-roadmap-master, 029-backport,
 033-backport, 034-backport, 034-roadmap-master, 034-triage-20180328,
 034-included-20180328, 031-unreached-backport-maybe, 035-triaged-
 in-20180711, 035-can, 032-unreached-backport-maybe
 * sponsor:   => Sponsor8-can
 * milestone:  Tor: 0.3.5.x-final => Tor: 0.4.0.x-final


Comment:

 This task and its subtasks improve Tor's bootstrapping speed, so they can
 be part of Sponsor 8.

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

Re: [tor-bugs] #24804 [Core Tor/Fallback Scripts]: Run an opt-in process for relay operators to become fallbacks

[Tor Bug Tracker & Wiki]

#24804: Run an opt-in process for relay operators to become fallbacks
-+-
 Reporter:  teor |  Owner:  phoul
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Fallback Scripts|Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  s8-bootstrap, fallback,  |  Actual Points:
  034-triage-20180328, 034-removed-20180328, |
  035-roadmap-subtask, 035-triaged-in-20180711,  |
  035-can|
Parent ID:  #24786   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by teor):

 * status:  assigned => closed
 * keywords:
 fallback, 034-triage-20180328, 034-removed-20180328, 035-roadmap-
 subtask, 035-triaged-in-20180711, 035-can
 =>
 s8-bootstrap, fallback, 034-triage-20180328, 034-removed-20180328, 035
 -roadmap-subtask, 035-triaged-in-20180711, 035-can
 * resolution:   => fixed
 * sponsor:   => Sponsor8-can
 * milestone:  Tor: 0.3.5.x-final => Tor: 0.4.0.x-final


Comment:

 This task is done, we're about to merge the whitelist in #24805, and we're
 generating the new hard-coded list in #24803.

 Phoul, if you can update this ticket's "Actual Points" with the number of
 days you spent on this task, that will help gaba with the project
 management.

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

Re: [tor-bugs] #28725 [Applications/Tor Browser]: Upgrade go-webrtc to dcbfc825aa33471253a5da1834d499257e05d557

[Tor Bug Tracker & Wiki]

#28725: Upgrade go-webrtc to dcbfc825aa33471253a5da1834d499257e05d557
-+-
 Reporter:  dcf  |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake tbb-rbm,   |  Actual Points:
  TorBrowserTeam201812   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  snowflake tbb-rbm, TorBrowserTeam201812R => snowflake tbb-rbm,
 TorBrowserTeam201812
 * status:  needs_review => needs_revision


Comment:

 Still broken:
 {{{
 [2226/2226] AR obj/libwebrtc.a
 dirname: extra operand `space/test.h'
 Try `dirname --help' for more information.
 cp: cannot create regular file
 
`/var/tmp/dist/webrtc/include/./third_party/llvm/tools/clang/test/ARCMT/Inputs/with
 space/test.h': No such file or directory
 }}}

 I have both `third-party/llvm` and `third-party/llvm-build` for what it's
 worth. `git status` run in `gclient/webrtc/src/third_party` gives
 {{{
 gk@stefan:~/tor-browser-build/gclient/webrtc/src/third_party$ git status
 HEAD detached at 6a94dad
 Untracked files:
   (use "git add ..." to include in what will be committed)

 gtest-parallel/
 llvm-build-tools/
 winsdk_samples/
 }}}
 Does that ring some bell?

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

Re: [tor-bugs] #24805 [Core Tor/Fallback Scripts]: Update fallback whitelist in late 2018

[Tor Bug Tracker & Wiki]

#24805: Update fallback whitelist in late 2018
-+-
 Reporter:  teor |  Owner:  phoul
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Fallback Scripts|Version:
 Severity:  Normal   | Resolution:
 Keywords:  s8-bootstrap, fallback,  |  Actual Points:
  034-triage-20180328, 034-removed-20180328, |
  035-removed-20180711, 035-roadmap  |
Parent ID:  #24786   | Points:  0.5
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by teor):

 * keywords:
 fallback, 034-triage-20180328, 034-removed-20180328,
 035-removed-20180711, 035-roadmap
 =>
 s8-bootstrap, fallback, 034-triage-20180328, 034-removed-20180328,
 035-removed-20180711, 035-roadmap
 * status:  needs_revision => needs_review
 * sponsor:   => Sponsor8-can
 * milestone:  Tor: 0.3.5.x-final => Tor: 0.4.0.x-final


Comment:

 We're creating the new fallback list over the next few days.

 I created a pull request for the whitelist updates in:
 https://github.com/torproject/tor/pull/572

 I based it on Phoul's branch, and added a changes file.

 Phoul, if you can update the actual points in the ticket with the number
 of days you spent on this task, that would be great!

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

Re: [tor-bugs] #28769 [Internal Services/Tor Sysadmin Team]: Please change email forwarding (several items)

[Tor Bug Tracker & Wiki]

#28769: Please change email forwarding (several items)
-+-
 Reporter:  ewyatt   |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by arma):

 I did 1, and 2, and I removed tommyc from a bunch of email aliases, but I
 didn't finish 3 yet. That's because it appears he has an ldap account, not
 just an email forwarder, so we need to open a ticket asking the account to
 be disabled. (When we do open that ticket, I think it's fine to disable it
 the normal way, not the emergency way, meaning the email forwarding will
 get automatically deactivated some months after the account gets
 disabled.)

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

Re: [tor-bugs] #24803 [Core Tor/Fallback Scripts]: Generate a new fallback list in 2018 and backport it to all supported versions

[Tor Bug Tracker & Wiki]

#24803: Generate a new fallback list in 2018 and backport it to all supported
versions
-+-
 Reporter:  teor |  Owner:  phoul
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Fallback Scripts|Version:
 Severity:  Normal   | Resolution:
 Keywords:  s8-bootstrap, fallback,  |  Actual Points:  0.4
  029-backport, 033-backport, 034-backport,  |
  035-backport, 034-triage-20180328, |
  034-included-20180405, 034-roadmap-subtask,|
  031-unreached-backport-maybe, 035-roadmap- |
  subtask, 035-triaged-in-20180711, 035-can, |
  032-unreached-backport-maybe   |
Parent ID:  #24786   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by teor):

 * status:  new => assigned
 * actualpoints:   => 0.4
 * keywords:
 fallback, 029-backport, 033-backport, 034-backport,
 034-triage-20180328, 034-included-20180405, 034-roadmap-subtask, 031
 -unreached-backport-maybe, 035-roadmap-subtask, 035-triaged-
 in-20180711, 035-can, 032-unreached-backport-maybe
 =>
 s8-bootstrap, fallback, 029-backport, 033-backport, 034-backport,
 035-backport, 034-triage-20180328, 034-included-20180405, 034-roadmap-
 subtask, 031-unreached-backport-maybe, 035-roadmap-subtask, 035
 -triaged-in-20180711, 035-can, 032-unreached-backport-maybe
 * sponsor:   => Sponsor8-can
 * milestone:  Tor: 0.3.5.x-final => Tor: 0.4.0.x-final
 * owner:  (none) => phoul


Comment:

 Hi phoul,

 Can you generate a fallback list from my branch ticket24838-24805 from
 https://github.com/teor2345/tor/ ?

 It contains my fallback script changes from #24838, and your fallback
 whitelist changes from #24805.

 Once you've created the list, you can attach it to this ticket, or put it
 in a branch.

 I have also created a list using ticket24838-24805, it's in my branch
 ticket24803-029:
 https://github.com/torproject/tor/pull/571

 Once you've done your list, I'll merge both lists, and update the changes
 file.

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

Re: [tor-bugs] #24838 [Core Tor/Fallback Scripts]: Fuzzy match the fallback whitelist (was: Ignore addresses in the fallback whitelist)

[Tor Bug Tracker & Wiki]

#24838: Fuzzy match the fallback whitelist
-+-
 Reporter:  teor |  Owner:  teor
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Fallback Scripts|Version:
 Severity:  Normal   | Resolution:
 Keywords:  s8-bootstrap, easy, intro,   |  Actual Points:  0.5
  fallback, 034-triage-20180328, |
  034-removed-20180328, fast-fix, 035-roadmap-   |
  subtask, 035-triaged-in-20180711   |
Parent ID:  #24786   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by teor):

 * status:  assigned => needs_review
 * actualpoints:   => 0.5
 * sponsor:   => Sponsor8-can
 * milestone:  Tor: 0.3.5.x-final => Tor: 0.4.0.x-final
 * keywords:
 easy, intro, fallback, 034-triage-20180328, 034-removed-20180328,
 fast-fix, 035-roadmap-subtask, 035-triaged-in-20180711
 =>
 s8-bootstrap, easy, intro, fallback, 034-triage-20180328,
 034-removed-20180328, fast-fix, 035-roadmap-subtask, 035-triaged-
 in-20180711


Old description:

> We can rely on Onionoo to tell us when relay addresses change, so we
> don't need to check them.
> But listing addresses is useful when fingerprints change.
>
> This simplifies maintaining the fallback whitelist, and also simplifies
> the script.
>
> We will delete the blacklist in #26502.

New description:

 We can rely on Onionoo to tell us when relay fingerprints or addresses
 change, so we don't need to do an exact match.

 But listing fingerprints, addresses and ports in the whitelist is useful
 so that we know what a relay operator originally asked for.

 Fuzzy matching simplifies maintaining the fallback whitelist, because we
 don't have to ask operators to update their relay details. (Or ask if
 those details are permanent.)

 We deleted the blacklist in #26502.

--

Comment:

 See my pull request, which contains the code for this ticket and #28768:
 https://github.com/torproject/tor/pull/570

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28772 [Core Tor/Tor]: DNS resolver at DNSPort stops working after some time, while tor is working. Only restart helps.

[Tor Bug Tracker & Wiki]

#28772: DNS resolver at DNSPort stops working after some time, while tor is
working. Only restart helps.
--+--
 Reporter:  toruser787|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Immediate |  Component:  Core Tor/Tor
  Version:  Tor: 0.3.5.5-alpha|   Severity:  Blocker
 Keywords:  dns bug fail restart dnsport  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
 Hello. I am tor user more than 6 years. And always this problem existed.
 Now I am totally tired and decided to fill a bug. I am using always latest
 versions, now at 0.3.5.5 and on android the same, latest 0.3.* version.

 I use DNSPort option and route all my DNS traffic to it. After tor is
 connected, it is working well, but after some time (2-5-10 hours), it stop
 to work and return no IP address to any DNS request, while the tor itself
 continue working, log don't show anything relevant. DNS requests resolve
 only internally through socks port.

 This happens many years to me, and only restarting tor helps to get my DNS
 back.
 I even tried to open multiple DNSresolvers, like
 DNSPort 127.0.0.2:53
 DNSPort 127.0.0.3:53
 DNSPort 127.0.0.4:53

 and put them all to /etc/resolv.conf, and it helped to keep it running
 more long, but anyway after some time they all stops resolving.

 On android I have the same issue. I rerouted all DNS traffic to it, and
 after some hours only restarting to service works. I even thought to write
 some script, if domain fails to resolve, restart to service...

 Please help! DNSPort resolver must recreate it's circuits if they fails.
 and don't wait for hard reset.
 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] #28740 [Applications/Tor Browser]: Make navigator.platform return "Win32", even on Win64 OS

[Tor Bug Tracker & Wiki]

#28740: Make navigator.platform return "Win32", even on Win64 OS
-+-
 Reporter:  omg  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  GeorgKoppen201812,   |  Actual Points:
  TorBrowserTeam201812R, tbb-backport|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by Thorin):

 ^^ I ran some tests (Windows). Gee, forgot to give you the link (includes
 lots of pretty pictures). There may some other things in there that stick
 out for you (e.g Pointer Events you already covered)
 - https://github.com/ghacksuserjs/ghacks-user.js/issues/550

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

Re: [tor-bugs] #28740 [Applications/Tor Browser]: Make navigator.platform return "Win32", even on Win64 OS

[Tor Bug Tracker & Wiki]

#28740: Make navigator.platform return "Win32", even on Win64 OS
-+-
 Reporter:  omg  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  GeorgKoppen201812,   |  Actual Points:
  TorBrowserTeam201812R, tbb-backport|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by Thorin):

 Replying to [comment:3 mcs]:
 > r=brade, r=mcs
 > Matching the value returned by recent versions of Firefox...

 Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1401493 I ran some
 tests (Windows). The platform difference was already noted. Note: this is
 not (for me at least) about blending TB users with FF RFP users, but
 ultimately about making sure that Tor Uplift patches came thru unscathed
 (and that includes relaxing prefs used in the past or still used in v8*
 that are now covered by RFP)

 Anyway, just FYI, if you didn't want to wait until the next ESR cycle,
 standardizing the buildId could be a good patch to backport: hardcoding
 `2018100100` rather than relying on a pref and using `20100101`. - see
 https://bugzilla.mozilla.org/show_bug.cgi?id=583181

 Up to you guys :) Not backporting it doesn't harm Tor Browser's FP'ing
 entropy

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

Re: [tor-bugs] #28682 [- Select a component]: Carml lacks PGP singatures and instructions for secure installation

[Tor Bug Tracker & Wiki]

#28682: Carml lacks PGP singatures and instructions for secure installation
--+
 Reporter:  wagon |  Owner:  meejah
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  carml |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by meejah):

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


Comment:

 https://github.com/meejah/carml/issues/30

 https://github.com/meejah/carml/issues/31

 https://github.com/meejah/carml/issues/32

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

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by dcf):

 Replying to [comment:17 loskiq]:
 > I just installed the bridge version 0.2.9.17, and the client immediately
 started working. I believe that the problem of 25% is related to the new
 version of the bridge.

 Oh! How surprising. I see from attachment:tor_bridge.log that formerly you
 were using 0.3.4.9. So downgrading from 0.3.4.9 to 0.2.9.17 on the bridge
 (keeping the client at 0.3.4.9) made the bridge start working.

 This also matches with the bridges you posted in comment:16.
 ||154.16.245.120:443 ||not working ||0.3.4.9
 
||[https://metrics.torproject.org/rs.html#details/F80D5303AEDF76071D205788B375719605736F2C
 relay search] [https://archive.is/fI6o0 (archive)] ||
 ||93.190.138.248:41248 ||working ||0.2.9.17
 
||[https://metrics.torproject.org/rs.html#details/BDBA3779B358235EE22161C171A74BFE0E004E66
 relay search] [https://archive.is/7ELUI (archive)] ||

 I'll ask and see if any core-tor developer have an idea about what it
 wrong. If you have time, you can help by testing versions between 0.2.9.17
 and 0.3.4.9 to see which versions work.

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

Re: [tor-bugs] #28771 [Applications/Tor Browser]: Does the build still require libfile-slurp-perl?

[Tor Bug Tracker & Wiki]

#28771: Does the build still require libfile-slurp-perl?
--+--
 Reporter:  dcf   |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dcf):

 * status:  new => needs_review


Comment:

 Here's a small patch porting get_hg_hash from File::Slurp to Path::Tiny. I
 followed the model of
 
[https://gitweb.torproject.org/user/boklm/rbm.git/commit/?h=bug_24361=8b6831b36becc697fc53e61cac058d18096ea4b9
 8b6831b36b]. I found out that the script also has a dependency on the JSON
 module, so I noted that in README.

 It seems that tools/clean-old and tools/dmg2mar still require File::Slurp.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28771 [Applications/Tor Browser]: Does the build still require libfile-slurp-perl?

[Tor Bug Tracker & Wiki]

#28771: Does the build still require libfile-slurp-perl?
--+--
 Reporter:  dcf   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 [https://gitweb.torproject.org/builders/tor-browser-
 build.git/commit/?id=a6d54303ad89af777a4994dc27d0ae90945f090c a6d54303a]
 removed libfile-slurp-perl from README. But
 [https://gitweb.torproject.org/builders/tor-browser-
 build.git/commit/?id=43c9452946313a5ab3dd064501daa05096db86eb 43c9452946]
 addedprojects/firefox-locale-bundle/get_hg_hash which requires it.
 This is the error I get in logs/firefox-locale-bundle-android-armv7.log:
 {{{
 pulling from https://hg.mozilla.org/l10n-central/ar
 searching for changes
 no changes found
 Can't locate File/Slurp.pm in @INC (you may need to install the
 File::Slurp module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-
 gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-
 gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24
 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu
 /perl-base) at /home/user/tor-browser-build/projects/firefox-locale-
 bundle/get_hg_hash line 3.
 BEGIN failed--compilation aborted at /home/user/tor-browser-build/projects
 /firefox-locale-bundle/get_hg_hash line 3.
 }}}

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

Re: [tor-bugs] #28771 [Applications/Tor Browser]: Does the build still require libfile-slurp-perl?

[Tor Bug Tracker & Wiki]

#28771: Does the build still require libfile-slurp-perl?
--+--
 Reporter:  dcf   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dcf):

 * Attachment "0001-Port-get_hg_hash-to-Path-Tiny-and-note-JSON-
 dependen.patch" added.


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

[tor-bugs] #28770 [Internal Services/Tor Sysadmin Team]: Please create email alias for Browser Team dev job posting

[Tor Bug Tracker & Wiki]

#28770: Please create email alias for Browser Team dev job posting
-+-
 Reporter:  ewyatt   |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 {{{
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512

 Please create a temporary email alias, as follows:

 job-browser@

 Forwarding to:

 g...@torproject.org
 sys...@torproject.org
 i...@torproject.org
 sisbe...@torproject.org
 rich...@torproject.org
 m...@pearlcrescent.com
 br...@pearlcrescent.com
 bo...@torproject.org
 ewy...@torproject.org
 isab...@torproject.org
 g...@torproject.org

 Thank you!

 -BEGIN PGP SIGNATURE-
 Comment: GPGTools - https://gpgtools.org

 iQIzBAEBCgAdFiEENecqn2ZVRfkstmYkugyUAPgPkc4FAlwJ2YMACgkQugyUAPgP
 kc5kCg/+LJmjdC5dvXRkePdrTDdW4ihdzZF+yZD9PM5hfU0UQoFahwapQOS7sygV
 wB69G0a0ZD7T+4MmkxS9rubx31uKRK55WrkAeFjMzjvAlBeEX8R0Np4PnohXzB8v
 TNqjsQDLquO2t15hI2d8UBhEt0aeFR1ZYaPV6tOERHoEkKtiV8wEPYt8g7oSfUfS
 5s47vC5nMgTTibpo6t2Dg1jylrUPnKWVdjAhKb7LqIDsxmnaVR8dRntC6+N5vjPc
 3J02cf0MRp9aEecv/9tXcFmIQw/dFausEXjPNpVqASMXk0WOiU7nZ+y6Goj5zjxq
 79N/CSdmdgpMUldepZQ8p0qAeGeOXR/jPXylPRjXVkGWLoHzboG3jEE9i9BRuO4n
 r5rhINcdJR8cJhr5IPog6+eQcvplO4LFVkvuhi53+j6Us2WD4fpTqHkxxw6DasaC
 /n4DXhgddh4mcB12PCCU0/YmtN75Xd1+/HK6aEn4uhhVjtkWvgYq+eKQ68CMxAb+
 ypmSLYkHVMlOARM7jvjcVSGyYnzcpP2DAScu3u9cPrGv6AeH4K9zccUGqi628Hvi
 /SCPrwZe5gaprLgQbe2sw/uRsVao4QFwsJez8Vj5T3SMY8FV/YXl+6xOGB7Vx0nj
 kL36BBe1lM2DVY7fwbFjhK1TFI85a64h7VeXCkyNX51VK2kga3M=
 =q+QT
 -END PGP SIGNATURE-
 }}}

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

[tor-bugs] #28769 [Internal Services/Tor Sysadmin Team]: Please change email forwarding (several items)

[Tor Bug Tracker & Wiki]

#28769: Please change email forwarding (several items)
-+-
 Reporter:  ewyatt   |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Hello. We need the below changes to email forwarding. The two substantive
 changes were announced by email to tor-internal earlier today. Thank you!

 {{{
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512

 1. Remove Shari from job-anticensor@
 2. Change the forwarding for millicent@ to accounting@
 3. Discontinue email forwarding for tommyc@
 -BEGIN PGP SIGNATURE-
 Comment: GPGTools - https://gpgtools.org

 iQIzBAEBCgAdFiEENecqn2ZVRfkstmYkugyUAPgPkc4FAlwJyN4ACgkQugyUAPgP
 kc5uoQ/+NpcG+gx60Sx6ElW1AWvgoObgaVZGGyqaBHdRFEpWtslFW5l0MN7ZLwzy
 SM0fRD9NuDYh4Cvu2oUS3lKa2mMCFvlGSdPyVTrrR3+6zPlNk5aY5TFNnYAkf8AX
 n68QhEQDXPmZYkPYKNElvge3IniPgsjHkeIyjxiqVB6z1vy4m1sS0DLwH+cqScIU
 KRENEyWYRTd7mKprcMzEIVmyQp1OkyYtFSiT9XXHI3fvq1kfmbilr48owKr1hH5u
 wf2PNPnoMIE3w/PCDH7jrSG9XOqbsqK5STsiGOc/xkRaWeo9zXH3vMpfZFmiZOYt
 AXYq05M4vDLEICQ/NC7DoPewZwyWzhUdxtXoypaN6TB3IYCyq74ptBllY7tknW9W
 V3ceWaS+8kiuyRWHFzPL71HCixMkDka5OzCkIX4qO2CeKyInGBqSfCePw28bpW3z
 fdktWxCu31o15nLFKXaqUaLe7t11t2gEoQxOLvz8Sz57R4vqeprunPCMgew+lMK4
 zO5dxUvMDA4MO9iXPaSv4v0JlveugZUYRFPz8K0SovwpSnhq+9QtJrxn6bxUcKIa
 HDwjyjbqHQHYDgP1rW4iRDS5TjoTI4mk+BuDEX09hrXbsIX7JrPfg6ZK6NPhM+9e
 7LA6cyFADeRtEXf6PGdMRENBUR6m/DgTaFtr3R8Ye7JUTQUPddg=
 =Biig
 -END PGP SIGNATURE-}}}

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

Re: [tor-bugs] #28766 [Applications/Tor Browser]: Tor Build for Android

[Tor Bug Tracker & Wiki]

#28766: Tor Build for Android
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:
  TorBrowserTeam201812   |
Parent ID:  #28704   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by boklm):

 For the linux nightly build, we build rust 1.28.0. Maybe we can do the
 same.

 We can also start by building Tor without rust (like on Windows and
 macOS).

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

Re: [tor-bugs] #28768 [Core Tor/Fallback Scripts]: Update fallback script to match Tor bootstrap changes

[Tor Bug Tracker & Wiki]

#28768: Update fallback script to match Tor bootstrap changes
---+---
 Reporter:  teor   |  Owner:  teor
 Type:  enhancement| Status:  assigned
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.0.x-final
Component:  Core Tor/Fallback Scripts  |Version:
 Severity:  Normal | Resolution:
 Keywords:  fallback   |  Actual Points:
Parent ID:  #24838 | Points:
 Reviewer: |Sponsor:  Sponsor8-can
---+---

Comment (by teor):

 I'll add the code for this ticket to the #24838 branch.

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

Re: [tor-bugs] #28142 [Core Tor/Tor]: Merge original WTF-PAD branch

[Tor Bug Tracker & Wiki]

#28142: Merge original WTF-PAD branch
-+-
 Reporter:  asn  |  Owner:
 |  mikeperry
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad, tor-relay, tor-cell,|  Actual Points:
  padding|
Parent ID:  #28631   | Points:
 Reviewer:  asn  |Sponsor:
 |  Sponsor2
-+-

Comment (by mikeperry):

 OK! Phew. https://github.com/mikeperry-tor/tor/tree/adaptive_padding-
 rebased_0.3.6-pr547-squashed is now the same as
 https://github.com/torproject/tor/pull/547 (head
 7b65aba210f62b3527782705ba867f6ce4a57088) with the type changes. Plus a
 couple tweaks. I think, anyway.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28768 [Core Tor/Fallback Scripts]: Update fallback script to match Tor bootstrap changes

[Tor Bug Tracker & Wiki]

#28768: Update fallback script to match Tor bootstrap changes
---+---
 Reporter:  teor   |  Owner:  teor
 Type:  enhancement| Status:  assigned
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.0.x-final
Component:  Core Tor/Fallback Scripts  |Version:
 Severity:  Normal |   Keywords:  fallback
Actual Points: |  Parent ID:  #24838
   Points: |   Reviewer:
  Sponsor:  Sponsor8-can   |
---+---
 In #24661, we make clients bootstrap from reasonably old consensuses
 (expired in the last 24 hours).

 In #28591, we make clients accept future consensuses as long as they're
 reasonably future consensuses (valid up to 24 hours in the future), and
 relays serve those consensuses.

 We need to change the fallback checks to match these changes in Tor.

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

Re: [tor-bugs] #28591 [Core Tor/Tor]: Accept a future consensus for bootstrap

[Tor Bug Tracker & Wiki]

#28591: Accept a future consensus for bootstrap
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  bootstrap, clock-skew, tor-guard,|  Actual Points:
  usability, ux, s8-errors, 035-roadmap- |
  subtask, 035-triaged-in-20180711,  |
  s8-bootstrap   |
Parent ID:  #23605   | Points:
 Reviewer:  catalyst |Sponsor:
 |  Sponsor8-can
-+-
Changes (by teor):

 * sponsor:   => Sponsor8-can


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

Re: [tor-bugs] #28766 [Applications/Tor Browser]: Tor Build for Android

[Tor Bug Tracker & Wiki]

#28766: Tor Build for Android
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:
  TorBrowserTeam201812   |
Parent ID:  #28704   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by sisbell):

 Tor needs rust 1.28. However for android we are using 1.26.1. How should
 we handle this?

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

Re: [tor-bugs] #28722 [Webpages/Website]: Add cs el hu ka locales to the Tor Browser download pages

[Tor Bug Tracker & Wiki]

#28722: Add cs el hu ka locales to the Tor Browser download pages
--+--
 Reporter:  boklm |  Owner:  boklm
 Type:  task  | Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201812  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by boklm):

 * cc: arthuredelstein (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] #28722 [Webpages/Website]: Add cs el hu ka locales to the Tor Browser download pages

[Tor Bug Tracker & Wiki]

#28722: Add cs el hu ka locales to the Tor Browser download pages
--+--
 Reporter:  boklm |  Owner:  boklm
 Type:  task  | Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201812  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by boklm):

 #28767 is a duplicate.

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

Re: [tor-bugs] #28767 [Webpages]: Add links for TBB 8.5a cs, el, hu, ka locales

[Tor Bug Tracker & Wiki]

#28767: Add links for TBB 8.5a cs, el, hu, ka locales
-+---
 Reporter:  arthuredelstein  |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Webpages |Version:
 Severity:  Normal   | Resolution:  duplicate
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by boklm):

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


Comment:

 This is a duplicate of #28722.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28767 [Webpages]: Add links for TBB 8.5a cs, el, hu, ka locales

[Tor Bug Tracker & Wiki]

#28767: Add links for TBB 8.5a cs, el, hu, ka locales
-+
 Reporter:  arthuredelstein  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Webpages |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+


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

Re: [tor-bugs] #25164 [Applications/Tor Browser]: Reproducible Tor Browser for Android builds

[Tor Bug Tracker & Wiki]

#25164: Reproducible Tor Browser for Android builds
---+--
 Reporter:  sysrqb |  Owner:  tbb-team
 Type:  enhancement| Status:  closed
 Priority:  Very High  |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  tbb-mobile, TorBrowserTeam201812R  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  Sponsor8
---+--
Changes (by gk):

 * status:  reopened => closed
 * keywords:  tbb-mobile, TorBrowserTeam201812 => tbb-mobile,
 TorBrowserTeam201812R
 * resolution:   => fixed


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

Re: [tor-bugs] #25164 [Applications/Tor Browser]: Reproducible Tor Browser for Android builds

[Tor Bug Tracker & Wiki]

#25164: Reproducible Tor Browser for Android builds
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  enhancement   | Status:  reopened
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, TorBrowserTeam201812  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor8
--+--
Changes (by gk):

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


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

Re: [tor-bugs] #28697 [Applications/Tor Browser]: Our QA and testing .apks are signed with a key per build

[Tor Bug Tracker & Wiki]

#28697: Our QA and testing .apks are signed with a key per build
---+--
 Reporter:  gk |  Owner:  tbb-team
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  tbb-mobile, TorBrowserTeam201812R  |  Actual Points:
Parent ID:  #25164 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by gk):

 * parent:   => #25164


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

Re: [tor-bugs] #28697 [Applications/Tor Browser]: Our QA and testing .apks are signed with a key per build

[Tor Bug Tracker & Wiki]

#28697: Our QA and testing .apks are signed with a key per build
---+--
 Reporter:  gk |  Owner:  tbb-team
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  tbb-mobile, TorBrowserTeam201812R  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by gk):

 * parent:  #25164 =>


Comment:

 Replying to [comment:15 boklm]:
 > Replying to [comment:14 gk]:
 > > boklm: let me know whether you think we should change anything of my
 commit (commit 60163914e4f9418709bfe5b8fdc946fb56ca6e07). (I know I messed
 up the bug number which is highly annoying, but a thing we can't change
 anymore).
 >
 > I think the line `arch: amd64` is not needed as we already set it to
 this value in rbm.conf. Otherwise this looks good.

 Good point. Fixed in a follow-up commit
 (0a2cc62f08063cc0c91b1db57e87505c954349a9) on `master` (with a better bug
 number.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28766 [Applications/Tor Browser]: Tor Build for Android

[Tor Bug Tracker & Wiki]

#28766: Tor Build for Android
-+-
 Reporter:  sisbell  |  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  tbb-mobile, tbb-rbm,
 Severity:  Normal   |  TorBrowserTeam201812
Actual Points:   |  Parent ID:  #28704
   Points:   |   Reviewer:
  Sponsor:   |
-+-


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

[tor-bugs] #28765 [Applications/Tor Browser]: LibEvent Build for Android

[Tor Bug Tracker & Wiki]

#28765: LibEvent Build for Android
-+-
 Reporter:  sisbell  |  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  tbb-mobile, tbb-rbm,
 Severity:  Normal   |  TorBrowserTeam201812
Actual Points:   |  Parent ID:  #28704
   Points:   |   Reviewer:
  Sponsor:   |
-+-


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

[tor-bugs] #28764 [Applications/Tor Browser]: OpenSSL Build for Android

[Tor Bug Tracker & Wiki]

#28764: OpenSSL Build for Android
-+-
 Reporter:  sisbell  |  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  tbb-mobile, tbb-rbm,
 Severity:  Normal   |  TorBrowserTeam201812
Actual Points:   |  Parent ID:  #28704
   Points:   |   Reviewer:
  Sponsor:   |
-+-


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

Re: [tor-bugs] #28763 [Applications/Tor Browser]: Create Tor-Android Project

[Tor Bug Tracker & Wiki]

#28763: Create Tor-Android Project
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:
  TorBrowserTeam201812   |
Parent ID:  #28704   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by sisbell):

 The projects that tor-android is dependent on are:

  1. libevent (included patch)
  1. openssl
  1. tor
  1. zstd -!https://github.com/facebook/zstd (not sure how the project is
 using this)
  1. lzma (not sure how the project is using this)

 The first 3 we already have tor-browser-build projects for.

 !https://github.com/n8fr8/tor-android/tree/master/external

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

Re: [tor-bugs] #28752 [Applications/Tor Browser]: Gradle sometimes downloads tor-android-binary resources during build (or the build is failing)

[Tor Bug Tracker & Wiki]

#28752: Gradle sometimes downloads tor-android-binary resources during build (or
the build is failing)
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:
  TorBrowserTeam201812   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 Replying to [comment:2 sisbell]:
 > Gradle offline is flagged so it shouldn't download anything (although
 there can always be a bug in gradle). It could be that the files are not
 actually downloading even though the logs say it is attempting download.
 Did the build say it was downloading and then pass the build. Or did it
 say it was downloading and then fail the build?

 It says it was downloading
 {{{
 26:02.41
 :geckoview:compileOfficialWithGeckoBinariesNoMinApiReleaseJavaWithJavac
 26:02.43 Download
 https://raw.githubusercontent.com/guardianproject/gpmaven/master/org/torproject
 /tor-android-binary/0.3.4.9/tor-android-binary-0.3.4.9.pom
 26:04.40 Download
 https://raw.githubusercontent.com/guardianproject/gpmaven/master/org/torproject
 /tor-android-binary/0.3.4.9/tor-android-binary-0.3.4.9.aar
 26:04.91
 
:app:generateOfficialWithoutGeckoBinariesNoMinApiPhotonDebugAndroidTestResValues
 }}}
 and then the build passed. My guess is that in the rare cases I saw the
 build failures this resulted in the download failing for some reason. And
 later on the missing dependencies were not available.

 The big question is why it is downloading those things and just those two
 even though we bundled everything.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28763 [Applications/Tor Browser]: Create Tor-Android Project

[Tor Bug Tracker & Wiki]

#28763: Create Tor-Android Project
-+-
 Reporter:  sisbell  |  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  tbb-mobile, tbb-rbm,
 Severity:  Normal   |  TorBrowserTeam201812
Actual Points:   |  Parent ID:  #28704
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 The tor-android repo contains a TorResourceInstaller. This is an
 !Android/Java library that Orbot uses. We need this.

 The tor-android repo also contains the native Tor libraries. We don't want
 to use these. So the Tor-Android project will need to depend on our own
 versions of these native libraries.

 !https://github.com/n8fr8/tor-android

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

Re: [tor-bugs] #25164 [Applications/Tor Browser]: Reproducible Tor Browser for Android builds

[Tor Bug Tracker & Wiki]

#25164: Reproducible Tor Browser for Android builds
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  enhancement   | Status:  closed
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  tbb-mobile, TorBrowserTeam201812  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor8
--+--

Comment (by boklm):

 Replying to [comment:26 gk]:
 > We are good here. I added the .apk to our `sha265sum` step now that it
 is reproducible in commit 3d7c32b67b25d869d94ec8f23da82e7558fb9993 to get
 our build going. boklm: let me know whether you are good with that commit.

 This commit looks good to me.

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

Re: [tor-bugs] #28682 [- Select a component]: Carml lacks PGP singatures and instructions for secure installation

[Tor Bug Tracker & Wiki]

#28682: Carml lacks PGP singatures and instructions for secure installation
--+--
 Reporter:  wagon |  Owner:  meejah
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:  carml |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by meejah):

 Note that I do sign the tags (but they don't include locked/hashed
 dependencies).

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

Re: [tor-bugs] #25164 [Applications/Tor Browser]: Reproducible Tor Browser for Android builds

[Tor Bug Tracker & Wiki]

#25164: Reproducible Tor Browser for Android builds
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  enhancement   | Status:  closed
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  tbb-mobile, TorBrowserTeam201812  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor8
--+--
Changes (by boklm):

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


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

Re: [tor-bugs] #25164 [Applications/Tor Browser]: Reproducible Tor Browser for Android builds

[Tor Bug Tracker & Wiki]

#25164: Reproducible Tor Browser for Android builds
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  enhancement   | Status:  reopened
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, TorBrowserTeam201812  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor8
--+--
Changes (by boklm):

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


Comment:

 (I am temporarily reopening this ticket to set it as parent for #28697)

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

Re: [tor-bugs] #28697 [Applications/Tor Browser]: Our QA and testing .apks are signed with a key per build

[Tor Bug Tracker & Wiki]

#28697: Our QA and testing .apks are signed with a key per build
---+--
 Reporter:  gk |  Owner:  tbb-team
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  tbb-mobile, TorBrowserTeam201812R  |  Actual Points:
Parent ID:  #25164 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by boklm):

 * parent:   => #25164


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

Re: [tor-bugs] #28752 [Applications/Tor Browser]: Gradle sometimes downloads tor-android-binary resources during build (or the build is failing)

[Tor Bug Tracker & Wiki]

#28752: Gradle sometimes downloads tor-android-binary resources during build (or
the build is failing)
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:
  TorBrowserTeam201812   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by sisbell):

 The tor-android-binary is the only artifact hosted on
 githubusercontent.com. One possibility could be that the host is returning
 some error page and the script is treating it as downloaded.  So the
 gradle build script would then detect it is bad and try again. What does
 this file look like in the gradle-dependencies-3 directory?

 Gradle offline is flagged so it shouldn't download anything (although
 there can always be a bug in gradle). It could be that the files are not
 actually downloading even though the logs say it is attempting download.
 Did the build say it was downloading and then pass the build. Or did it
 say it was downloading and then fail the build?

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

Re: [tor-bugs] #28697 [Applications/Tor Browser]: Our QA and testing .apks are signed with a key per build

[Tor Bug Tracker & Wiki]

#28697: Our QA and testing .apks are signed with a key per build
---+--
 Reporter:  gk |  Owner:  tbb-team
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  tbb-mobile, TorBrowserTeam201812R  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by boklm):

 * parent:  #25164 =>


Comment:

 Replying to [comment:14 gk]:
 > boklm: let me know whether you think we should change anything of my
 commit (commit 60163914e4f9418709bfe5b8fdc946fb56ca6e07). (I know I messed
 up the bug number which is highly annoying, but a thing we can't change
 anymore).

 I think the line `arch: amd64` is not needed as we already set it to this
 value in rbm.conf. Otherwise this 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] #28682 [- Select a component]: Carml lacks PGP singatures and instructions for secure installation

[Tor Bug Tracker & Wiki]

#28682: Carml lacks PGP singatures and instructions for secure installation
--+--
 Reporter:  wagon |  Owner:  meejah
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:  carml |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by meejah):

 Yes, please file tickets on github: https://github.com/meejah/carml/issues

 And yes, all the above points are valid and true; as carml started as a
 bunch of random utilities I valued "release easily and quickly" over
 "securely". However, that should be corrected.

 Can you please file this as 3 separate tickets? 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] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by loskiq):

 I just installed the bridge version 0.2.9.17, and the client immediately
 started working. I believe that the problem of 25% is related to the new
 version of the bridge.

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

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by loskiq):

 I have just tested working with another obfs4 bridge received from
 brid...@torproject.org. The problem persists. Stuck in 25%. But there is a
 bridge with which the client works correctly.

 The bridges I checked:

 Not worked
 {{{
 obfs4 154.16.245.120:443 072AF4D16146012D6E8DFA8518B169345D8CEA51
 cert=/nZrKfIZrw39ij9PLfoY0Uq+CCyQIYpP0BefZJbe2yf9cbJtXynlsWLwV77pVbKK4xDvHw
 iat-mode=0
 }}}

 Worked
 {{{
 obfs4 93.190.138.248:41248 577059FF2CADFB6AEFBCC78FFAB4DBEC1AF8A57B
 cert=d5ijyl75isX32Vx9yQkSDZicYPiamD413fnyKf/5TQxBTytobCVrzX7ATtBKZGOwIQ4IYg
 iat-mode=0
 }}}

 I think this problem is related to bridges, not clients...

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

Re: [tor-bugs] #28740 [Applications/Tor Browser]: Make navigator.platform return "Win32", even on Win64 OS

[Tor Bug Tracker & Wiki]

#28740: Make navigator.platform return "Win32", even on Win64 OS
-+-
 Reporter:  omg  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  GeorgKoppen201812,   |  Actual Points:
  TorBrowserTeam201812R, tbb-backport|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * status:  needs_review => closed
 * keywords:  GeorgKoppen201812, TorBrowserTeam201812R => GeorgKoppen201812,
 TorBrowserTeam201812R, tbb-backport
 * resolution:   => fixed


Comment:

 Thanks. Merged to `tor-browser-60.3.0esr-8.5-1` (commit
 a3cbc068df86e03a6420bc863be2793e35078fa3). Marking for possible backport.

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

Re: [tor-bugs] #25164 [Applications/Tor Browser]: Reproducible Tor Browser for Android builds

[Tor Bug Tracker & Wiki]

#25164: Reproducible Tor Browser for Android builds
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  enhancement   | Status:  closed
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  tbb-mobile, TorBrowserTeam201812  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor8
--+--
Changes (by gk):

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


Comment:

 We are good here. I added the .apk to our `sha265sum` step now that it is
 reproducible in commit 3d7c32b67b25d869d94ec8f23da82e7558fb9993 to get our
 build going. boklm: let me know whether you are good with that commit.

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

Re: [tor-bugs] #28697 [Applications/Tor Browser]: Our QA and testing .apks are signed with a key per build

[Tor Bug Tracker & Wiki]

#28697: Our QA and testing .apks are signed with a key per build
---+--
 Reporter:  gk |  Owner:  tbb-team
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  tbb-mobile, TorBrowserTeam201812R  |  Actual Points:
Parent ID:  #25164 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by gk):

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


Comment:

 Okay, I tested a bunch of things. The problem goes away with Debian Jessie
 and `openjdk-7` or Debian Buster. I don't know why (yet) but opted for the
 latter to get our build going and get the .apk reproducible.

 I picked sisbell's patch and applied it to `master` (commit
 ea1d0b24448f0365b9c8ff60a6ab2c4a130ec279)and made an additional commit
 switching to Buster for the tor-browser step. This seems like low risk as
 I doubt the `jarsigner` tool is changing behavior here drastically in case
 newer packages arrive in Buster.

 boklm: let me know whether you think we should change anything of my
 commit (commit 60163914e4f9418709bfe5b8fdc946fb56ca6e07). (I know I messed
 up the bug number which is highly annoying, but a thing we can't change
 anymore).

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

Re: [tor-bugs] #28353 [Metrics/Website]: Use Guard & Exit, Guard only, Exit only, and Middle only on all bandwidth by flag graphs

[Tor Bug Tracker & Wiki]

#28353: Use Guard & Exit, Guard only, Exit only, and Middle only on all 
bandwidth
by flag graphs
-+--
 Reporter:  teor |  Owner:  metrics-team
 Type:  defect   | Status:  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #28328   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Great! Pushed and deployed the first commit. We'll have two more weeks to
 finalize the color discussion, missing patch (to remove the two obsolete
 graphs), and for a more detailed review. 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] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by loskiq):

 It seems with obfs4proxy all right

 Replying to [comment:14 dcf]:

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

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by loskiq):

 * Attachment "obfs4proxy_client.log" added.

 obfs4proxy log of client

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

Re: [tor-bugs] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by loskiq):

 * Attachment "obfs4proxy_server.log" added.

 obfs4proxy log of server

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

Re: [tor-bugs] #28738 [Core Tor/sbws]: Stop merging multiple torrc options with the same name

[Tor Bug Tracker & Wiki]

#28738: Stop merging multiple torrc options with the same name
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  sbws: 1.0.x-final
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by juga):

 * status:  new => needs_review


Comment:

 https://github.com/torproject/sbws/pull/308

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

Re: [tor-bugs] #28762 [Core Tor/sbws]: Wrong sbws git repo link

[Tor Bug Tracker & Wiki]

#28762: Wrong sbws git repo link
---+---
 Reporter:  anadahz|  Owner:  (none)
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  sbws: 1.0.x-final
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by juga):

 * milestone:   => sbws: 1.0.x-final


Comment:

 Setting milestone, this seems basic for new deployment

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

Re: [tor-bugs] #28762 [Core Tor/sbws]: Wrong sbws git repo link

[Tor Bug Tracker & Wiki]

#28762: Wrong sbws git repo link
---+--
 Reporter:  anadahz|  Owner:  (none)
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by juga):

 Replying to [comment:3 anadahz]:
 > Replying to [comment:2 juga]:
 > > What's wrong with https://gitweb.torproject.org/sbws.git?, it's our
 canonical git repository.
 >
 > You cannot clone the gitweb "version" of torproject.org git repository.

 Oh, you're right it's git.torproject.org/sbws.git

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

Re: [tor-bugs] #28762 [Core Tor/sbws]: Wrong sbws git repo link

[Tor Bug Tracker & Wiki]

#28762: Wrong sbws git repo link
---+--
 Reporter:  anadahz|  Owner:  (none)
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by anadahz):

 Replying to [comment:2 juga]:
 > What's wrong with https://gitweb.torproject.org/sbws.git?, it's our
 canonical git repository.

 You cannot clone the gitweb "version" of torproject.org git repository.

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

Re: [tor-bugs] #28762 [Core Tor/sbws]: Wrong sbws git repo link

[Tor Bug Tracker & Wiki]

#28762: Wrong sbws git repo link
---+--
 Reporter:  anadahz|  Owner:  (none)
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by juga):

 What's wrong with https://gitweb.torproject.org/sbws.git?, it's our
 canonical git repository.

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

Re: [tor-bugs] #28300 [Core Tor/Stem]: Scrolling support for tor-prompt is needed

[Tor Bug Tracker & Wiki]

#28300: Scrolling support for tor-prompt is needed
---+--
 Reporter:  wagon  |  Owner:  atagar
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:  Tor: 0.3.4.8
 Severity:  Normal | Resolution:  wontfix
 Keywords:  tor-prompt |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by wagon):

 > Sounds like your other ticket's covering that.
 Yes. Both problems I reported about in above comments are appeared to be
 core Tor issues: #28757, #28760.
 > If you need something from me let me know.
 I think you could add SAFECOOKIE auth example from
 [[http://ea5faa5po25cf7fb.onion/projects/tor/ticket/28295#comment:7|this
 comment]] to doc page as I suggested.

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

Re: [tor-bugs] #28759 [Core Tor/sbws]: Upload sbws to PyPI

[Tor Bug Tracker & Wiki]

#28759: Upload sbws to PyPI
---+
 Reporter:  anadahz|  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by juga):

 I'd mark this wontfix, though should search for the relevant link in order
 to demonstrate this is not just my personal opinion.

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

Re: [tor-bugs] #28759 [Core Tor/sbws]: Upload sbws to PyPI

[Tor Bug Tracker & Wiki]

#28759: Upload sbws to PyPI
---+
 Reporter:  anadahz|  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by juga):

 Using PyPi is discouraged because of security

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

Re: [tor-bugs] #28758 [Core Tor/sbws]: Add requirements files

[Tor Bug Tracker & Wiki]

#28758: Add requirements files
---+
 Reporter:  anadahz|  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by juga):

 I'd mark this wontfix, though should search for the relevant link in order
 to demonstrate this is not just my personal opinion.

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

Re: [tor-bugs] #28758 [Core Tor/sbws]: Add requirements files

[Tor Bug Tracker & Wiki]

#28758: Add requirements files
---+
 Reporter:  anadahz|  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by juga):

 requirements files are only used to provide "pinned" versions, but after
 some times they might conflict with system libraries.
 They are not needed having a setup.py, in which one specifies a bigger
 range of versions and can be used by system packages.

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

Re: [tor-bugs] #28762 [Core Tor/sbws]: Wrong sbws git repo link

[Tor Bug Tracker & Wiki]

#28762: Wrong sbws git repo link
---+--
 Reporter:  anadahz|  Owner:  (none)
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by anadahz):

 * 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

[tor-bugs] #28762 [Core Tor/sbws]: Wrong sbws git repo link

[Tor Bug Tracker & Wiki]

#28762: Wrong sbws git repo link
---+
 Reporter:  anadahz|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 Install instructions file
 [http://jqs44zhtxl2uo6gk.onion/sbws.git/tree/INSTALL.rst#n46 INSTALL.rst]
 point to a wrong link clone sbws.

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

Re: [tor-bugs] #28757 [Core Tor/Tor]: Remove deprecated ControlPort commands from GETINFO info/names listing

[Tor Bug Tracker & Wiki]

#28757: Remove deprecated ControlPort commands from GETINFO info/names listing
---+--
 Reporter:  wagon  |  Owner:  atagar
 Type:  defect | Status:  reopened
 Priority:  Medium |  Milestone:
Component:  Core Tor/Tor   |Version:  Tor: 0.3.4.9
 Severity:  Normal | Resolution:
 Keywords:  tor-control, tor-spec  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by wagon):

 > This means that the help output will list all `GETINFO` commands tor
 itself advertises (including new features in the future)
 Good, I didn't know about it. It means it is not Nyx, but core Tor's bug.
 I reopen the ticket and ascribe it to Tor team. Maybe teor will take care
 about 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] #28757 [Core Tor/Tor]: Remove deprecated ControlPort commands from GETINFO info/names listing (was: Remove deprecated ControlPort commands from controller interpreter's /help)

[Tor Bug Tracker & Wiki]

#28757: Remove deprecated ControlPort commands from GETINFO info/names listing
---+--
 Reporter:  wagon  |  Owner:  atagar
 Type:  defect | Status:  reopened
 Priority:  Medium |  Milestone:
Component:  Core Tor/Tor   |Version:  Tor: 0.3.4.9
 Severity:  Normal | Resolution:
 Keywords:  tor-control, tor-spec  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by wagon):

 * status:  closed => reopened
 * component:  Core Tor/Nyx => Core Tor/Tor
 * version:   => Tor: 0.3.4.9
 * keywords:   => tor-control, tor-spec
 * resolution:  worksforme =>


Comment:

 > This means that the help output will list all `GETINFO` commands tor
 itself advertises (including new features in the future)
 Good, I didn't know about it. It means it is not Nyx, but core Tor's bug.
 I reopen the ticket and ascribe it to Tor team. Maybe teor will take care
 about 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] #28676 [Core Tor/Tor]: Tor versions of Tor nodes should be accessible through ControlPort

[Tor Bug Tracker & Wiki]

#28676: Tor versions of Tor nodes should be accessible through ControlPort
--+--
 Reporter:  wagon |  Owner:  arma
 Type:  enhancement   | Status:  assigned
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #24110| Points:
 Reviewer:|Sponsor:
--+--

Comment (by wagon):

 > There are millions of tor clients, and they use microdescriptors and the
 microdesc consensus (md) by default. So we need to minimise the size of md
 documents.
 OK. However, most of these clients download consensus files from mirrors
 on other relays, i.e. not from authorities.
 > We have proposals that would create a new consensus flavour (picodesc
 consensus? pd?) with fewer fields. Once all supported Tor versions use the
 pd consensus, we can stop distributing the microdesc consensus.
 Ok. I see Tor development is moving in opposite direction than that I
 thought about. I hope Tor people make right decisions.
 > Or, more likely, distribute a md consensus containing no relays.
 What does it mean? What is the point of having consensus which contain no
 information about relays?
 > Please open one ticket per bug. Otherwise, we lose track of bugs.
 Done: #28757, #28760.
 > You can bind `ControlPort` to a non-local port, but you must have
 authentication on
 How I can do this technically? I cannot see any option in `man torrc`
 about that. According to `man` page `ControlPort` specifies only port and
 not `IP:port`.
 > I'm not sure how we could keep a man page and the control spec in sync,
 without it taking a lot of effort.
 Spec was not updated so often until now. However, if you plan to re-
 architect all `ControlPort` internals, it is better to wait until new
 interface will be stable.

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

Re: [tor-bugs] #28757 [Core Tor/Nyx]: Remove deprecated ControlPort commands from controller interpreter's /help

[Tor Bug Tracker & Wiki]

#28757: Remove deprecated ControlPort commands from controller interpreter's 
/help
--+
 Reporter:  wagon |  Owner:  atagar
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Core Tor/Nyx  |Version:
 Severity:  Normal| Resolution:  worksforme
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by atagar):

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


Comment:

 Hi wagon. Nyx (and by extension Stem's) '/help GETINFO' listing
 [https://gitweb.torproject.org/stem.git/tree/stem/interpreter/help.py#n78
 comes from tor itself] through its 'GETINFO info/names' command. This
 means that the help output will list all GETINFO commands tor itself
 advertises (including new features in the future). When your tor instance
 no longer supports that command it will cease to be listed.

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

Re: [tor-bugs] #28761 [Core Tor/sbws]: sbws ignores config option `to_sylog` (was: sbsw ignores config option `to_sylog`)

[Tor Bug Tracker & Wiki]

#28761: sbws ignores config option `to_sylog`
---+
 Reporter:  anadahz|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Major  | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

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

[tor-bugs] #28761 [Core Tor/sbws]: sbsw ignores config option `to_sylog`

[Tor Bug Tracker & Wiki]

#28761: sbsw ignores config option `to_sylog`
---+
 Reporter:  anadahz|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Major  |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 sbws seems to ignore the config option `to_sylog`

 `sbws version 1.0.3-dev0 with python 3.6.7 on Linux-4.9.0-8-amd64-x86_64
 -with-debian-9.6, stem 1.7.0, and requests 2.20.1`

 Excerpt of `/etc/sbws/sbws.ini`:
 {{{
 [logging]
 # Whether or not to log to syslog
 to_syslog = no
 }}}

 Complete [https://raw.githubusercontent.com/anadahz/sbws-
 ansible/master/roles/sbws-ansible/defaults/main.yml | sbws.ini] file used.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28760 [Core Tor/Tor]: Option/* format for ControlPort options needs to be homogeneous

[Tor Bug Tracker & Wiki]

#28760: Option/* format for ControlPort options needs to be homogeneous
---+--
 Reporter:  wagon  |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Component:  Core Tor/Tor
  Version:  Tor: 0.3.4.9   |   Severity:  Normal
 Keywords:  tor-control, tor-spec  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
 According to [[https://gitweb.torproject.org/torspec.git/tree/control-
 spec.txt|control-spec.txt]]:

 > The OptionPrefix form indicates a number of options beginning with the
 prefix. So if `config/*` is listed, other options beginning with `config/`
 will work, but `config/*` itself is not an option.

 In Nyx and `tor-prompt` interpreters' `/help`, if the format `Option/*` is
 used to name a group of options (each of them is still described
 separately), it must be done for everything. However, e.g., we have many
 options inside `accounting`, but key `accounting/*` doesn't exist:

 {{{
 accounting/bytes  - Number of bytes read/written so far in the
 accounting interval.
 accounting/bytes-left - Number of bytes left to write/read so far in
 the accounting interval.
 accounting/enabled- Is accounting currently enabled?
 accounting/hibernating- Are we hibernating or awake?
 accounting/interval-end   - Time when the accounting period ends.
 accounting/interval-start - Time when the accounting period starts.
 accounting/interval-wake  - Time to wake up in this accounting period.
 }}}

 Compare it with:

 {{{
 config/*  - Current configuration values.
 config/defaults   - List of default values for configuration
 options. See also config/names
 config/names  - List of configuration options, types, and
 documentation.
 }}}

 If grouping syntax is used, it should be used everywhere (for all groups)
 or nowhere. Otherwise, it is confusing, because for many other options the
 syntax `option/*` implies that something not listed here (in list of
 options) should be substituted (e.g. fingerprint of a relay, IP address,
 etc.).

 P.S. At first glance it looks like Nyx controller interpreter's bug, but
 atagar
 [[https://trac.torproject.org/projects/tor/ticket/28300#comment:5|says]]
 that it is taken literally from `control-spec.txt`. Initially it was
 reported in
 [[https://trac.torproject.org/projects/tor/ticket/28300#comment:6|this
 comment]]. Separate ticket was created because of
 [[https://trac.torproject.org/projects/tor/ticket/28676#comment:8|teor's
 suggestion]].

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

Re: [tor-bugs] #28740 [Applications/Tor Browser]: Make navigator.platform return "Win32", even on Win64 OS

[Tor Bug Tracker & Wiki]

#28740: Make navigator.platform return "Win32", even on Win64 OS
-+-
 Reporter:  omg  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  GeorgKoppen201812,   |  Actual Points:
  TorBrowserTeam201812R  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by mcs):

 r=brade, r=mcs
 Matching the value returned by recent versions of Firefox (as well as
 Chrome and Edge) seems like a good idea.

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

Re: [tor-bugs] #28555 [Metrics/Analysis]: Assess methodology for modern privcount Tor user counts

[Tor Bug Tracker & Wiki]

#28555: Assess methodology for modern privcount Tor user counts
--+--
 Reporter:  arma  |  Owner:  metrics-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Metrics/Analysis  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor19
--+--

Comment (by arma):

 I've been avoiding the word concurrent, because to me it implies that two
 users are concurrent if they are both interacting with the Tor network at
 the same time. Whereas this daily user count is the total number of people
 who, some time during the day, have had a Tor client online.

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

Re: [tor-bugs] #26280 [Applications/Tor Browser]: Icon in applications switching on Gnome is blurry/pixelated

[Tor Bug Tracker & Wiki]

#26280: Icon in applications switching on Gnome is blurry/pixelated
--+---
 Reporter:  Porkepix  |  Owner:  pospeselr
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:  #25702| Points:
 Reviewer:|Sponsor:
--+---
Changes (by pospeselr):

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


Comment:

 Works for me, likely fixed in #26556

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

Re: [tor-bugs] #28755 [Core Tor/Tor]: Implement a K/V parser library

[Tor Bug Tracker & Wiki]

#28755: Implement a K/V parser library
--+
 Reporter:  dgoulet   |  Owner:  nickm
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  .3
Parent ID:  #25502| Points:
 Reviewer:  ahf, dgoulet  |Sponsor:
--+
Changes (by dgoulet):

 * reviewer:   => ahf, 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] #28755 [Core Tor/Tor]: Implement a K/V parser library

[Tor Bug Tracker & Wiki]

#28755: Implement a K/V parser library
--+
 Reporter:  dgoulet   |  Owner:  nickm
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  .3
Parent ID:  #25502| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  assigned => needs_review
 * actualpoints:   => .3


Comment:

 Branch `ticket28755` has my first take on this.  PR at
 https://github.com/torproject/tor/pull/568 .  More testing and/or fuzzing
 might be a good idea here.

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

Re: [tor-bugs] #26280 [Applications/Tor Browser]: Icon in applications switching on Gnome is blurry/pixelated

[Tor Bug Tracker & Wiki]

#26280: Icon in applications switching on Gnome is blurry/pixelated
--+---
 Reporter:  Porkepix  |  Owner:  pospeselr
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25702| Points:
 Reviewer:|Sponsor:
--+---
Changes (by mcs):

 * 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

[tor-bugs] #28759 [Core Tor/sbws]: Upload sbws to PyPI

[Tor Bug Tracker & Wiki]

#28759: Upload sbws to PyPI
---+
 Reporter:  anadahz|  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 Package sbws and upload it to the Python Package Index repository.

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

[tor-bugs] #28758 [Core Tor/sbws]: Add requirements files

[Tor Bug Tracker & Wiki]

#28758: Add requirements files
---+
 Reporter:  anadahz|  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 Add a requirements.txt file with the required sbws dependencies.

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

Re: [tor-bugs] #26843 [Applications/Tor Browser]: TBA: Investigate how Mozilla Fennec provides localization

[Tor Bug Tracker & Wiki]

#26843: TBA: Investigate how Mozilla Fennec provides localization
-+-
 Reporter:  sysrqb   |  Owner:  tbb-
 |  team
 Type:  task | Status:  closed
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-mobile, TBA-a2,  |  Actual Points:
  GeorgKoppen201812, TorBrowserTeam201812|
Parent ID:  #26782   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

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


Comment:

 Replying to [comment:27 gk]:
 > Replying to [comment:26 boklm]:
 > > In `bug_26843_v6`, I added a commit that will get the json file from
 our `tor-browser.git` clone:
 > > https://gitweb.torproject.org/user/boklm/tor-browser-
 build.git/commit/?h=bug_26843_v6=1cffd6ce018e4114fa0e814602d5793646e6b10b
 > >
 > > To get the json file we use the `exec()` function, which will checkout
 the `git_hash` commit and run the command from there.
 >
 > You used `cat browser/locales/l10n-changesets.json` but we should take
 the .json file for now from the mobile directory as the l10n repos and
 revisions are used for Android only at the moment. Thus, `cat
 mobile/locales/l10n-changesets.json`. Otherwise this looks reasonable. I
 still need to test it, though.

 Alright, that seems to work. I compared the mobile/locales/ and the
 browser/locales/ l10n-changesets.json and it seems they differ a bit.
 Looking at https://product-details.mozilla.org/1.0/l10n/Firefox-60.3.0esr-
 build1.json it seems that one mirrors the file in browser/locales. Thus,
 as we ship for mobile I think it is good to use the one on mobile/locales
 instead.

 To save a roundtrip I've made that small change in the patch myself. The
 result is commit bad46e532fa614ffdd3ed0e21f4b8fae3ba7793d on `master`.

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

[tor-bugs] #28757 [Core Tor/Nyx]: Remove deprecated ControlPort commands from controller interpreter's /help

[Tor Bug Tracker & Wiki]

#28757: Remove deprecated ControlPort commands from controller interpreter's 
/help
+--
 Reporter:  wagon   |  Owner:  atagar
 Type:  defect  | Status:  assigned
 Priority:  Medium  |  Component:  Core Tor/Nyx
  Version:  |   Severity:  Normal
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
 If `GETINFO` commands `status/version/num-concurring` and `status/version
 /num-versioning` are used in Nyx or `tor-prompt`, Tor writes to its log
 file:

 {{{
 [warn] status/version/num-concurring is deprecated; it no longer gives
 useful information
 [warn] status/version/num-versioning is deprecated; it no longer gives
 useful information
 }}}

 These commands should be removed from interpreter's `/help GETINFO`
 listing. They are deprecated according to
 [[https://gitweb.torproject.org/torspec.git/tree/control-spec.txt|control-
 spec.txt]]:

 {{{
 "status/version/num-concurring"
 "status/version/num-versioning"
   These options are deprecated; they no longer give useful information.
 }}}

 [[https://blog.torproject.org/tor-02030-released-stable|since 0.2.0.30]]
 (more than 10 years):

 > o Newly deprecated features:
 > - The `status/version/num-versioning` and `status/version/num-
 concurring` `GETINFO` controller options are no longer useful in the v3
 directory protocol: treat them as deprecated, and warn when they're used.

 Probably, there are also other deprecated commands in `/help` listing.
 They should be removed too.

 P.S. Initially it was reported in
 [[https://trac.torproject.org/projects/tor/ticket/28300#comment:4|this
 comment]]. teor
 
[[http://ea5faa5po25cf7fb.onion/projects/tor/ticket/28676#comment:8|recommended]]
 to create separate 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] #28717 [Core Tor/Tor]: Tor stuck in 25% Loading networkstatus consensus

[Tor Bug Tracker & Wiki]

#28717: Tor stuck in 25% Loading networkstatus consensus
--+--
 Reporter:  loskiq|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.9
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by dcf):

 Replying to [comment:13 loskiq]:
 > By the way, with the same configuration, the client successfully works
 with other bridges.

 I see. This means my guess was wrong.

 I don't have any other good ideas, except to turn on obfs4proxy logging.
 In the client torrc, use
 {{{
 ClientTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy --enableLogging
 --logLevel=DEBUG
 }}}
 In the bridge torrc, use
 {{{
 ServerTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy --enableLogging
 --logLevel=DEBUG
 }}}
 In both cases, the log file will appear in
 /pt_state/obfs4proxy.log.

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

Re: [tor-bugs] #28725 [Applications/Tor Browser]: Upgrade go-webrtc to dcbfc825aa33471253a5da1834d499257e05d557

[Tor Bug Tracker & Wiki]

#28725: Upgrade go-webrtc to dcbfc825aa33471253a5da1834d499257e05d557
-+-
 Reporter:  dcf  |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake tbb-rbm,   |  Actual Points:
  TorBrowserTeam201812R  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by dcf):

 * status:  needs_revision => needs_review
 * keywords:  snowflake tbb-rbm, TorBrowserTeam201812 => snowflake tbb-rbm,
 TorBrowserTeam201812R


Comment:

 Sorry about that. I didn't get any error from a full `make testbuild`,
 neither when I originally staged the patch on
 3e75d4bbf273c1494ff9442c67c0dda1f86c6eac, nor when I tried rebasing on
 30c764db2bbbde93ebee67e2b190a4d9c88873b9 yesterday. I don't even have a
 directory called `gclient/webrtc/src/third_party/llvm`; mine is called
 `gclient/webrtc/src/third_party/llvm-build`.

 Nevertheless, I am guessing from the error message that there is a problem
 with whitespace in filenames. Here's a revised patch that rewrites the
 `for` loops to instead use whitespace-safe `find -print0` and `xargs -0`.
 This additional patch doesn't affect the output for me; i.e., my
 corresponding out/webrtc/webrtc-*.tar.gz files are the same except for the
 gzip timestamp.

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

Re: [tor-bugs] #28725 [Applications/Tor Browser]: Upgrade go-webrtc to dcbfc825aa33471253a5da1834d499257e05d557

[Tor Bug Tracker & Wiki]

#28725: Upgrade go-webrtc to dcbfc825aa33471253a5da1834d499257e05d557
-+-
 Reporter:  dcf  |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake tbb-rbm,   |  Actual Points:
  TorBrowserTeam201812   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by dcf):

 * Attachment "bug28725_2.patch" added.


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

Re: [tor-bugs] #28551 [Core Tor/Tor]: Tor's Travis should print the python version after installation

[Tor Bug Tracker & Wiki]

#28551: Tor's Travis should print the python version after installation
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  tor-ci, travis, fast-fix  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by rl1987):

 * cc: rl1987 (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] #28353 [Metrics/Website]: Use Guard & Exit, Guard only, Exit only, and Middle only on all bandwidth by flag graphs

[Tor Bug Tracker & Wiki]

#28353: Use Guard & Exit, Guard only, Exit only, and Middle only on all 
bandwidth
by flag graphs
-+--
 Reporter:  teor |  Owner:  metrics-team
 Type:  defect   | Status:  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #28328   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by irl):

 * status:  needs_review => merge_ready


Comment:

 I have not looked in a lot of detail for syntax issues or other specifics,
 but this looks good in principle.

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