Re: [tor-bugs] #34200 [Core Tor/Tor]: Refactor tor's circuit path node selection checks

[Tor Bug Tracker & Wiki]

#34200: Refactor tor's circuit path node selection checks
---+---
 Reporter:  teor   |  Owner:  teor
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.4.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ipv6, prop311, technical-debt  |  Actual Points:  1
Parent ID:  #33221 | Points:  1
 Reviewer: |Sponsor:  Sponsor55-can
---+---
Changes (by teor):

 * cc: nickm (added)
 * status:  assigned => needs_review


Comment:

 See my PR, which is based on #33222:
 * incomplete: https://github.com/torproject/tor/pull/1888

 This PR still needs unit tests and changes files for the extra refactor on
 top of #33222.

 The stem tests will fail due to:
 * https://github.com/torproject/stem/issues/63
 Reverting to the most recent stem release, or stem commit 13e401d, should
 resolve this issue.

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

Re: [tor-bugs] #33222 [Core Tor/Tor]: Prop 311: 4.2. Implement IPv6 ORPort Reachability Self-Tests

[Tor Bug Tracker & Wiki]

#33222: Prop 311: 4.2. Implement IPv6 ORPort Reachability Self-Tests
---+
 Reporter:  teor   |  Owner:  teor
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ipv6, prop311  |  Actual Points:  3
Parent ID:  #33221 | Points:  6
 Reviewer:  nickm  |Sponsor:  Sponsor55-must
---+

Comment (by teor):

 I just pushed a final refactor that cleans up a bunch of duplicate code.
 But I think it's best that we deal with the latest refactor commits in
 another ticket. (They shouldn't hold up merging this feature.) So I opened
 #34200 for the refactor, and split the branch.

 The (shorter) PR still needs unit tests and changes files.

 The stem tests will fail due to:
 * https://github.com/torproject/stem/issues/63
 Reverting to the most recent stem release, or stem commit 13e401d, should
 resolve this issue.

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

[tor-bugs] #34200 [Core Tor/Tor]: Refactor tor's circuit path node selection checks

[Tor Bug Tracker & Wiki]

#34200: Refactor tor's circuit path node selection checks
---+---
 Reporter:  teor   |  Owner:  teor
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal |   Keywords:  ipv6, prop311, technical-debt
Actual Points:  1  |  Parent ID:  #33221
   Points:  1  |   Reviewer:
  Sponsor:  Sponsor55-can  |
---+---
 In #33222, we added an extra "can extend over IPv6" check to tor's circuit
 path node selection code.

 To make sure it's applied consistently, I did a refactor of that code, so
 all those checks are in one function.

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

Re: [tor-bugs] #34192 [Applications/Tor Browser]: It Just Does Not Work

[Tor Bug Tracker & Wiki]

#34192: It Just Does Not Work
--+--
 Reporter:  WR Smith  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by teor):

 * owner:  (none) => tbb-team
 * version:  Tor: unspecified =>
 * component:  - Select a component => Applications/Tor Browser


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

Re: [tor-bugs] #34171 [Core Tor/Tor]: possible single circuit maximum transfer rate regression in 0.3.4

[Tor Bug Tracker & Wiki]

#34171: possible single circuit maximum transfer rate regression in 0.3.4
--+---
 Reporter:  starlight |  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.10
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by teor):

 One way to make progress here is to create a command-line script that
 reproduces the issue.

 Ideally the script should only use localhost, so that the person who runs
 the script doesn't need a fast internet connection.

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

Re: [tor-bugs] #34175 [Internal Services/Service - trac]: spam attack on trac

[Tor Bug Tracker & Wiki]

#34175: spam attack on trac
--+--
 Reporter:  anarcat   |  Owner:  qbi
 Type:  defect| Status:  assigned
 Priority:  Immediate |  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunk1):

 I've asked to create a people.md page and I'll just do it anyway. If some
 poor soul deface it that's it.

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

Re: [tor-bugs] #34175 [Internal Services/Service - trac]: spam attack on trac

[Tor Bug Tracker & Wiki]

#34175: spam attack on trac
--+--
 Reporter:  anarcat   |  Owner:  qbi
 Type:  defect| Status:  assigned
 Priority:  Immediate |  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunk1):

 > wiki looks now like nothing happend.

 My contrib was defaced again. This is ''second'' time. I'm not going to
 waste my time on 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

[tor-bugs] #34199 [Core Tor/Torsocks]: torsocks irssi weird bug

[Tor Bug Tracker & Wiki]

#34199: torsocks irssi weird bug
---+---
 Reporter:  crab   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  High   |  Component:  Core Tor/Torsocks
  Version:  Tor: 0.4.2.7   |   Severity:  Major
 Keywords:  tor irssi bug debug weird  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
 Depending on the arguments to torsocks the output varies even though it
 shouldn't

 case-1: torsocks irssi
 `/connect oftc` gives following error
 Irssi: Unable to connect server irc.oftc.net port 6697 [Interrupted system
 call]

 case 2: torsocks -d irssi
 `/connect oftc` works as expected

 I don't think there should be difference in output just because logging is
 enabled. This just might be the "torsocks uncertainty principle". I think
 we are onto something. Below I've attached the log dumped on the terminal.

 1589343629 DEBUG torsocks[22051]: Logging subsytem initialized. Level 5,
 file (null), time 1 (in init_logging() at torsocks.c:303)
 1589343629 DEBUG torsocks[22051]: Config file not provided by
 TORSOCKS_CONF_FILE. Using default /etc/torsocks.conf (in
 config_file_read() at config-file.c:543)
 1589343629 DEBUG torsocks[22051]: Config file setting tor address to
 127.0.0.1 (in conf_file_set_tor_address() at config-file.c:298)
 1589343629 DEBUG torsocks[22051]: Config file setting tor port to 9050 (in
 conf_file_set_tor_port() at config-file.c:254)
 1589343629 DEBUG torsocks[22051]: [config] Onion address range set to
 127.42.42.0/24 (in set_onion_info() at config-file.c:108)
 1589343629 DEBUG torsocks[22051]: Config file /etc/torsocks.conf opened
 and parsed. (in config_file_read() at config-file.c:572)
 1589343629 DEBUG torsocks[22051]: [fclose] Close caught for fd 3 (in
 tsocks_fclose() at fclose.c:45)
 1589343629 DEBUG torsocks[22051]: [onion] Pool init with subnet
 127.42.42.0 and mask 24 (in onion_pool_init() at onion.c:104)
 1589343629 DEBUG torsocks[22051]: [onion] Pool initialized with base 0,
 max_pos 255 and size 8 (in onion_pool_init() at onion.c:132)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 3 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 3 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 3 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in
 tsocks_close() at close.c:33)
 1589343629 DEBUG torsocks[22051]: [close] Close caught for fd 5 (in
 tsocks_close() at close.c:33)

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

Re: [tor-bugs] #24351 [Applications/Tor Browser]: Block Global Active Adversary Cloudflare

[Tor Bug Tracker & Wiki]

#24351: Block Global Active Adversary Cloudflare
-+-
 Reporter:  nullius  |  Owner:
 |  cypherpunks
 Type:  enhancement  | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  security, privacy, anonymity, mitm,  |  Actual Points:
  cloudflare, TorBrowserTeamTriaged  |
Parent ID:  #18361   | Points:  1000
 Reviewer:   |Sponsor:
-+-

Comment (by #BuiltForThis):

 LOL

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

Re: [tor-bugs] #34135 [Internal Services]: Feature suggestion: SOCKS5 internal DNS resolver.

[Tor Bug Tracker & Wiki]

#34135: Feature suggestion: SOCKS5 internal DNS resolver.
---+
 Reporter:  pcr|  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Internal Services  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by ϲypherpunks):

 Did you try this #34004 dnsresolver patch?

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

Re: [tor-bugs] #34190 [Internal Services/Service - trac]: New shared account idea

[Tor Bug Tracker & Wiki]

#34190: New shared account idea
--+-
 Reporter:  cypherpunk1   |  Owner:  qbi
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #34175| Points:
 Reviewer:|Sponsor:
--+-

Comment (by ϲypherpunks):

 Before and after looks same.

 
 The abuse was up to daily editing comments. This will not cover by this
 sadly. Hardened effort for the spammer but won't prevent it. Well a first
 step to recovery functionality of anonymous bug report is important. Of
 course no 100% solution exits. If someone after it he will find his way.
 Cat and mouse game. But daily account rotate would be to much I think.
 Keep in mind timezones differences.
 Weekly sounds reasonable.
  Is it possible to drop permission of editing (at least comments) for
 anything not from same session instead account based?

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

Re: [tor-bugs] #34192 [- Select a component]: It Just Does Not Work

[Tor Bug Tracker & Wiki]

#34192: It Just Does Not Work
--+--
 Reporter:  WR Smith  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Very High |  Milestone:
Component:  - Select a component  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by ϲypherpunks):

 Can you connect to your logged guard at all?

 {{{
 openssl s_client 86.59.21.38:443
 }}}

 Looks like connection\ firewall or https antivirus

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

Re: [tor-bugs] #34175 [Internal Services/Service - trac]: spam attack on trac

[Tor Bug Tracker & Wiki]

#34175: spam attack on trac
--+--
 Reporter:  anarcat   |  Owner:  qbi
 Type:  defect| Status:  assigned
 Priority:  Immediate |  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by ϲypherpunks):

 Thanks ! wiki looks now like nothing happend.

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

Re: [tor-bugs] #34176 [Internal Services/Tor Sysadmin Team]: Tor Browser Nightly external server support

[Tor Bug Tracker & Wiki]

#34176: Tor Browser Nightly external server support
-+-
 Reporter:  sysrqb   |  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 anarcat):

 >  To be clear, the current plan is we (Tor Browser devs) get an external
 server and we maintain it ourselves, in the short-term. I'll take on this
 responsibility. At some time in the future (but not too far in the
 future), TPA receive additional budget for adding a machine large enough
 for building Tor Browser Nightly. We then migrate the nightly build setup
 onto the new server and cancel the old machine.

 Works for me! :)

 >  Currently, the build system runs the following programs as root (in
 addition to executing dynamically created build (shell) scripts at run-
 time):

 > {{{
 > sudo tar
 > ...
 > }}}

 ... game over! might as well just give you root at that point...

 >  I've never tried runc-in-docker, but maybe? ticket:23631#comment:2
 describes some problems with directly using Docker.

 Thanks for the pointer! I admit I haven't read the entire thread so I
 hadn't caught that. I'm surprised to hear Docker can't run inside a i386
 machine... but as for the container escapes, the point would be that the
 container would run as as a regular user so that you wouldn't need to do
 all that pesky `runc` and `netns` stuff yourself. ;)

 But of course, I have no idea what I'm talking about here... That build
 seems to do some hairy stuff that maybe I will be happier not knowing
 about until I need to. :)

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

Re: [tor-bugs] #34176 [Internal Services/Tor Sysadmin Team]: Tor Browser Nightly external server support

[Tor Bug Tracker & Wiki]

#34176: Tor Browser Nightly external server support
-+-
 Reporter:  sysrqb   |  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 sysrqb):

 Replying to [comment:4 anarcat]:
 > > What do you think?
 >
 > I need to talk with the team about this, we have the change of guard
 tomorrow, let me see if I can poke at this problem again then.

 To be clear, the current plan is we (Tor Browser devs) get an external
 server and we maintain it ourselves, in the short-term. I'll take on this
 responsibility. At some time in the future (but not too far in the
 future), TPA receive additional budget for adding a machine large enough
 for building Tor Browser Nightly. We then migrate the nightly build setup
 onto the new server and cancel the old machine.

 >
 > What, exactly, do you need to run as root? Could we encapsulate only a
 subset of the build to run as root?

 Not easily in the current architecture of the build system. The system
 alternates between configuring a clean build environment (and installing
 dependencies) and then building the component.

 Currently, the build system runs the following programs as root (in
 addition to executing dynamically created build (shell) scripts at run-
 time):
 {{{
 sudo tar
 sudo ip netns add
 sudo ip netns exec
 sudo runc run
 sudo ip netns delete
 sudo mkdir
 sudo cp
 sudo chown
 sudo rm
 sudo runc --version
 sudo id
 sudo useradd
 ...
 }}}

 >
 > How about if we give you the ability to run Docker containers?

 I've never tried runc-in-docker, but maybe? ticket:23631#comment:2
 describes some problems with directly using Docker.

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

Re: [tor-bugs] #34175 [Internal Services/Service - trac]: spam attack on trac

[Tor Bug Tracker & Wiki]

#34175: spam attack on trac
--+--
 Reporter:  anarcat   |  Owner:  qbi
 Type:  defect| Status:  assigned
 Priority:  Immediate |  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by qbi):

 As far as I can tell all vandalism is now resetted.

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

Re: [tor-bugs] #33907 [Internal Services/Tor Sysadmin Team]: new gnt-fsn node (fsn-node-06)

[Tor Bug Tracker & Wiki]

#33907: new gnt-fsn node (fsn-node-06)
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tpa-roadmap-may  |  Actual Points:
Parent ID:  #32802   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * parent:   => #32802


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

Re: [tor-bugs] #33974 [Metrics/Onionperf]: Update OnionPerf to TGen 1.0.0

[Tor Bug Tracker & Wiki]

#33974: Update OnionPerf to TGen 1.0.0
---+
 Reporter:  karsten|  Owner:  metrics-team
 Type:  enhancement| Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor59-must
---+

Comment (by jnewsome):

 IIUC, the proposed work remaining here is roughly:

 * Update log-parsing for tgen 1.0 (ideally by using TGen's analysis.py)
 * Validate measurements in this patch.

 It'd be nice to have some automated end to end test for onionperf in
 general, and for this change in particular. I *think* the right way to do
 that would be to make an option in onionperf to set up and run its
 experiment under Shadow, rather than running the onionperf python script
 itself under Shadow. That *might* be possible with today's Shadow.
 Probably outside the scope of this ticket but I'll keep this in mind while
 I'm digging into onionperf, and perhaps open another ticket for it.

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

Re: [tor-bugs] #33907 [Internal Services/Tor Sysadmin Team]: new gnt-fsn node (fsn-node-06)

[Tor Bug Tracker & Wiki]

#33907: new gnt-fsn node (fsn-node-06)
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tpa-roadmap-may  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

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


Comment:

 ran the ganeti bootstrap procedure:

 {{{
 root@fsn-node-01:~# gnt-node list fsn-node-06
 Node   DTotal  DFree MTotal MNode MFree Pinst Sinst
 fsn-node-06.torproject.org 893.6G 800.9G  62.8G  215M 62.0G 0 0
 }}}

 node 6 now 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] #34024 [Metrics/Onionperf]: Reduce timeout and stallout values

[Tor Bug Tracker & Wiki]

#34024: Reduce timeout and stallout values
---+
 Reporter:  karsten|  Owner:  metrics-team
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:  Sponsor59-must
---+
Changes (by jnewsome):

 * cc: jnewsome (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] #33974 [Metrics/Onionperf]: Update OnionPerf to TGen 1.0.0

[Tor Bug Tracker & Wiki]

#33974: Update OnionPerf to TGen 1.0.0
---+
 Reporter:  karsten|  Owner:  metrics-team
 Type:  enhancement| Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor59-must
---+
Changes (by jnewsome):

 * cc: jnewsome (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] #34198 [Circumvention/Snowflake]: Include full broker messaging spec in /doc

[Tor Bug Tracker & Wiki]

#34198: Include full broker messaging spec in /doc
-+--
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  HashikD  |Sponsor:
-+--
Changes (by cohosh):

 * status:  assigned => needs_review
 * reviewer:   => HashikD


Comment:

 https://github.com/cohosh/snowflake/pull/30

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #34198 [Circumvention/Snowflake]: Include full broker messaging spec in /doc

[Tor Bug Tracker & Wiki]

#34198: Include full broker messaging spec in /doc
-+--
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 This adds information about the broker API, with the messaging protocol
 and the endpoints used by clients and proxies.

 This is a prerequisite for our work to implement a Snowflake proxy on
 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] #34173 [Internal Services/Service - trac]: prevent cypherpunks from editing old comments

[Tor Bug Tracker & Wiki]

#34173: prevent cypherpunks from editing old comments
--+---
 Reporter:  cypherpunks   |  Owner:  qbi
 Type:  defect| Status:  closed
 Priority:  Very High |  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Critical  | Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by qbi):

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


Comment:

 The ticket #34175 lists several of those tickets. We try to fix all
 tickets and reset the comments.

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

Re: [tor-bugs] #34159 [Internal Services/Service - trac]: user ϲypharpunks is removing wiki pages

[Tor Bug Tracker & Wiki]

#34159: user ϲypharpunks is removing wiki pages
--+
 Reporter:  ϲypherpunks   |  Owner:  qbi
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by qbi):

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


Comment:

 Several cypherpunks accounts are now disabled. We try to reset the pages
 to its original state.

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

Re: [tor-bugs] #34031 [Metrics/Onionperf]: Figure out warning about unknown error type when exporting .tpf file

[Tor Bug Tracker & Wiki]

#34031: Figure out warning about unknown error type when exporting .tpf file
---+
 Reporter:  karsten|  Owner:  acute
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.6
Parent ID: | Points:  2.0
 Reviewer:  karsten|Sponsor:  Sponsor59-must
---+
Changes (by karsten):

 * status:  needs_review => closed
 * points:  2 => 2.0
 * resolution:   => fixed
 * actualpoints:  0.2 => 0.6


Comment:

 Alright, I just made that [https://gitweb.torproject.org/metrics-
 lib.git/commit/?id=afc57a61209f806581c3c6ca472077fbcba835ec small change
 to metrics-lib]. I also left a comment on #34141 saying that we'll have to
 go back to this ticket ''if'' we decide not to do that ticket. I guess
 that concludes this ticket. Thanks again! Adding my 0.4 points to yours
 and closing.

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

Re: [tor-bugs] #34196 [Applications/Tor Browser]: Update site info URL with the onion name

[Tor Bug Tracker & Wiki]

#34196: Update site info URL with the onion name
--+--
 Reporter:  antonela  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:  sysrqb, antonela  |Sponsor:
--+--
Changes (by antonela):

 * Attachment "0.png" added.

 TB9.5 stable - onion names

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

Re: [tor-bugs] #34196 [Applications/Tor Browser]: Update site info URL with the onion name

[Tor Bug Tracker & Wiki]

#34196: Update site info URL with the onion name
--+--
 Reporter:  antonela  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:  sysrqb, antonela  |Sponsor:
--+--
Changes (by antonela):

 * Attachment "0.2.png" added.


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

Re: [tor-bugs] #34141 [Metrics/Onionperf]: Stop generating .tpf files

[Tor Bug Tracker & Wiki]

#34141: Stop generating .tpf files
---+
 Reporter:  karsten|  Owner:  metrics-team
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:  1.0
 Reviewer: |Sponsor:  Sponsor59-must
---+

Comment (by karsten):

 2 days ago I started a new [https://lists.torproject.org/pipermail/tor-
 dev/2020-May/014273.html thread on tor-dev@], asking if anybody is using
 OnionPerf's measurement results in the .tpf format. If we don't hear
 anything by our weekly meeting on Thursday, I'd say we can move on to step
 2.

 Just in case we decide in the end to keep the .tpf format and not do step
 3, we'll have to take care of #34031. I hope we don't have to.

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

Re: [tor-bugs] #33292 [Applications/Tor Browser]: Difficult to Change Site Circuit After Redirect (was: Difficult Change Site Circuit After Redirect)

[Tor Bug Tracker & Wiki]

#33292: Difficult to Change Site Circuit After Redirect
-+-
 Reporter:  sysrqb   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  TorBrowserTeamTriaged, tbb-  |  Actual Points:
  usability, ux-team |
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] #34197 [Metrics/Exit Scanner]: Teer shillong numbers hidden

[Tor Bug Tracker & Wiki]

#34197: Teer shillong numbers hidden
+--
 Reporter:  Red@…   |  Owner:  metrics-team
 Type:  project | Status:  new
 Priority:  Medium  |  Component:  Metrics/Exit Scanner
  Version:  Tor: 0.4.3.2-alpha  |   Severity:  Normal
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:  SponsorM
+--


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

Re: [tor-bugs] #34196 [Applications/Tor Browser]: Update site info URL with the onion name

[Tor Bug Tracker & Wiki]

#34196: Update site info URL with the onion name
--+--
 Reporter:  antonela  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:  sysrqb, antonela  |Sponsor:
--+--
Changes (by antonela):

 * Attachment "0.png" added.

 TB9.5 stable - onion names

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

Re: [tor-bugs] #34196 [Applications/Tor Browser]: Update site info URL with the onion name

[Tor Bug Tracker & Wiki]

#34196: Update site info URL with the onion name
--+--
 Reporter:  antonela  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:  sysrqb, antonela  |Sponsor:
--+--
Changes (by antonela):

 * Attachment "0.2.png" added.


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

Re: [tor-bugs] #34171 [Core Tor/Tor]: possible single circuit maximum transfer rate regression in 0.3.4

[Tor Bug Tracker & Wiki]

#34171: possible single circuit maximum transfer rate regression in 0.3.4
--+---
 Reporter:  starlight |  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.4.10
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by dgoulet):

 > In #29427 KIST related transfer rate impairment shown in the graph is
 huge. I am doubtful regarding the cost vs benefit of the feature.

 Just to be clear, that issue is related to *client* only. Relays do not
 suffer from the interval issue because they have thousands of open
 connections compared to a client with a couple at best.

 So relays should really not be capped _in theory_ compared to Vanilla
 scheduler... If there are evidence that KIST is performing poorly compared
 from Vanilla on the *relay* side, then that is a different story.

 But without data, we can't really go on here?

 As for the bandwidth scanner issue, that is very different problem and a
 big one that we are trying to address.

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

Re: [tor-bugs] #34196 [Applications/Tor Browser]: Update site info URL with the onion name

[Tor Bug Tracker & Wiki]

#34196: Update site info URL with the onion name
--+--
 Reporter:  antonela  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:  sysrqb, antonela  |Sponsor:
--+--

Comment (by antonela):

 FPF's iteration
 [[Image(https://trac.torproject.org/projects/tor/raw-
 attachment/ticket/34196/friendlyurl.png, 700)]]

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

Re: [tor-bugs] #34196 [Applications/Tor Browser]: Update site info URL with the onion name

[Tor Bug Tracker & Wiki]

#34196: Update site info URL with the onion name
--+--
 Reporter:  antonela  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:  sysrqb, antonela  |Sponsor:
--+--

Comment (by antonela):

 Stable

 [[Image(https://trac.torproject.org/projects/tor/raw-
 attachment/ticket/34196/0.png, 700)]]

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

Re: [tor-bugs] #34196 [Applications/Tor Browser]: Update site info URL with the onion name

[Tor Bug Tracker & Wiki]

#34196: Update site info URL with the onion name
--+--
 Reporter:  antonela  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:  sysrqb, antonela  |Sponsor:
--+--
Changes (by antonela):

 * Attachment "friendlyurl.png" added.


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

[tor-bugs] #34196 [Applications/Tor Browser]: Update site info URL with the onion name

[Tor Bug Tracker & Wiki]

#34196: Update site info URL with the onion name
--+--
 Reporter:  antonela  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  ux-team
Actual Points:|  Parent ID:
   Points:|   Reviewer:  sysrqb, antonela
  Sponsor:|
--+--
 After discussing onion names with the Freedom of the Press UX folks, they
 suggested showing a more explicit relationship between the origin .onion
 address and HTTPSeverywhere alias in our user interface.

 We agreed on this idea and we planned to:

 - update the site info at the identity doorhanger by showing the onion
 name
 - link users to a more info section in
 `support.torproject.org/onionservices/onionnames`

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

Re: [tor-bugs] #34196 [Applications/Tor Browser]: Update site info URL with the onion name

[Tor Bug Tracker & Wiki]

#34196: Update site info URL with the onion name
--+--
 Reporter:  antonela  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:  sysrqb, antonela  |Sponsor:
--+--
Changes (by antonela):

 * Attachment "0.png" added.

 TB9.5 stable - onion names

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

Re: [tor-bugs] #32335 [Core Tor/Tor]: Set up a .github repository on GitHub

[Tor Bug Tracker & Wiki]

#32335: Set up a .github repository on GitHub
--+--
 Reporter:  teor  |  Owner:  (none)
 Type:  task  | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-github, 043-deferred  |  Actual Points:
Parent ID:| Points:  1
 Reviewer:  nickm |Sponsor:
--+--

Comment (by nickm):

 Good catch! The license file isn't part of this PR, though; it looks like
 github provided it with the initial repository.

 Given the history of this ticket, I think our best bet is for me to raise
 this for more general discussion again and propose a way forward.  Namely,
 I think we should merge the PR, and then fix up whatever remaining issues
 we find.

 I'll bring this up at the all-hands on wednesday and propose that we go
 ahead that way.

 Some issues I would fix post-merge are:
* Stop recommending trac as a support forum.
* Explicitly list which repositories are "owned"/maintained by which
 teams, with a table or list covering every repo we have.

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

Re: [tor-bugs] #33907 [Internal Services/Tor Sysadmin Team]: new gnt-fsn node (fsn-node-06)

[Tor Bug Tracker & Wiki]

#33907: new gnt-fsn node (fsn-node-06)
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tpa-roadmap-may  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 mandos fixed, i forgot the roles::fde / puppet procedure part.

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

Re: [tor-bugs] #34031 [Metrics/Onionperf]: Figure out warning about unknown error type when exporting .tpf file

[Tor Bug Tracker & Wiki]

#34031: Figure out warning about unknown error type when exporting .tpf file
---+
 Reporter:  karsten|  Owner:  acute
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.2
Parent ID: | Points:  2
 Reviewer:  karsten|Sponsor:  Sponsor59-must
---+

Comment (by acute):

 Replying to [comment:14 karsten]:

 >  - Maybe we should avoid keeping a map/dictionary with known failure
 types in metrics-lib and simply put together the error code in the format
 we want, which would be `TOR/END/INTERNAL` in this case. I'll add a new
 ticket for that. Should be an easy change.
 This is a solid approach - especially since we don't know if the latest
 Tgen reuses the same error codes. I'd also be interested in knowing how
 many total combinations are possible.
 >
 > Regarding the additional cases, I strongly believe that these are the
 result of OnionPerf's approach to match TGen transfers to streams and
 circuits, which is somewhat broken. The approach there is to match them by
 source port, but that fails as soon as the same source port is being used
 more than once per day. In metrics-lib I'm doing a somewhat more complex
 approach that also looks at start/end times of transfers and streams. That
 avoids these cases, so I'd say that there's nothing else to do here,
 assuming that we do #34141.
 I suspected this was the case, and it makes sense. In the past I tried
 matching transfer times as well as source port directly in Onionperf
 analysis, but encountered issues with log parsing and opened #30362.

 > If you agree, I'll leave a comment on #34141 that we need to fix this
 ticket, if we don't do that one. And I'll open a new ticket to tweak
 metrics-lib's code for including yet unknown error codes in Torperf
 results. And then I'll close this ticket. Makes sense?
 Yes, makes sense! Thank you for the quick review!

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

Re: [tor-bugs] #34130 [Core Tor/Tor]: Tor won't start with seccomp sandbox when compiled with --enable-nss

[Tor Bug Tracker & Wiki]

#34130: Tor won't start with seccomp sandbox when compiled with --enable-nss
-+-
 Reporter:  Jigsaw52 |  Owner:  (none)
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  nss sandbox seccomp 035-backport |  Actual Points:
  041-backport-maybe 042-backport 043-backport   |
Parent ID:   | Points:
 Reviewer:  nickm|Sponsor:
-+-
Changes (by nickm):

 * status:  needs_review => merge_ready
 * milestone:  Tor: 0.4.4.x-final => Tor: 0.4.3.x-final


Comment:

 I've made a branch against 0.3.5 that cherry-picks this patch, as
 `bug34130_035`.  The PR for that is
 https://github.com/torproject/tor/pull/1887 .

 I've merged it to master, and am marking for backport.  Additional 0.4.1
 releases are indeed unlikely. :)

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

Re: [tor-bugs] #34133 [Core Tor/Tor]: Tor documentation missing sandbox and %include limitations

[Tor Bug Tracker & Wiki]

#34133: Tor documentation missing sandbox and %include limitations
---+---
 Reporter:  Jigsaw52   |  Owner:  (none)
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.4.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:  implemented
 Keywords:  seccomp sandbox documentation  |  Actual Points:
Parent ID: | Points:
 Reviewer:  nickm  |Sponsor:
---+---
Changes (by nickm):

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


Comment:

 Thank you; this looks good to me now.  Merged to master!

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

Re: [tor-bugs] #33907 [Internal Services/Tor Sysadmin Team]: new gnt-fsn node (fsn-node-06)

[Tor Bug Tracker & Wiki]

#33907: new gnt-fsn node (fsn-node-06)
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tpa-roadmap-may  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 added to LDAP, password manager, spreadsheet, nagios, puppet bootstrapped,
 mandos setup (although not working yet?), rebooted with dropbear password
 input.

 next step: ganeti bootstrap.

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

Re: [tor-bugs] #34175 [Internal Services/Service - trac]: spam attack on trac

[Tor Bug Tracker & Wiki]

#34175: spam attack on trac
--+--
 Reporter:  anarcat   |  Owner:  qbi
 Type:  defect| Status:  assigned
 Priority:  Immediate |  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by qbi):

 Replying to [comment:9 ϲypherpunks]:
 > wiki:
 > [wiki:org/doc/ListOfServicesBlockingTor]
 > [wiki:org/projects/WeSupportTor]
 > [wiki:doc/CloudflareSites]
 > [wiki:org/projects/DontBlockMe]

 I resetted all of the wiki pages. Resetting the tickets requires a bit
 more 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] #34194 [Applications/Tor Browser]: dead link in tor-browser

[Tor Bug Tracker & Wiki]

#34194: dead link in tor-browser
--+
 Reporter:  crab  |  Owner:  tbb-team
 Type:  defect| Status:
  |  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor:
  |  0.4.2.7
 Severity:  Normal| Resolution:
 Keywords:  dead link onion site tor browser  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by crab):

 I have made no manual changes within preferences. Do you suppose this
 error,
 is due to an unset locale? I haven't really dealt with it, but can you
 suggest
 the shell variable I should set? "Requested locales" is followed by a
 blank field.

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

Re: [tor-bugs] #34187 [Applications/Tor Browser]: Update zlib build script to pick up new android toolchain

[Tor Bug Tracker & Wiki]

#34187: Update zlib build script to pick up new android toolchain
-+-
 Reporter:  gk   |  Owner:  gk
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:
  TorBrowserTeam202005R, GeorgKoppen202005   |
Parent ID:  #33184   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-mobile, tbb-rbm, TorBrowserTeam202005, GeorgKoppen202005
 => tbb-mobile, tbb-rbm, TorBrowserTeam202005R, GeorgKoppen202005
 * status:  assigned => needs_review


Comment:

 `bug_34187` (https://gitweb.torproject.org/user/gk/tor-browser-
 build.git/commit/?h=bug_34187=9f6ad40c4bd67459417d824d9e3a573d5cb6ec03)
 has a patch for 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] #34195 [Circumvention/Wolpertinger]: Make wolpertinger create usage metrics

[Tor Bug Tracker & Wiki]

#34195: Make wolpertinger create usage metrics
+--
 Reporter:  phw |  Owner:  phw
 Type:  enhancement | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Circumvention/Wolpertinger  |Version:
 Severity:  Normal  |   Keywords:
Actual Points:  |  Parent ID:  #32740
   Points:  0.5 |   Reviewer:
  Sponsor:  |
+--
 Wolpertinger should export usage metrics to help us understand 1) how
 censorship measurement platforms use its API, and 2) its inner workings.
 Metrics that come to mind:

 * Number of bridge requests over time per censorship measurement platform.
 * The distribution of origin countries per censorship measurement
 platform.

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

Re: [tor-bugs] #34031 [Metrics/Onionperf]: Figure out warning about unknown error type when exporting .tpf file

[Tor Bug Tracker & Wiki]

#34031: Figure out warning about unknown error type when exporting .tpf file
---+
 Reporter:  karsten|  Owner:  acute
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.2
Parent ID: | Points:  2
 Reviewer:  karsten|Sponsor:  Sponsor59-must
---+

Comment (by karsten):

 Thanks for the very detailed analysis!

 Regarding the three unknown failure types, I think we should rather stop
 generating .tpf files (#34141) than add these three cases to the existing
 dictionary. However, that doesn't solve the problem entirely:
  - We have similar code in metrics-lib that converts OnionPerf's analysis
 files to Torperf results. Right now, that code contains a similar
 map/dictionary with known failure types, and if it doesn't find a key, it
 simply includes the combined error code, as in: `PROXY_END_INTERNAL`. I
 was somehow under the impression that OnionPerf would do the same, but I
 was wrong.
  - Maybe we should avoid keeping a map/dictionary with known failure types
 in metrics-lib and simply put together the error code in the format we
 want, which would be `TOR/END/INTERNAL` in this case. I'll add a new
 ticket for that. Should be an easy change.

 Regarding the additional cases, I strongly believe that these are the
 result of OnionPerf's approach to match TGen transfers to streams and
 circuits, which is somewhat broken. The approach there is to match them by
 source port, but that fails as soon as the same source port is being used
 more than once per day. In metrics-lib I'm doing a somewhat more complex
 approach that also looks at start/end times of transfers and streams. That
 avoids these cases, so I'd say that there's nothing else to do here,
 assuming that we do #34141.

 If you agree, I'll leave a comment on #34141 that we need to fix this
 ticket, if we don't do that one. And I'll open a new ticket to tweak
 metrics-lib's code for including yet unknown error codes in Torperf
 results. And then I'll close this ticket. Makes sense?

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

Re: [tor-bugs] #34194 [Applications/Tor Browser]: dead link in tor-browser

[Tor Bug Tracker & Wiki]

#34194: dead link in tor-browser
--+
 Reporter:  crab  |  Owner:  tbb-team
 Type:  defect| Status:
  |  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor:
  |  0.4.2.7
 Severity:  Normal| Resolution:
 Keywords:  dead link onion site tor browser  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by acat):

 * status:  new => needs_information


Comment:

 It looks like the browser is not getting the proper language: `und` should
 have been the locale (e.g. en-US). If I may ask, are you using a localized
 Tor Browser? Or did you manually change the language via the preferences
 (`about:preferences`) page? If so, it would also be useful to know the
 value of "Requested locales" in `about:support` page.

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

Re: [tor-bugs] #33907 [Internal Services/Tor Sysadmin Team]: new gnt-fsn node (fsn-node-06)

[Tor Bug Tracker & Wiki]

#33907: new gnt-fsn node (fsn-node-06)
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tpa-roadmap-may  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 basic bootstrap completed:

 SSH keys:

 {{{
 ecdsa-sha2-nistp256
 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBKQ4ly0V924z2WT1Y6VGyvh/mTMkGhONGsZmuosvjg8ex6S9lTAP4ay3V1Dh+XGP+LoQeOw40JvedHrCNmW91a0=
 root@fsn-node-06
 ssh-ed25519
 C3NzaC1lZDI1NTE5IAYa9smDmzTXXfYoAyUsDLR7iCTZVNgXJn8PkH9GNq7M root
 @fsn-node-06
 ssh-rsa
 
B3NzaC1yc2EDAQABAAABAQC50C7XrouYBgUa6MV+LQI+Os+J+EKSYd5w/PKq+f6nAJUHNA9TeF1W7pykCNA7FAvYTDnnunDDPm/boaDKmLxQZkQyuiYoLvS4GdWpouf5u/QFdMpaooTJis6o0pYSZZ8uJZ/mf6mx+pDQ4kfQh1/qI6WS83vmM8+++tw0hBupLrvHg5Y1s7BXkE6iRZTzQbDnascVn5TCebDJCer4vVSQQjPRJXh5sRvbWxcrZ12PZtg8EojCrZtjUiWSP7guv33KlQ5voNuQADop0R0baBi4R7g/uW1FbQldz5Nsv4Q+0Oeb4Fa2GNdK112F6PQxmzqSybFPcFNBQdzmE8EkaSwv
 root@fsn-node-06
 }}}

 initramfs keys:

 {{{
 ssh-dss
 
B3NzaC1kc3MAAACBAJAlwlR0LAi10ud9fDplFZFJ4A1EW51WGKC7x5KVwYnvBMWop7CMZMTB94768EE6sO3cdi6VL51dxl5F3sjohOhpu8w4Y+xuGUjGu9bzdftkZNNcm1l6A72O41sP58wvpq5LkvBlEhBBp0y+6ttwkZ/21RfepuQb/SMbiCKgoXT/FQCCey/oeh4D5xE5q1viR1lZXHcTuQAAAIApRxHd3nh92EOe2/MADcLc2yoED0Wfoe+4R+MvMdx8pm6Cx3Dj+Z1QH14xxO9WriV1TjXrypVemEzkffYlRJEBYMEHVejSVFv/wroljvXkfNMcm2hk+YuC6U20Oaf45tUmYweDm9iVvBIW0Ie7ptgDrOzP7retabMpVn/GuhUGCQAAAIArTFLi6rXG71Cc9RZM05W0vADPk9i63cs0nvjD0D+srbis1/TGZxVCKckHB4bxUkuRPESslhsbsf0DnDVC3Xvi6s1c5hJua9jTwDIx8uqzfum5ActD0PR2P2HzvPdDLpJGAkRIcBHQW2GNayOj7NnO8BUdmxJ3gr4F89oW0LWo/Q==
 root@fsn-node-06
 ecdsa-sha2-nistp256
 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBNFBe7NnAIQrKL8zXRz0emiwyWoF/n/FTabXESKTjSFM6x88b9td9QFW2Y3R382ICXdKJUmbLQi/Bj8vlxcBKmA=
 root@fsn-node-06
 ssh-rsa
 
B3NzaC1yc2EDAQABAAABAQDjjZub9ksagAy0x3zPtXdlrbEINROJ2VJdR7QMpQbRUIYEbLk52QOK4LP9bT34gvqWfkY/khpUc49dt2elMr8Tzjy13R4kc+73l8o1vC2/fBIt1wYsrc5mm2Me2RjMEPUEEeS7S1xYTCwF9wC2jgA3zfC0eudbULp7L59Ljxw0TUIzBBffpCKoBsyr1YCYQKPXBAccmjMucFLdZPd4xYuhh5u3Y9zfHg7aE0jfl0t7Saczb00g4YDs9tWPnOFYm1vZpCW07bavfQTFUX/nLf6vesGwNGmGXrk2rRG4aOQ/ikTrEub6ii+uzqQsXK/OlvJNOQYoMp1gxt9RZ+d4bwDF
 root@fsn-node-06
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #34194 [Applications/Tor Browser]: dead link in tor-browser

[Tor Bug Tracker & Wiki]

#34194: dead link in tor-browser
-+-
 Reporter:  crab |  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Component:  Applications/Tor
 |  Browser
  Version:  Tor: 0.4.2.7 |   Severity:  Normal
 Keywords:  dead link onion site |  Actual Points:
  tor browser|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
 Click on tor icon beside the search bar to show the site information.
 Below the "New Circuit for this Site" button click the "Learn more" link.
 link leads to https://support.torproject.org/und/tbb/tbb-2/
 Greets with following error.

 Not Found

 The requested URL was not found on this server.

 Swear to god I wanted to learn more this time.

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

Re: [tor-bugs] #34028 [Applications/GetTor]: Monitor GetTor's email autoresponder

[Tor Bug Tracker & Wiki]

#34028: Monitor GetTor's email autoresponder
-+
 Reporter:  phw  |  Owner:  (none)
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/GetTor  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+
Changes (by hiro):

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


Comment:

 done.

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

Re: [tor-bugs] #33941 [Internal Services/Tor Sysadmin Team]: Nagios checks for op-??.onionperf.torproject.net

[Tor Bug Tracker & Wiki]

#33941: Nagios checks for op-??.onionperf.torproject.net
-+-
 Reporter:  karsten  |  Owner:  hiro
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tpa-roadmap-may  |  Actual Points:
Parent ID:  #33318   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor59-must
-+-
Changes (by hiro):

 * status:  assigned => 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] #31159 [Internal Services/Tor Sysadmin Team]: Monitor anti-censorship www services with prometheus

[Tor Bug Tracker & Wiki]

#31159: Monitor anti-censorship www services with prometheus
-+-
 Reporter:  phw  |  Owner:  hiro
 Type:  task | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tpa-roadmap-may  |  Actual Points:
Parent ID:  #30152   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by hiro):

 I think this does it:
 https://grafana2.torproject.org/d/TVZiAIRGz/bridges?orgId=1

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

Re: [tor-bugs] #34089 [Internal Services/Services Admin Team]: Add Apache ProxyPass directive on polyanthum to expose wolpertinger

[Tor Bug Tracker & Wiki]

#34089: Add Apache ProxyPass directive on polyanthum to expose wolpertinger
-+-
 Reporter:  phw  |  Owner:  anarcat
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Services Admin |Version:
  Team   |
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:  #32740   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

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


Comment:

 done, with a manual config on the server (as the vhost is not in puppet).

 let me know how that goes.

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

Re: [tor-bugs] #34089 [Internal Services/Services Admin Team]: Add Apache ProxyPass directive on polyanthum to expose wolpertinger

[Tor Bug Tracker & Wiki]

#34089: Add Apache ProxyPass directive on polyanthum to expose wolpertinger
-+-
 Reporter:  phw  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Services Admin |Version:
  Team   |
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #32740   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * owner:  (none) => anarcat
 * status:  new => accepted


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

Re: [tor-bugs] #33907 [Internal Services/Tor Sysadmin Team]: new gnt-fsn node (fsn-node-06)

[Tor Bug Tracker & Wiki]

#33907: new gnt-fsn node (fsn-node-06)
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tpa-roadmap-may  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * Attachment "fsn-node-06-nvme0n1.log" 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] #33907 [Internal Services/Tor Sysadmin Team]: new gnt-fsn node (fsn-node-06)

[Tor Bug Tracker & Wiki]

#33907: new gnt-fsn node (fsn-node-06)
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tpa-roadmap-may  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * Attachment "fsn-node-06-nvme1n1.log" 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] #34176 [Internal Services/Tor Sysadmin Team]: Tor Browser Nightly external server support

[Tor Bug Tracker & Wiki]

#34176: Tor Browser Nightly external server support
-+-
 Reporter:  sysrqb   |  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 anarcat):

 > What do you think?

 I need to talk with the team about this, we have the change of guard
 tomorrow, let me see if I can poke at this problem again then.

 What, exactly, do you need to run as root? Could we encapsulate only a
 subset of the build to run as root?

 How about if we give you the ability to run Docker containers?

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

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

[Tor Bug Tracker & Wiki]

#33801: Upgrade Go Project to use new Android Toolchain
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  merge_ready
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:  .1
  TorBrowserTeam202005R  |
Parent ID:  #33184   | Points:
 Reviewer:  gk   |Sponsor:
 |  Sponsor58-must
-+-

Comment (by gk):

 `bug_33801_v2` (https://gitweb.torproject.org/user/gk/tor-browser-
 build.git/commit/?h=bug_33801_v2=d828411d441d1b9ebce642cbaf41d60e525bb617)
 has the same patch based on the slightly updated toolchain for #33557.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #34193 [Applications/Tor Browser]: Audit the U2F API

[Tor Bug Tracker & Wiki]

#34193: Audit the U2F API
--+--
 Reporter:  acat  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  ff78-esr
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:  Sponsor58 |
--+--
 Similar to #26614, we should audit the `U2F` API implementation that is
 enabled with the `security.webauth.webauthn` pref.

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

Re: [tor-bugs] #34193 [Applications/Tor Browser]: Audit the U2F API

[Tor Bug Tracker & Wiki]

#34193: Audit the U2F API
--+---
 Reporter:  acat  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff78-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor58
--+---
Description changed by acat:

Old description:

> Similar to #26614, we should audit the `U2F` API implementation that is
> enabled with the `security.webauth.webauthn` pref.

New description:

 Similar to #26614, we should audit the `U2F` API implementation that is
 enabled with the `security.webauth.u2f` pref.

--

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

Re: [tor-bugs] #33557 [Applications/Tor Browser]: Update Android Toolchain for Fenix

[Tor Bug Tracker & Wiki]

#33557: Update Android Toolchain for Fenix
-+-
 Reporter:  sisbell  |  Owner:  gk
 Type:  task | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:
  TorBrowserTeam202005R, GeorgKoppen202005   |
Parent ID:  #33184   | Points:
 Reviewer:  sysrqb   |Sponsor:
 |  Sponsor58-must
-+-

Comment (by gx):

 https://bugzilla.mozilla.org/show_bug.cgi?id=1525999

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

Re: [tor-bugs] #34031 [Metrics/Onionperf]: Figure out warning about unknown error type when exporting .tpf file

[Tor Bug Tracker & Wiki]

#34031: Figure out warning about unknown error type when exporting .tpf file
---+
 Reporter:  karsten|  Owner:  acute
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.2
Parent ID: | Points:  2
 Reviewer:  karsten|Sponsor:  Sponsor59-must
---+
Changes (by karsten):

 * reviewer:   => karsten


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

Re: [tor-bugs] #33962 [Applications/Tor Browser]: Uplift patch for 5741 (dns leak protection)

[Tor Bug Tracker & Wiki]

#33962: Uplift patch for 5741 (dns leak protection)
-+-
 Reporter:  acat |  Owner:  acat
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ReleaseTrainMigration|  Actual Points:
  TorBrowserTeam202005   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor58
-+-
Changes (by acat):

 * keywords:  ReleaseTrainMigration TorBrowserTeam202005R =>
 ReleaseTrainMigration TorBrowserTeam202005
 * status:  needs_review => new


Comment:

 Removing review_needed, as this second push might change the original
 patch that landed more than I expected.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #34192 [- Select a component]: It Just Does Not Work

[Tor Bug Tracker & Wiki]

#34192: It Just Does Not Work
--+--
 Reporter:  WR Smith  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Very High |  Component:  - Select a component
  Version:  Tor: unspecified  |   Severity:  Normal
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
 Tor worked like a breeze for me a few months ago.  Now I cannot even get
 it to start.

 Something is serious fucked up with this latest version of the browser,
 and there is **no good information out there** on what to do about it.
 Gibberish and nonsense.

 Please post a **plain-English** solution to this problem.

 No, I do not use a proxy, I am not in a country where Tor is censored, and
 there is absolutely nothing wrong with my system clock.


 OS:  **Windows 7**
 Tor Version:  **9.0.10**

 Log:

 5/12/20, 13:23:34.321 [NOTICE] DisableNetwork is set. Tor will not make or
 accept non-control network connections. Shutting down all existing
 connections.
 5/12/20, 13:23:34.321 [NOTICE] DisableNetwork is set. Tor will not make or
 accept non-control network connections. Shutting down all existing
 connections.
 5/12/20, 13:23:34.321 [NOTICE] DisableNetwork is set. Tor will not make or
 accept non-control network connections. Shutting down all existing
 connections.
 5/12/20, 13:23:34.322 [NOTICE] Opening Socks listener on 127.0.0.1:9150
 5/12/20, 13:23:34.322 [NOTICE] Opened Socks listener on 127.0.0.1:9150
 5/12/20, 13:23:34.322 [NOTICE] Renaming old configuration file to "E:\Tor
 Browser\Browser\TorBrowser\Data\Tor\torrc.orig.1"
 5/12/20, 13:23:34.322 [NOTICE] Bootstrapped 5% (conn): Connecting to a
 relay
 5/12/20, 13:24:58.291 [WARN] Problem bootstrapping. Stuck at 5% (conn):
 Connecting to a relay. (Connection timed out [WSAETIMEDOUT ]; TIMEOUT;
 count 10; recommendation warn; host
 847B1F850344D7876491A54892F904934E4EB85D at 86.59.21.38:443)
 5/12/20, 13:24:58.291 [WARN] 9 connections have failed:
 5/12/20, 13:24:58.291 [WARN] 9 connections died in state connect()ing with
 SSL state (No SSL object)
 5/12/20, 13:24:58.299 [WARN] Problem bootstrapping. Stuck at 5% (conn):
 Connecting to a relay. (Connection timed out [WSAETIMEDOUT ]; TIMEOUT;
 count 11; recommendation warn; host
 FFA72BD683BC2FCF988356E6BEC1E490F313FB07 at 193.11.164.243:9001)
 5/12/20, 13:24:58.299 [WARN] 10 connections have failed:
 5/12/20, 13:24:58.299 [WARN] 10 connections died in state connect()ing
 with SSL state (No SSL object)
 5/12/20, 13:24:58.299 [NOTICE] Closing no-longer-configured Socks listener
 on 127.0.0.1:9150
 5/12/20, 13:24:58.299 [NOTICE] DisableNetwork is set. Tor will not make or
 accept non-control network connections. Shutting down all existing
 connections.
 5/12/20, 13:24:59.290 [NOTICE] Delaying directory fetches: DisableNetwork
 is set.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #34191 [Metrics/Onionperf]: Combine multiple analysis files into single data set

[Tor Bug Tracker & Wiki]

#34191: Combine multiple analysis files into single data set
---+--
 Reporter:  karsten|  Owner:  metrics-team
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points:  0.5|   Reviewer:
  Sponsor:  Sponsor59-must |
---+--
 OnionPerf's visualize mode currently supports specifying multiple data
 sets to be graphed with different labels for each data set. However, for
 each data set it's only possible to specify exactly one analysis results
 file. If we ever want to graph a data set covering more than a single day
 and compare that to another data set, we cannot do that at the moment.

 Here's a possible user interface extension to allow specifying one or more
 analysis results files for each data set:

 {{{
 diff --git a/onionperf/onionperf b/onionperf/onionperf
 index cb1899c..957c6df 100755
 --- a/onionperf/onionperf
 +++ b/onionperf/onionperf
 @@ -326,8 +326,9 @@ files generated by this script will be written""",
  visualize_parser.set_defaults(func=visualize,
 formatter_class=my_formatter_class)

  visualize_parser.add_argument('-d', '--data',
 -help="""Append a PATH to a onionperf.analysis.json analysis
 results file, and a LABEL that we
 -should use for the graph legend for this dataset""",
 +help="""Append a file or directory PATH to an
 onionperf.analysis.json
 +analysis results file or directory of such files, and a
 LABEL
 +that we should use for the graph legend for this
 dataset""",
  metavar=("PATH", "LABEL"),
  nargs=2,
  required="True",
 }}}

 I didn't write any other code for this yet.

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

Re: [tor-bugs] #33222 [Core Tor/Tor]: Prop 311: 4.2. Implement IPv6 ORPort Reachability Self-Tests

[Tor Bug Tracker & Wiki]

#33222: Prop 311: 4.2. Implement IPv6 ORPort Reachability Self-Tests
---+
 Reporter:  teor   |  Owner:  teor
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ipv6, prop311  |  Actual Points:  3
Parent ID:  #33221 | Points:  6
 Reviewer:  nickm  |Sponsor:  Sponsor55-must
---+

Comment (by nickm):

 I've left comments un through 04b6b7b.

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

Re: [tor-bugs] #34031 [Metrics/Onionperf]: Figure out warning about unknown error type when exporting .tpf file

[Tor Bug Tracker & Wiki]

#34031: Figure out warning about unknown error type when exporting .tpf file
---+
 Reporter:  karsten|  Owner:  acute
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.2
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor59-must
---+
Changes (by acute):

 * status:  assigned => needs_review
 * actualpoints:   => 0.2


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

Re: [tor-bugs] #34187 [Applications/Tor Browser]: Update zlib build script to pick up new android toolchain

[Tor Bug Tracker & Wiki]

#34187: Update zlib build script to pick up new android toolchain
-+-
 Reporter:  gk   |  Owner:  gk
 Type:  defect   | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:
  TorBrowserTeam202005, GeorgKoppen202005|
Parent ID:  #33184   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * owner:  tbb-team => gk
 * cc: tbb-team (added)
 * status:  new => assigned
 * priority:  Medium => High


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

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

[Tor Bug Tracker & Wiki]

#33561: Upgrade openssl to use Android NDK 21
-+-
 Reporter:  sisbell  |  Owner:  gk
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:
  TorBrowserTeam202005R, GeorgKoppen202005   |
Parent ID:  #33184   | Points:
 Reviewer:  sysrqb   |Sponsor:
 |  Sponsor58-must
-+-

Comment (by gk):

 `bug_33561_v2` (https://gitweb.torproject.org/user/gk/tor-browser-
 build.git/commit/?h=bug_33561_v2=5ba0336685601621ff999accec5767f7989aa9ac)
 has no patch changes but is based on the slightly changed toolchain (see:
 #33557).

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

Re: [tor-bugs] #34142 [Metrics/Onionperf]: Integrate reprocessing mode into analysis mode

[Tor Bug Tracker & Wiki]

#34142: Integrate reprocessing mode into analysis mode
---+
 Reporter:  karsten|  Owner:  karsten
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:  implemented
 Keywords: |  Actual Points:  0.5
Parent ID: | Points:  1.0
 Reviewer:  acute  |Sponsor:  Sponsor59-must
---+
Changes (by acute):

 * actualpoints:  0.4 => 0.5


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

Re: [tor-bugs] #34031 [Metrics/Onionperf]: Figure out warning about unknown error type when exporting .tpf file

[Tor Bug Tracker & Wiki]

#34031: Figure out warning about unknown error type when exporting .tpf file
---+
 Reporter:  karsten|  Owner:  acute
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor59-must
---+

Comment (by acute):

 To start off, a bit of background:
 The `ERRORCODE` field present in the tpf files combines error codes from
 both Tgen and Tor's json output. To produce `ERRORCODE`, we combine three
 fields: Tgen's `error_code` field, Tor's `failure_reason_local` (if
 present), and `failure_reason_remote` (if present, and only if
 failure_reason_local is present, too). While all the error codes are
 present individually in the json output, the `ERRORCODE` field is produced
 by matching between the two on the stream's source port, and is output
 only in the tpf file.

 This is something to keep in mind when we remove tpf files in the future.

 So, to confirm this bug only affects tpf files, and not json, and we are
 missing the following cases:


 Tgen Error: `PROXY` + Tor Error Local: `END` + Tor Error Remote:
 `CONNRESET` = `PROXY_END_CONNRESET`(missing key PROXY_END_CONNRESET)
 Tgen Error: `PROXY` + Tor Error Local: `END` + Tor Error Remote:
 `INTERNAL` = `PROXY_END_INTERNAL`(missing key PROXY_END_INTERNAL)
 Tgen Error: `PROXY` + Tor Error Local: `END` + Tor Error Remote: `MISC` =
 `PROXY_END_MISC` (missing key PROXY_END_MISC)

 We could add the following to our existing dictionary (in line with how we
 previously named these, see #29787), and this would fix the tpf export:
 {{{
 PROXY_END_CONNRESET: TOR/END/CONNRESET
 PROXY_END_INTERNAL: TOR/END/INTERNAL
 PROXY_END_MISC: TOR/END/MISC
 }}}
 I can attach a patch for the above.

 We additionally see this case:

 Tgen Error: None + Tor Error Local: `TIMEOUT` + Tor Error Remote: None =
 `_TIMEOUT` (missing key ERRORCODE)
 This happens when Tgen never sees an an error, but the stream reports a
 timeout, and results in warnings like the following:
 {{{
 2020-05-06 20:05:00 1588795500.42 [onionperf] [WARNING] KeyError while
 exporting torperf file, missing key ''ERRORCODE'', skipping transfer
 'transfer1m:2189'
 }}}

 Not sure how to handle cases where the Tgen transfer appears to complete
 with no error, but Tor repors a timeout - should we record this as an
 error, even if the transfer completed?

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

Re: [tor-bugs] #34190 [Internal Services/Service - trac]: New shared account idea

[Tor Bug Tracker & Wiki]

#34190: New shared account idea
--+-
 Reporter:  cypherpunk1   |  Owner:  qbi
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #34175| Points:
 Reviewer:|Sponsor:
--+-

Comment (by cypherpunk1):

 > Week 1: create/keep cypherpunk2020051 writecode, delete cypherpunks,
 delete cypherpunks2020*
 > Week 2: create/keep cypherpunk2020052 writecode, delete cypherpunks,
 delete cypherpunks2020*
 > Week 3: ...

 (and prevent the creation of 'cypherpunk*' account from trac.tpo website)


 @weekly rotate_cypherpunks.sh

 {{{
 e.g

 year = current year#2020
 month = current month#05
 weeknumber = current week of month#02

 delete account cypherpunks
 delete account ypherpunks{year}*

 delete account{year}{month}{weeknum}
 create account{year}{month}{weeknum} as password writecode

 update website text
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #34190 [Internal Services/Service - trac]: New shared account idea

[Tor Bug Tracker & Wiki]

#34190: New shared account idea
-+-
 Reporter:  cypherpunk1  |  Owner:  qbi
 Type:  task | Status:  new
 Priority:  Medium   |  Component:  Internal Services/Service -
 |  trac
  Version:   |   Severity:  Normal
 Keywords:   |  Actual Points:
Parent ID:  #34175   | Points:
 Reviewer:   |Sponsor:
-+-
 Old system:
 - cypherpunks, writecode
 - Anyone can use it
   - Bot attack / Script is very easy


 New system:
 - cypherpunk(RandomStringHere), writecode
  - ID:Password rotate every 1 week or 1 day
   - So they can't vandalize comments after 1 week or 1 day
 - Anyone can use it
  - Yes, this is a must
  - Bot attack / Script is difficult

 

 1. Open
 https://trac.torproject.org/projects/tor/wiki/WikiStart#UnofficialDocumentation
 2. Click "use this shared account of this week"
 3. Solve Captcha
 4. Display current ID:Password pair


 Before
 {{{
 Most of the content here is written by volunteers from around the world.
 If you find a topic you want to fix, expand, or create, please either
 create an account or use the multi-user account cypherpunks with the
 password writecode Note that edits will be credited to the cypherpunks
 account and not you personally.
 }}}

 After
 {{{
 Most of the content here is written by volunteers from around the world.
 If you find a topic you want to fix, expand, or create, please either
 create an account or use the multi-user account. Click here to view
 ''account information''. Note that edits will be credited to the
 cypherpunks account and not you personally.
 }}}

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

Re: [tor-bugs] #34175 [Internal Services/Service - trac]: spam attack on trac

[Tor Bug Tracker & Wiki]

#34175: spam attack on trac
--+--
 Reporter:  anarcat   |  Owner:  qbi
 Type:  defect| Status:  assigned
 Priority:  Immediate |  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunk1):

 Replying to [comment:14 qbi]:
 > Replying to [comment:13 cypherpunk1]:
 > If you want you can copy the text to a pad and paste the link to the pad
 here. I can make the change in trac for you.


 Version 461 looks fine to me. Can you revert it to version {{{461}}}?

 The text can be retrieved from
 
https://trac.torproject.org/projects/tor/wiki/org/projects/WeSupportTor?action=edit=461

 > 462   25 hourscypherpunks (vandalized)
 > 461   26 hourscypherpunks (last good)


 > i disabled the cypherpunks account

 How long are you going to lock it? Other cpunks might wondering why they
 can't log in if they didn't logged in recently.

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

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

[Tor Bug Tracker & Wiki]

#33564: Upgrade ZSTD to use Android NDK 20
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:  .1
  TorBrowserTeam202005R, GeorgKoppen202005   |
Parent ID:  #33184   | Points:
 Reviewer:  sysrqb   |Sponsor:
 |  Sponsor58-must
-+-

Comment (by gk):

 The patch is the same but `bug_33564_v3`
 (https://gitweb.torproject.org/user/gk/tor-browser-
 build.git/commit/?h=bug_33564_v3=601353544998d42707d4f935683521c43798e36b)
 builds on the slightly changed patch for #33557.

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

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

[Tor Bug Tracker & Wiki]

#33564: Upgrade ZSTD to use Android NDK 20
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:  .1
  TorBrowserTeam202005R, GeorgKoppen202005   |
Parent ID:  #33184   | Points:
 Reviewer:  sysrqb   |Sponsor:
 |  Sponsor58-must
-+-

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

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

[Tor Bug Tracker & Wiki]

#33760: Update rbm.conf to match NDK 20
-+-
 Reporter:  sisbell  |  Owner:  gk
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:
  TorBrowserTeam202005R, GeorgKoppen202005   |
Parent ID:  #33184   | Points:
 Reviewer:  sysrqb   |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] #33833 [Applications/Tor Browser]: Upgrade Rust To Use Android NDK 20 (was: Upgrade Rust To Use Android NDK 21)

[Tor Bug Tracker & Wiki]

#33833: Upgrade Rust To Use Android NDK 20
-+-
 Reporter:  sisbell  |  Owner:  gk
 Type:  defect   | Status:
 |  needs_revision
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb.rbm, |  Actual Points:  .5
  TorBrowserTeam202005, GeorgKoppen202005|
Parent ID:  #33184   | Points:
 Reviewer:  sysrqb   |Sponsor:
 |  Sponsor58-must
-+-
Changes (by gk):

 * keywords:  tbb-mobile, tbb.rbm, TorBrowserTeam202005R, GeorgKoppen202005
 => tbb-mobile, tbb.rbm, TorBrowserTeam202005, GeorgKoppen202005
 * status:  needs_review => needs_revision


Comment:

 I believe I have a slightly cleaner approach in `fenix_toolchain3`. I am
 currently testing the `rust` compilation.

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

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

[Tor Bug Tracker & Wiki]

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

Comment (by gk):

 The latest incarnation of the patch can be found on `fenix_toolchain3`
 (https://gitweb.torproject.org/user/gk/tor-browser-
 
build.git/commit/?h=fenix_toolchain3=12531d06332bc15093049e4d6bacf6f34ccf95bd).

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

Re: [tor-bugs] #34189 [Applications/Quality Assurance and Testing]: tbb-testsuite: fix the settings test for 78

[Tor Bug Tracker & Wiki]

#34189: tbb-testsuite: fix the settings test for 78
-+-
 Reporter:  acat |  Owner:  acat
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Quality Assurance and   |Version:
  Testing|
 Severity:  Normal   | Resolution:
 Keywords:  tbb-testsuite,   |  Actual Points:
  TorBrowserTeam202005R, ReleaseTrainMigration   |
Parent ID:  #27105   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by acat):

 * keywords:  tbb-testsuite, TorBrowserTeam202004, ReleaseTrainMigration =>
 tbb-testsuite, TorBrowserTeam202005R, ReleaseTrainMigration
 * status:  assigned => needs_review


Comment:

 Patch in https://gitlab.torproject.org/acat/tor-browser-bundle-
 testsuite/-/commits/34189 (65cae7af429d29b37196482ca6a464f538750b94). This
 passes for me, running it with `./tbb-testsuite --default-retry 1 --no-
 xdummy --xvfb --enable-tests settings /path/to/33533+5/build.tar.xz`.

 Changed prefs:
 {{{
 Removed in 27268:
 -

 browser.download.manager.retention
 browser.download.manager.scanWhenDone
 browser.newtabpage.preload
 browser.pocket.api
 browser.pocket.site
 browser.safebrowsing.enabled -> browser.safebrowsing.phishing.enabled
 browser.search.countryCode
 browser.zoom.siteSpecific
 datareporting.healthreport.about.reportUrl
 datareporting.healthreport.about.reportUrlUnified
 datareporting.healthreport.service.enabled
 device.sensors.enabled
 devtools.appmanager.enabled: None != False
 devtools.webide.autoinstallADBHelper ->
 devtools.webide.autoinstallADBExtension
 devtools.webide.autoinstallFxdtAdapters
 dom.enable_performance
 dom.enable_user_timing
 dom.event.highrestimestamp.enabled
 dom.gamepad.enabled
 dom.maxHardwareConcurrency
 general.appname.override
 general.appversion.override
 general.buildID.override
 general.oscpu.override
 general.platform.override
 general.productSub.override
 general.useragent.vendor
 general.useragent.vendorSub
 intl.charset.default
 media.audio_data.enabled
 media.eme.apiVisible
 media.gmp-eme-adobe.enabled
 media.gmp-eme-adobe.visible (not removed there, but mentioned)
 media.video_stats.enabled
 media.webspeech.synth.enabled
 network.jar.block-remote-files
 plugin.expose_full_path
 privacy.suppressModifierKeyEvents
 privacy.use_utc_timezone
 security.pki.sha1_enforcement_level -> 4
 security.tls.unrestricted_rc4_fallback
 ui.use_standins_for_native_colors

 Other
 -

 dom.indexedDB.enabled (removed in #23745)
 browser.pocket.enabled -> extensions.pocket.enabled (#31602)
 extensions.langpacks.signatures.required (reenabled in #31942)
 extensions.legacy.exceptions (doesn't do anything)
 extensions.enabledItems (doesn't do anything)
 extensions.enabledAddons (doesn't do anything)
 app.update.auto (set to False by marionette, we can maybe cover this with
 separate update tests in the future)
 }}}

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

Re: [tor-bugs] #34031 [Metrics/Onionperf]: Figure out warning about unknown error type when exporting .tpf file

[Tor Bug Tracker & Wiki]

#34031: Figure out warning about unknown error type when exporting .tpf file
---+
 Reporter:  karsten|  Owner:  acute
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor59-must
---+
Changes (by karsten):

 * owner:  karsten => acute
 * status:  accepted => assigned


Comment:

 Ah, no, you can have it back! I didn't make visible progress on this in
 the last 15 minutes.

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

Re: [tor-bugs] #33557 [Applications/Tor Browser]: Update Android Toolchain for Fenix

[Tor Bug Tracker & Wiki]

#33557: Update Android Toolchain for Fenix
-+-
 Reporter:  sisbell  |  Owner:  gk
 Type:  task | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, |  Actual Points:
  TorBrowserTeam202005R, GeorgKoppen202005   |
Parent ID:  #33184   | Points:
 Reviewer:  sysrqb   |Sponsor:
 |  Sponsor58-must
-+-
Changes (by gk):

 * keywords:  tbb-mobile, tbb-rbm, TorBrowserTeam202005, GeorgKoppen202005
 => tbb-mobile, tbb-rbm, TorBrowserTeam202005R, GeorgKoppen202005
 * status:  needs_revision => needs_review


Comment:

 Okay, `fenix_toolchain3` (https://gitweb.torproject.org/user/gk/tor-
 browser-
 
build.git/commit/?h=fenix_toolchain3=4e6b194109ed0aef2b8d1b46c97a4b038aba8858)
 has a better fix I believe.

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

Re: [tor-bugs] #34142 [Metrics/Onionperf]: Integrate reprocessing mode into analysis mode

[Tor Bug Tracker & Wiki]

#34142: Integrate reprocessing mode into analysis mode
---+
 Reporter:  karsten|  Owner:  karsten
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:  implemented
 Keywords: |  Actual Points:  0.4
Parent ID: | Points:  1.0
 Reviewer:  acute  |Sponsor:  Sponsor59-must
---+
Changes (by karsten):

 * status:  needs_review => closed
 * resolution:   => implemented
 * actualpoints:  0.3 => 0.4


Comment:

 Great! Squashed the two commits into one and pushed to master. Closing.
 Thanks!

 Can you add your actual points (with 480 minutes being 1.0 point) to mine?
 For example, I spent 195 minutes = 0.40625 points on this; if you spent 50
 minutes on this, that would be another 0.1 point, so 0.5 total.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #34189 [Applications/Quality Assurance and Testing]: tbb-testsuite: fix the settings test for 78

[Tor Bug Tracker & Wiki]

#34189: tbb-testsuite: fix the settings test for 78
-+-
 Reporter:  acat |  Owner:  acat
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:   |Version:
  Applications/Quality Assurance |   Keywords:  tbb-testsuite,
  and Testing|  TorBrowserTeam202004,
 Severity:  Normal   |  ReleaseTrainMigration
Actual Points:   |  Parent ID:  #27105
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 We should fix the settings tests so that it passes with the preferences
 that we currently have.

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

Re: [tor-bugs] #30318 [Applications/Tor Browser]: Integrate snowflake into mobile Tor Browser alpha

[Tor Bug Tracker & Wiki]

#30318: Integrate snowflake into mobile Tor Browser alpha
---+---
 Reporter:  gk |  Owner:  tbb-team
 Type:  enhancement| Status:
   |  needs_review
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-mobile, TorBrowserTeam202005R  |  Actual Points:
Parent ID:  #19001 | Points:
 Reviewer: |Sponsor:
   |  Sponsor28-must
---+---

Comment (by gk):

 Replying to [comment:5 cohosh]:
 > Replying to [comment:3 gk]:
 > > I don't have good repro steps but I've never seen such a problem with
 other pluggable transports. Sometimes when I don't get
 > > {{{
 > > - Circuit (1) CLOSED: flakey
 > > }}}
 > > I still get the TLS handshaking issue as above but the bootstrapping
 succeeds and I can use Tor Browser. So, it might not actually be a
 snowflake bug but something else. Hard to say.
 >
 > Awesome, thanks GeKo! We should be testing this with #34043. I can build
 with these patches on top of that or wait until we merge it to test this.

 Alright, here is a bundle that includes the code for #34043:

 https://people.torproject.org/~gk/testbuilds/tor-browser-testbuild-
 android-armv7-multi-qa-30318-34043.apk
 https://people.torproject.org/~gk/testbuilds/tor-browser-testbuild-
 android-armv7-multi-qa-30318-34043.apk.asc

 I have not hit the issue in comment:3 after a bit of testing which is
 promising as I did not have a problem encountering it with my previous
 test build.

 The branch for building I used was https://gitweb.torproject.org/user/gk
 /tor-browser-build.git/log/?h=bug_30318.

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

Re: [tor-bugs] #34031 [Metrics/Onionperf]: Figure out warning about unknown error type when exporting .tpf file

[Tor Bug Tracker & Wiki]

#34031: Figure out warning about unknown error type when exporting .tpf file
---+
 Reporter:  karsten|  Owner:  karsten
 Type:  defect | Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor59-must
---+

Comment (by acute):

 This was my next todo - I can return this to you in 2 hours or so? But I'm
 happy to work on something else if you've already started!

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

Re: [tor-bugs] #34175 [Internal Services/Service - trac]: spam attack on trac

[Tor Bug Tracker & Wiki]

#34175: spam attack on trac
--+--
 Reporter:  anarcat   |  Owner:  qbi
 Type:  defect| Status:  assigned
 Priority:  Immediate |  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by qbi):

 Replying to [comment:13 cypherpunk1]:
 > {{{
 > Submission rejected as potential spam
 > Maximum number of external links per post exceeded
 > }}}
 >
 >
 
https://trac.torproject.org/projects/tor/wiki/org/projects/WeSupportTor?action=edit=461
 > What now?

 If you want you can copy the text to a pad and paste the link to the pad
 here. I can make the change in trac for 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] #34142 [Metrics/Onionperf]: Integrate reprocessing mode into analysis mode

[Tor Bug Tracker & Wiki]

#34142: Integrate reprocessing mode into analysis mode
---+
 Reporter:  karsten|  Owner:  karsten
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:  0.3
Parent ID: | Points:  1.0
 Reviewer:  acute  |Sponsor:  Sponsor59-must
---+

Comment (by acute):

 Replying to [comment:6 karsten]:
 > Thanks for the review and the patch! I agree that we can make the
 analysis more flexible in the future, if we need it.
 >
 > I rebased my patch to master (now that the Python 3 port is in),
 squashed your patch into mine, and fixed three unit tests. Can you take
 another final review of the last two
 [https://gitweb.torproject.org/user/karsten/onionperf.git/log/?h=task-34142-2
 commits ed5e056 and ceb83af in my task-34142-2 branch]?

 Looking great, I think this can now be merged/closed :)

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

Re: [tor-bugs] #32537 [Applications/Quality Assurance and Testing]: Update marionette version used in tor browser testsuite, for ESR78 (was: Update marionette version used in tor browser testsuite, fo

[Tor Bug Tracker & Wiki]

#32537: Update marionette version used in tor browser testsuite, for ESR78
-+-
 Reporter:  boklm|  Owner:  acat
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Quality Assurance and   |Version:
  Testing|
 Severity:  Normal   | Resolution:
 Keywords:  ReleaseTrainMigration|  Actual Points:
  TorBrowserTeam202005R  |
Parent ID:  #33654   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor58
-+-
Changes (by acat):

 * status:  assigned => needs_review
 * keywords:  ReleaseTrainMigration => ReleaseTrainMigration
 TorBrowserTeam202005R


Old description:

> The version of marionette that is used by the tor browser testsuite needs
> to be updated in order to support esr68 versions of Tor Browser.

New description:

 The version of marionette that is used by the tor browser testsuite needs
 to be updated in order to support esr68 versions of Tor Browser.

 The package versions used are for current mozilla-central (78).

--

Comment:

 Patch in https://gitlab.torproject.org/acat/tor-browser-bundle-
 testsuite/-/commits/32537 (f3d05690356a10f76db4c22a677220fd2615e171). I
 also added a check for `virtualenv2`, as I needed it for my environment,
 and remove code for https://bugzilla.mozilla.org/show_bug.cgi?id=1345274
 workaround.

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

Re: [tor-bugs] #34031 [Metrics/Onionperf]: Figure out warning about unknown error type when exporting .tpf file

[Tor Bug Tracker & Wiki]

#34031: Figure out warning about unknown error type when exporting .tpf file
---+
 Reporter:  karsten|  Owner:  karsten
 Type:  defect | Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor59-must
---+
Changes (by karsten):

 * status:  assigned => accepted
 * owner:  acute => karsten


Comment:

 acute, I ''think'' that you're working on another ticket right now, so I'm
 assigning this to myself to work on this today and maybe tomorrow. If my
 assumption was wrong, please let me know ASAP, and we can sync who does
 what here. 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] #32335 [Core Tor/Tor]: Set up a .github repository on GitHub

[Tor Bug Tracker & Wiki]

#32335: Set up a .github repository on GitHub
--+--
 Reporter:  teor  |  Owner:  (none)
 Type:  task  | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-github, 043-deferred  |  Actual Points:
Parent ID:| Points:  1
 Reviewer:  nickm |Sponsor:
--+--

Comment (by teor):

 I think the license file is wrong, it says:
 "Copyright (c) 2019, Tor Project — Unofficial repositories"

 Maybe we want to delete it, or copy the one from the tor 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] #32537 [Applications/Quality Assurance and Testing]: Update marionette version used in tor browser testsuite, for ESR68

[Tor Bug Tracker & Wiki]

#32537: Update marionette version used in tor browser testsuite, for ESR68
-+-
 Reporter:  boklm|  Owner:  acat
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Quality Assurance and   |Version:
  Testing|
 Severity:  Normal   | Resolution:
 Keywords:  ReleaseTrainMigration|  Actual Points:
Parent ID:  #33654   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor58
-+-
Changes (by acat):

 * owner:  tbb-team => acat


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

Re: [tor-bugs] #10609 [Core Tor/Torflow]: aggregate.py should ignore empty scan-data files

[Tor Bug Tracker & Wiki]

#10609: aggregate.py should ignore empty scan-data files
--+--
 Reporter:  ln5   |  Owner:  (none)
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Core Tor/Torflow  |Version:
 Severity:  Normal| Resolution:
 Keywords:  easy intro|  Actual Points:
Parent ID:| Points:
 Reviewer:  dgoulet   |Sponsor:
--+--

Comment (by teor):

 I thought we weren't doing any fixes to torflow?

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

Re: [tor-bugs] #10609 [Core Tor/Torflow]: aggregate.py should ignore empty scan-data files

[Tor Bug Tracker & Wiki]

#10609: aggregate.py should ignore empty scan-data files
--+--
 Reporter:  ln5   |  Owner:  (none)
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Core Tor/Torflow  |Version:
 Severity:  Normal| Resolution:
 Keywords:  easy intro|  Actual Points:
Parent ID:| Points:
 Reviewer:  dgoulet   |Sponsor:
--+--
Changes (by asn):

 * reviewer:   => dgoulet


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

Re: [tor-bugs] #33617 [Core Tor/Tor]: Add a BandwidthStatistics option and consensus parameter

[Tor Bug Tracker & Wiki]

#33617: Add a BandwidthStatistics option and consensus parameter
-+-
 Reporter:  teor |  Owner:
 |  MrSquanchee
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  extra-review, prop313, ipv6, |  Actual Points:
  outreachy-ipv6, network-team-roadmap-2020Q1|
Parent ID:  #33052   | Points:  1
 Reviewer:  asn  |Sponsor:
 |  Sponsor55-can
-+-
Changes (by asn):

 * reviewer:   => asn


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

Re: [tor-bugs] #32335 [Core Tor/Tor]: Set up a .github repository on GitHub

[Tor Bug Tracker & Wiki]

#32335: Set up a .github repository on GitHub
--+--
 Reporter:  teor  |  Owner:  (none)
 Type:  task  | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-github, 043-deferred  |  Actual Points:
Parent ID:| Points:  1
 Reviewer:  nickm |Sponsor:
--+--
Changes (by asn):

 * reviewer:   => nickm


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