Re: [tor-bugs] #21910 [Core Tor/Tor]: Refactor connection_edge_process_relay_cell()

[Tor Bug Tracker & Wiki]

#21910: Refactor connection_edge_process_relay_cell()
-+-
 Reporter:  dgoulet  |  Owner:  neel
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Low  |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  refactor, easy, technical-debt big-  |  Actual Points:
  function   |
Parent ID:   | Points:  4
 Reviewer:   |Sponsor:
-+-
Changes (by neel):

 * cc: neel (added)
 * owner:  (none) => neel
 * status:  new => assigned


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

Re: [tor-bugs] #34312 [Metrics/Consensus Health]: Remove teor from the "Fallback Directory Summary" emails

[Tor Bug Tracker & Wiki]

#34312: Remove teor from the "Fallback Directory Summary" emails
--+-
 Reporter:  teor  |  Owner:  tom
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Metrics/Consensus Health  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-fallback  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by arma):

 Let's put dgoulet onto the recipient list while we're at it.

 Where does this change happen? That is, is this part of "doctor", or is it
 some other component?

 For context, in recent months we've gotten one mail in April and one mail
 in May, so I'd say it is doing very well at not producing false positives.
 Unless it only runs once a month I guess. :)

 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

[tor-bugs] #34312 [Metrics/Consensus Health]: Remove teor from the "Fallback Directory Summary" emails

[Tor Bug Tracker & Wiki]

#34312: Remove teor from the "Fallback Directory Summary" emails
--+--
 Reporter:  teor  |  Owner:  tom
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Metrics/Consensus Health  |Version:
 Severity:  Normal|   Keywords:  tor-fallback
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Hi,

 Please remove my email address from the recipients of the "Fallback
 Directory Summary" emails.

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

Re: [tor-bugs] #34311 [Core Tor/Tor]: Space out code in relay.c

[Tor Bug Tracker & Wiki]

#34311: Space out code in relay.c
--+--
 Reporter:  neel  |  Owner:  neel
 Type:  enhancement   | Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  easy  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by neel):

 * type:  defect => enhancement


Old description:

> Yes, I do understand that Tor is working on automatic code checks for
> things like code spacing, but I still noticed a lot of spacing issues in
> relay.c.
>
> This patches fixes all (or at least most) of relay.c.

New description:

 Yes, I do understand that Tor is working on automatic code checks for
 things like code spacing and that I should work on that instead of sending
 spacing patches, but I still noticed a lot of spacing issues in relay.c
 (more than normal) so I just **had** to submit this.

 My PR fixes all (or at least most) of relay.c.

--

Comment:

 PR: https://github.com/torproject/tor/pull/1906

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #34311 [Core Tor/Tor]: Space out code in relay.c

[Tor Bug Tracker & Wiki]

#34311: Space out code in relay.c
--+--
 Reporter:  neel  |  Owner:  neel
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  easy
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Yes, I do understand that Tor is working on automatic code checks for
 things like code spacing, but I still noticed a lot of spacing issues in
 relay.c.

 This patches fixes all (or at least most) of relay.c.

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

Re: [tor-bugs] #34298 [Metrics/Onionperf]: Address networkx's API change, which breaks OnionPerf

[Tor Bug Tracker & Wiki]

#34298: Address networkx's API change, which breaks OnionPerf
---+
 Reporter:  phw|  Owner:  phw
 Type:  defect | Status:  needs_revision
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:  0.1
 Reviewer: |Sponsor:
---+
Changes (by karsten):

 * status:  needs_review => needs_revision


Comment:

 I noticed the same issue when setting up an OnionPerf instance on Ubuntu.
 It would be nice to find a solution that works for 2.2.1 and 2.4.

 Is there any way that we can avoid calling `g.node` or `g.nodes`? Maybe
 there's a function for that that hasn't changed its name between 2.2.1 and
 2.4? Or maybe we can specify `socksproxy` when adding the node in the
 first place? (It's too late for me to try this out today, but I wanted to
 leave this idea here just in case somebody wants to pick it up.)

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

Re: [tor-bugs] #34223 [Internal Services/Service - lists]: Please create a 'translation-admin' mailing list

[Tor Bug Tracker & Wiki]

#34223: Please create a 'translation-admin' mailing list
---+
 Reporter:  sysrqb |  Owner:  qbi
 Type:  task   | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Internal Services/Service - lists  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by anarcat):

 note that this was done for #34174

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

Re: [tor-bugs] #32179 [Internal Services/Tor Sysadmin Team]: retire orestis

[Tor Bug Tracker & Wiki]

#32179: retire orestis
-+
 Reporter:  weasel   |  Owner:  weasel
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:  #31659   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by anarcat):

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


Comment:

 scheduled backups removal, revoked puppet:

 {{{
 $ ./retire -v -H orestis.torproject.org retire-all
 starting tasks at 2020-05-25 17:37:03.873529
 not wiping instance orestis.torproject.org data: no parent host
 scheduling orestis.torproject.org backup disks removal on host
 bungei.torproject.org
 checking for path "/srv/backups/bacula/orestis.torproject.org/" on
 bungei.torproject.org
 scheduling rm -rf "/srv/backups/bacula/orestis.torproject.org/" to run on
 bungei.torproject.org in 30 days
 warning: commands will be executed using /bin/sh
 job 32 at Wed Jun 24 21:37:00 2020
 Notice: Revoked certificate with serial 50
 Notice: Removing file Puppet::SSL::Certificate orestis.torproject.org at
 '/var/lib/puppet/ssl/ca/signed/orestis.torproject.org.pem'
 orestis.torproject.org
 Submitted 'deactivate node' for orestis.torproject.org with UUID 2484e196
 -707a-42f6-91a2-ef0c46654d16
 completed tasks, elasped: 0:00:10.723336 (user 2.13 system 0.09 chlduser
 0.03 chldsystem 0.03 RSS 42.4 MB)
 }}}

 removed from LDAP:

 {{{
 367 host=orestis,ou=hosts,dc=torproject,dc=org
 host: orestis
 hostname: orestis.torproject.org
 objectClass: top
 objectClass: debianServer
 distribution: Debian
 access: restricted
 admin: torproject-ad...@torproject.org
 architecture: amd64
 physicalHost: cloud.ipnett.se
 description: onionoo
 purpose: onionoo.torproject.org
 allowedGroups: onionoo
 allowedGroups: onionoo-unpriv
 l: Sweden
 ipHostNumber: 2001:6b0:5a:5000::4
 ipHostNumber: 89.45.235.19
 sshRSAHostKey: ssh-ed25519
 C3NzaC1lZDI1NTE5IGrDQvHxq6hpRz47n2MOUm0ylhPfCO0BtEtb5FjdaWXL
 root@orestis
 sshRSAHostKey: ssh-rsa
 
B3NzaC1yc2EDAQABAAABAQDAmeNHl4EMYDLtK/O8MxdllXX8Vf7Ryjo+7WwPmssCe1bWpUn5BbT7pJALTirF2Su7QB3iEQeVI/RBp7rsG5LKi7itJ4CaEuD8i/wKnl/paUeHIAGgg/zsvpwBAg96GloFpUeMUSVMaWfDYIwfDXB2Z0zkPU1ctQVMLXnLftHTGKn0ZUpjxXCBpC1E5gee2AHqnfR3vFRhe+xpMS/9PsOeOjaACl0aNmNQJaWqRVreM3HewxLP2LgdQlqzsSr5ukj9prhf3+265+yQf9fNStHRIXzk4RsEBGYx3gAmme9qJJ+/nh0JSqhSXHRt1Squx0u+pmUV/XsyRUm0dvdahLP3
 root@orestis
 rebootPolicy: rotation
 }}}

 removed from tor-passwords.

 deleted instance from sunet as well, which reminds me we have some spare
 capacity there now.

 all 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] #33433 [Metrics/Onionperf]: Add error handling for older stem versions

[Tor Bug Tracker & Wiki]

#33433: Add error handling for older stem versions
---+
 Reporter:  acute  |  Owner:  metrics-team
 Type:  defect | Status:  merge_ready
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID:  #33321 | Points:  0.5
 Reviewer:  karsten|Sponsor:  Sponsor59-must
---+
Changes (by karsten):

 * status:  needs_review => merge_ready
 * reviewer:   => karsten


Comment:

 Patch looks good, will merge together with #30586. Thanks for the analysis
 and for the fix!

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

Re: [tor-bugs] #31659 [Internal Services/Tor Sysadmin Team]: new onionoo hosts

[Tor Bug Tracker & Wiki]

#31659: new onionoo hosts
-+-
 Reporter:  weasel   |  Owner:  weasel
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * owner:  tpa => weasel
 * status:  new => assigned


Comment:

 weasel has picked this up again. oo-hetzner-03 retired, and omeiense
 (#34036), and orestis (#32179) scheduled for retirement.

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

Re: [tor-bugs] #30586 [Metrics/Onionperf]: requirements are not included in setup.py

[Tor Bug Tracker & Wiki]

#30586: requirements are not included in setup.py
---+
 Reporter:  irl|  Owner:  phw
 Type:  defect | Status:  merge_ready
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.45
Parent ID:  #33321 | Points:  0.5
 Reviewer: |Sponsor:  Sponsor59-must
---+

Comment (by karsten):

 Okay, I agree with the general approach to have different steps for
 researchers and developers and for ourselves.

 However, I'm still having difficulties with building and running OnionPerf
 without using `pip`: The command `python3 setup.py install --user` still
 runs `pip` in the background, and I'm unclear how to set `PYTHONPATH` in
 order to avoid running that command in the first place. Once I know how to
 do that I can merge this branch (and apply the #33433 patch on top of it).

 Another minor issue is that `python3-setuptools` needs to be listed as
 required package in the instructions now. I can add that to `README.md`,
 if that's the only remaining issue.

 Thanks for your patience! :)

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

Re: [tor-bugs] #34263 [Circumvention/Snowflake]: Library selection for using WebRTC for the project.

[Tor Bug Tracker & Wiki]

#34263: Library selection for using WebRTC for the project.
-+--
 Reporter:  HashikD  |  Owner:  (none)
 Type:  task | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-mobile |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by cohosh):

 Replying to [comment:6 arlolra]:
 > Sorry if this was covered elsewhere but is using pion, like the rest of
 the snowflake ecosystem, not an option?

 This is a good place to discuss this. I don't think we need to worry about
 using a different library for this project. If we were planning on reusing
 code from the stand-alone proxy-go instances that would be one thing. But
 given that we have to implement a UI with this (similar to the
 webextension) it doesn't seem like code sharing is an option.

 Another possible advantage to using pion is that it '''might''' give us
 more control if the Chrome WebRTC implementation is fingerprinted and
 blocked. OTOH, maybe the Chrome WebRTC implementation is more popular with
 other apps and is less likely to be blocked. Not knowing which way this
 will go, I'm inclined to go with whichever library is easiest for us to
 maintain the project.

 As far as interoperability, pion has been careful about testing to make
 sure their code plays well with other WebRTC implementations. If we have
 problems we should definitely upstream them but I suspect we'll be okay.

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

Re: [tor-bugs] #33963 [Applications/Tor Browser]: Uplift test for 21321 (Add test for .onion whitelisting)

[Tor Bug Tracker & Wiki]

#33963: Uplift test for 21321 (Add test for .onion whitelisting)
+---
 Reporter:  acat|  Owner:  acat
 Type:  task| Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  ReleaseTrainMigration ff78-esr  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:  Sponsor58
+---
Changes (by acat):

 * keywords:  ReleaseTrainMigration => ReleaseTrainMigration ff78-esr


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

Re: [tor-bugs] #33960 [Applications/Tor Browser]: Uplift patch for "32414: Make Services.search.addEngine obey FPI"

[Tor Bug Tracker & Wiki]

#33960: Uplift patch for "32414: Make Services.search.addEngine obey FPI"
-+-
 Reporter:  acat |  Owner:  acat
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ReleaseTrainMigration,   |  Actual Points:
  TorBrowserTeam202004, ff78-esr |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor58
-+-
Changes (by acat):

 * keywords:  ReleaseTrainMigration, TorBrowserTeam202004 =>
 ReleaseTrainMigration, TorBrowserTeam202004, ff78-esr


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

Re: [tor-bugs] #33960 [Applications/Tor Browser]: Uplift patch for "32414: Make Services.search.addEngine obey FPI"

[Tor Bug Tracker & Wiki]

#33960: Uplift patch for "32414: Make Services.search.addEngine obey FPI"
-+-
 Reporter:  acat |  Owner:  acat
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ReleaseTrainMigration,   |  Actual Points:
  TorBrowserTeam202004   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor58
-+-
Changes (by acat):

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


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

Re: [tor-bugs] #33963 [Applications/Tor Browser]: Uplift test for 21321 (Add test for .onion whitelisting)

[Tor Bug Tracker & Wiki]

#33963: Uplift test for 21321 (Add test for .onion whitelisting)
--+---
 Reporter:  acat  |  Owner:  acat
 Type:  task  | Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ReleaseTrainMigration |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor58
--+---
Changes (by acat):

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


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

Re: [tor-bugs] #32802 [Internal Services/Tor Sysadmin Team]: retire kvm4, 8 VMs to migrate

[Tor Bug Tracker & Wiki]

#32802: retire kvm4, 8 VMs to migrate
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  project  | Status:
 |  accepted
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Major| Resolution:
 Keywords:  tpa-roadmap-may  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 in progress:

 {{{
 nwipe --autonuke --method=random --verify=off /dev/sdb
 nwipe --autonuke --method=random --rounds=2 /dev/nvme1n1
 }}}

 next up is the final self-destruct procedure and cancelation.

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

Re: [tor-bugs] #32802 [Internal Services/Tor Sysadmin Team]: retire kvm4, 8 VMs to migrate

[Tor Bug Tracker & Wiki]

#32802: retire kvm4, 8 VMs to migrate
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  project  | Status:
 |  accepted
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Major| Resolution:
 Keywords:  tpa-roadmap-may  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 started retirement procedure:

  1. N/A
  2. removed from nagios
  3. N/A
  4. removed from puppet, backups (fabric)
  5. removed from LDAP:
 {{{
 380 host=kvm4,ou=hosts,dc=torproject,dc=org
 objectClass: top
 objectClass: debianServer
 host: kvm4
 hostname: kvm4.torproject.org
 architecture: amd64
 admin: torproject-ad...@torproject.org
 sshRSAHostKey: ssh-rsa
 
B3NzaC1yc2EDAQABAAABAQCjqP9zljgAnZj666cVW00GaF4rII8t1gYCUvCHX8+OIxffowAuNfxVAfk1AFqCMZCkP8ULLJCevAfrcbc86uVnzQ9J0bND4gFJE4dTDQeCgVrPqR+bt48V2U/KbYC93q2QTRa/UjHitBxO7Z1ryvYh0J0HluJew9ZIBXZ21/uqkqxQ4GWLXo7fXHOHTzKEtP6wwpWiYc9IOEfe4+93vmNX0ubPfgnsAh+2+2/SPUQairOc4c7XmSQM/fyyadoIit/lYANuXfPNidXQtgie1jggyD+Ti72mtHI7pRlVSXKRhXOiuganboENv0Hb9KszStLYnkk/3jJnCAxcGP6VVdpx
 root@kvm4
 sshRSAHostKey: ssh-ed25519
 C3NzaC1lZDI1NTE5IMB96RR18dP0BQ9ySEcpWuBcF4z5rET4KpvzOLKx4m9T
 root@kvm4
 description: KVM host
 purpose: KVM host
 access: restricted
 distribution: Debian
 ipHostNumber: 94.130.38.33
 ipHostNumber: 2a01:4f8:10b:239f::2
 l: Falkenstein, Saxony, Germany
 rebootPolicy: manual
 }}}
  6. removed from source code (puppet, auto-dns, domains, wiki)
  7. removed from tor-passwords
  8. N/A (dnswl)
  9. removed from spreadsheet

 last steps: disk wipes and cancelation with hetzner.

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

Re: [tor-bugs] #32355 [Applications/Tor Browser]: Tor Browser for Linux/ARMv7 (x86_64 build arch)

[Tor Bug Tracker & Wiki]

#32355: Tor Browser for Linux/ARMv7 (x86_64 build arch)
+--
 Reporter:  JeremyRand  |  Owner:  tbb-team
 Type:  project | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam202005R  |  Actual Points:
Parent ID:  #12631  | Points:
 Reviewer:  gk  |Sponsor:
+--
Changes (by gk):

 * keywords:  tbb-rbm, TorBrowserTeam201904 => tbb-rbm,
   TorBrowserTeam202005R
 * status:  new => needs_review
 * reviewer:   => gk


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

Re: [tor-bugs] #34264 [Circumvention/Snowflake]: Discussion on using a library for HTTP requests.

[Tor Bug Tracker & Wiki]

#34264: Discussion on using a library for HTTP requests.
-+--
 Reporter:  HashikD  |  Owner:  (none)
 Type:  task | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-mobile |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by HashikD):

 * status:  new => needs_review


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

Re: [tor-bugs] #34263 [Circumvention/Snowflake]: Library selection for using WebRTC for the project.

[Tor Bug Tracker & Wiki]

#34263: Library selection for using WebRTC for the project.
-+--
 Reporter:  HashikD  |  Owner:  (none)
 Type:  task | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-mobile |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by HashikD):

 * status:  new => needs_review


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

Re: [tor-bugs] #32355 [Applications/Tor Browser]: Tor Browser for Linux/ARMv7 (x86_64 build arch)

[Tor Bug Tracker & Wiki]

#32355: Tor Browser for Linux/ARMv7 (x86_64 build arch)
---+--
 Reporter:  JeremyRand |  Owner:  tbb-team
 Type:  project| Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201904  |  Actual Points:
Parent ID:  #12631 | Points:
 Reviewer: |Sponsor:
---+--

Comment (by JeremyRand):

 Updated branch at ​https://notabug.org/JeremyRand/tor-browser-build/src
 /armhf-esr68 (commit hash `bcd0e21237a0aeb598d1cf388b08d6f4e28eecd0`).
 Builds binaries that work fine on my Asus C201 (running PrawnOS, based on
 Debian Buster).  Binutils, Clang, Rust, Rust's stdlib, and cbindgen are
 all built from source in rbm, as with x86.  libgcc/libstdc++ from Debian
 Buster's repos are used as build-time dependencies (removing them is
 likely to be nontrivial).

 As discussed with Georg on IRC, I'm now requesting informal review, *not*
 for the purpose of determining eligibility to be merged at this time, but
 for the purpose of determining whether there are any likely conflicts
 between this branch and the eventual ESR78 port of Tor Browser.  Georg
 informs me that this will definitely not be considered for merge until
 after ESR78 is active; that's totally fine from my point of view.  I would
 appreciate any informal review that could point out things that might be
 merge blockers after ESR78 is active, or things that may need a
 rewrite/refactor to be compatible with ESR78.  (However, I recognize that
 this is a low priority for the Tor Browser team, probably more so due to
 the recent staff losses, so I will accept whatever delays happen in
 reviewing this.)  I am already aware that the use of network access while
 building the `tor` project is a blocker; I intend to fix that in the same
 way that I already fixed it in the `firefox` project (i.e. switching the
 build container to Debian Buster, and installing the relevant `armhf`
 packages via `apt-get` as part of container construction).

 Cheers!

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

Re: [tor-bugs] #30719 [Core Tor/sbws]: Work out why 90% of sbws measurements fail

[Tor Bug Tracker & Wiki]

#30719: Work out why 90% of sbws measurements fail
---+---
 Reporter:  teor   |  Owner:  juga
 Type:  defect | Status:  closed
 Priority:  High   |  Milestone:  sbws: 1.1.x-final
Component:  Core Tor/sbws  |Version:  sbws: 1.1.0
 Severity:  Major  | Resolution:  fixed
 Keywords:  sbws-roadmap   |  Actual Points:
Parent ID:  #33121 | Points:  2
 Reviewer: |Sponsor:
---+---
Changes (by juga):

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


Comment:

 Since longclaw changed to sbws 1.1.0+84.g3033421, and as commented in
 https://trac.torproject.org/projects/tor/ticket/30905#comment:8, the
 number of failures has been around 1000.
 So the high number of failures were not due to measurement failures, but
 bad counting of the actual errors.
 I think we can close this ticket.

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

[tor-bugs] #34310 [Core Tor/sbws]: Maybe add new type of errors in the bandwidth file

[Tor Bug Tracker & Wiki]

#34310: Maybe add new type of errors in the bandwidth file
---+---
 Reporter:  juga   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  sbws: unspecified
Component:  Core Tor/sbws  |Version:  sbws: 1.1.0
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+---
 As commented in
 https://trac.torproject.org/projects/tor/ticket/30905#comment:9

 Things that are not really failures:

 when loading the results, the relays that changed ip are excluded. I
 could add a patch to count all the results first, which reduces the number
 of failures in around 1000.
 when sbws is restarted, all the queued relays to measure that didn't
 start to be measured yet, are not saved in the results, but the attempt
 has already been count. We could also add a patch to count the attempt in
 measure_relay, instead of main_loop, though then we won't know the number
 of attempts counting from the moment they were queued.
 real failures would happen when result_putter_error is triggered, or
 some bug makes sbws stall, which then will print the TICKET_MSG error. In
 the 1st case, we could actually count an error.

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

[tor-bugs] #34309 [Core Tor/sbws]: Check that relay_recent_measurement_attempt_count and relay_recent_priority_list_count are correc

[Tor Bug Tracker & Wiki]

#34309: Check that relay_recent_measurement_attempt_count and
relay_recent_priority_list_count are correc
---+---
 Reporter:  juga   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  sbws: 1.1.x-final
Component:  Core Tor/sbws  |Version:  sbws: 1.1.0
 Severity:  Normal |   Keywords:  sbws-roadmap
Actual Points: |  Parent ID:  #33121
   Points: |   Reviewer:
  Sponsor: |
---+---
 This was a comment in
 https://trac.torproject.org/projects/tor/ticket/30905#comment:9

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

Re: [tor-bugs] #33590 [Core Tor/sbws]: SBWS maatuska is broken

[Tor Bug Tracker & Wiki]

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

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


Comment:

 Replying to [comment:4 starlight]:
 > https://metrics.torproject.org/totalcw.png?start=2020-02-23
 >
 > ?

 Thanks for the remainder, it was not forgotten and there was no new code
 to modify here, just to change maatuska sbws version, which was not urgent
 since we still have a majority of torflow bwauths.
 We've been working on the tickets tagged as `sbws-roadmap` and
 prioritized. This ticket doesn't have that tag and the title `broken` i
 less descriptive than the one in #33350, where i already copied the
 information you posted here.
 Hope now you're fine i close this ticket.

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

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

[Tor Bug Tracker & Wiki]

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

Comment (by juga):

 Last Saturday, 23th May, maatuska has updated to sbws version
 1.1.0+84.g3033421 (current maint-1.1 branch) and can be observed that the
 total consensus bandwidth is decreasing close to the rest of bwauths.
 i'm not closing this ticket yet cause i'd like to give an explanation on
 why i think this happening and because there are still some relays being
 measured too high (see
 https://trac.torproject.org/projects/tor/ticket/33947#comment: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] #34308 [Circumvention/Snowflake]: Creating a new Snowflake Android project.

[Tor Bug Tracker & Wiki]

#34308: Creating a new Snowflake Android project.
-+--
 Reporter:  HashikD  |  Owner:  (none)
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-mobile |  Actual Points:
Parent ID:  #34266   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by HashikD):

 * status:  new => needs_review


Comment:

 My GitHub mirror [https://github.com/Hashik-Donthineni/Snowflake-Mobile
 Link]

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

Re: [tor-bugs] #33387 [Internal Services/Tor Sysadmin Team]: establish tmpfs policy

[Tor Bug Tracker & Wiki]

#33387: establish tmpfs policy
-+-
 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:  #31239   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

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


Comment:

 after discussing this briefly with weasel, he suggested we set to the
 smallest of 2GB or 50% of ram, but that might be hard to implement in the
 installer. because 2GB might be too big for some hosts, leave this at
 512MB for now.

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

Re: [tor-bugs] #33871 [Core Tor/sbws]: Scale exactly as torflow does?

[Tor Bug Tracker & Wiki]

#33871: Scale exactly as torflow does?
-+-
 Reporter:  juga |  Owner:  juga
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  sbws:
 |  1.1.x-final
Component:  Core Tor/sbws|Version:
 Severity:  Normal   | Resolution:
 Keywords:  sbws-majority-blocker, sbws-roadmap  |  Actual Points:
Parent ID:  #33775   | Points:
 Reviewer:  ahf, gk  |Sponsor:
-+-

Comment (by juga):

 Note for the reviewer:
 In the end i'm taking into account consensus bandwidth when there is not
 observed bandwidth, but i'm still not sure that's what should be done
 cause Torflow doesn't do it.
 I'm also not sure whether to take the tor process observed bandwidth
 instead of the observed bandwidth that was stored at the moment of making
 the measurement. Torflow does not do this, but it measures relays faster
 and more often.
 I've observed (see
 https://trac.torproject.org/projects/tor/ticket/33947#comment:2) that the
 relays that have big differences with Torflow might be due missing
 descriptor/consensus bandwidth.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #34308 [Circumvention/Snowflake]: Creating a new Snowflake Android project.

[Tor Bug Tracker & Wiki]

#34308: Creating a new Snowflake Android project.
-+--
 Reporter:  HashikD  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   |   Keywords:  snowflake-mobile
Actual Points:   |  Parent ID:  #34266
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 Creating a new/fresh project for Snowflake Android with just empty
 activity.

 Project Name: Snowflake-Mobile
 Package Name: org.torproject.snowflake
 Min-SDK: API-21 - Android 5.0 Lollipop

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

Re: [tor-bugs] #33947 [Core Tor/sbws]: Compare sbws and Torflow

[Tor Bug Tracker & Wiki]

#33947: Compare sbws and Torflow
-+-
 Reporter:  juga |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  sbws:
 |  1.1.x-final
Component:  Core Tor/sbws|Version:  sbws: 1.1.0
 Severity:  Normal   | Resolution:
 Keywords:  sbws-roadmap, GeorgKoppen202005  |  Actual Points:
Parent ID:  #33121   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by juga):

 * Attachment "bw_comparative_extra.ods" 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] #33947 [Core Tor/sbws]: Compare sbws and Torflow

[Tor Bug Tracker & Wiki]

#33947: Compare sbws and Torflow
-+-
 Reporter:  juga |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  sbws:
 |  1.1.x-final
Component:  Core Tor/sbws|Version:  sbws: 1.1.0
 Severity:  Normal   | Resolution:
 Keywords:  sbws-roadmap, GeorgKoppen202005  |  Actual Points:
Parent ID:  #33121   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by juga):

 Something have not commented here is to check is how individual bandwidth
 values differ from one authority to other.
 I think this is useful for #33871, so i'm including it here.
 For that, i've implemented a new function in
 https://gitlab.torproject.org/juga/bwauthealth.
 I obtained the bw of all bwauths for the consensus on 25.05.2020, then in
 libre office i calculated the median of the torflow bwauths, then
 calculated the percentage difference with longclaw and maatuska (right
 before maatuska changed to last sbws version) and finally counted the
 number of relays for which the percentage difference is greater than 50.
 This is 626 relays for lonclaw.
 Then i counted how many of the relays with a percentage difference greater
 than 50 are greater than 1.
 This is 151 for longclaw. The cases in which longclaw (but not Torflow)
 has bw 1 is probably because not having the descriptors and consensus
 bandwidth.
 I attach the libre office file.
 I think it would be interesting also to see if it's actually the case that
 those bw are 1 cause of missing descriptors/consensus.
 I could have include this calculations as part of the code too, but for
 now, it was faster this way.
 I leave for #33350 the case of maatuska and the case in which the sbws bws
 are greater than 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] #34263 [Circumvention/Snowflake]: Library selection for using WebRTC for the project.

[Tor Bug Tracker & Wiki]

#34263: Library selection for using WebRTC for the project.
-+
 Reporter:  HashikD  |  Owner:  (none)
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-mobile |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by HashikD):

 Adding to my above comment, there are no really good alternatives to
 **Google's Native WebRTC** library, even for iOS they use this very same
 library. All the testing or demo apps that are trying to demonstrate
 WebRTC use this library (Android/iOS).

 If we want to deviate and use another good library, like Pion for
 instance, we have to write our own JNI wrapper. Besides, this library is
 good enough and works very fine. It handles asynchronous calls while
 creating SDP's and ICE trickling, we don't have to handle it manually.

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

Re: [tor-bugs] #34263 [Circumvention/Snowflake]: Library selection for using WebRTC for the project.

[Tor Bug Tracker & Wiki]

#34263: Library selection for using WebRTC for the project.
-+
 Reporter:  HashikD  |  Owner:  (none)
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-mobile |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Description changed by HashikD:

Old description:

> Selecting a good and resilient library with frequent updates is
> imperative, these are the libraries available:
> \\
> Google's official library that we have to compile to use in our project:
> http://webrtc.github.io/webrtc-org/native-code/android/
> \\
> Ant Server's library: https://github.com/ant-media/Ant-Media-Server/wiki
> /WebRTC-Android-SDK-Documentation - Here they used "Ant Media Server" as
> signaling server we can change that.

New description:

 Selecting a good and resilient library with frequent updates is
 imperative, these are the libraries available:
 \\
 Google's official library that we have to compile to use in our project:
 http://webrtc.github.io/webrtc-org/native-code/android/
 \\
 ~~Ant Server's library: https://github.com/ant-media/Ant-Media-Server/wiki
 /WebRTC-Android-SDK-Documentation - Here they used "Ant Media Server" as
 signaling server we can change that.~~

 Ant Media Server uses WebRTC library on top of that they added their own
 functionality to make it work with Ant Media Server. Which is not very
 useful for our project.

--

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

Re: [tor-bugs] #34264 [Circumvention/Snowflake]: Discussion on using a library for HTTP requests.

[Tor Bug Tracker & Wiki]

#34264: Discussion on using a library for HTTP requests.
-+
 Reporter:  HashikD  |  Owner:  (none)
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-mobile |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by HashikD):

 Although I said OkHttp is suffice. Retrofit is feature-rich, like auto
 parsing of JSON objects, another main and important thing is it works very
 well and integrate well with RxJava (#34307).

 Besides, code looks much simpler and elegant with OkHttp.

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

Re: [tor-bugs] #34264 [Circumvention/Snowflake]: Discussion on using a library for HTTP requests.

[Tor Bug Tracker & Wiki]

#34264: Discussion on using a library for HTTP requests.
-+
 Reporter:  HashikD  |  Owner:  (none)
 Type:  task | Status:  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-mobile |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by HashikD):

 * status:  new => needs_revision


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

Re: [tor-bugs] #34299 [Core Tor/Tor]: man page has wrong default for MinUptimeHidServDirectoryV2

[Tor Bug Tracker & Wiki]

#34299: man page has wrong default for MinUptimeHidServDirectoryV2
-+
 Reporter:  arma |  Owner:  (none)
 Type:  defect   | Status:  merge_ready
 Priority:  Medium   |  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor |Version:  Tor: 0.2.6.3-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs 043-backport  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  dgoulet  |Sponsor:
-+
Changes (by dgoulet):

 * keywords:   => tor-hs 043-backport
 * reviewer:   => dgoulet
 * status:  needs_review => merge_ready
 * milestone:  Tor: 0.4.3.x-final => Tor: 0.4.4.x-final


Comment:

 lgtm.

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

Re: [tor-bugs] #34307 [Circumvention/Snowflake]: RxJava library for making asynchronous calls.

[Tor Bug Tracker & Wiki]

#34307: RxJava library for making asynchronous calls.
-+--
 Reporter:  HashikD  |  Owner:  (none)
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-mobile |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by HashikD):

 * status:  new => needs_review


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

Re: [tor-bugs] #34307 [Circumvention/Snowflake]: RxJava library for making asynchronous calls.

[Tor Bug Tracker & Wiki]

#34307: RxJava library for making asynchronous calls.
-+--
 Reporter:  HashikD  |  Owner:  (none)
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-mobile |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Description changed by HashikD:

Old description:

> To be clear it's perfectly fine starting a project without this library
> by using Android's official inbuild **AsyncTask** class but Google is
> deprecating the Async task library in favor of RxJava.
>
> [https://www.xda-developers.com/asynctask-deprecate-android-11/
> Reference]

New description:

 To be clear it's perfectly fine starting a project without this library by
 using Android's official inbuild **AsyncTask** class but Google is
 deprecating the Async task library in favor of RxJava. Async task works
 for now but might not work in future versions of Android.

 [https://www.xda-developers.com/asynctask-deprecate-android-11/ Reference]

--

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

Re: [tor-bugs] #34307 [Circumvention/Snowflake]: RxJava library for making asynchronous calls.

[Tor Bug Tracker & Wiki]

#34307: RxJava library for making asynchronous calls.
-+
 Reporter:  HashikD  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-mobile |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by HashikD):

 * keywords:   => snowflake-mobile


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

[tor-bugs] #34307 [Circumvention/Snowflake]: RxJava library for making asynchronous calls.

[Tor Bug Tracker & Wiki]

#34307: RxJava library for making asynchronous calls.
-+
 Reporter:  HashikD  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+
 To be clear it's perfectly fine starting a project without this library by
 using Android's official inbuild **AsyncTask** class but Google is
 deprecating the Async task library in favor of RxJava.

 [https://www.xda-developers.com/asynctask-deprecate-android-11/ Reference]

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

Re: [tor-bugs] #32179 [Internal Services/Tor Sysadmin Team]: retire orestis

[Tor Bug Tracker & Wiki]

#32179: retire orestis
-+-
 Reporter:  weasel   |  Owner:  weasel
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #31659   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 removed from source code, spreadsheet, what's left:

  1. remove from tor-passwords
  2. remove from LDAP
  3. retire actual data (./retire in tsa-misc and retire at sunet)

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

Re: [tor-bugs] #34306 [Internal Services/Tor Sysadmin Team]: retire omeiense

[Tor Bug Tracker & Wiki]

#34306: retire omeiense
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #31659   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 removed from source code, spreadsheet, what's left:

  1. remove from tor-passwords
  2. remove from LDAP
  3. retire actual data (./retire in tsa-misc)

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

Re: [tor-bugs] #34267 [Circumvention/Snowflake]: Compiling the WebRTC Google library.

[Tor Bug Tracker & Wiki]

#34267: Compiling the WebRTC Google library.
-+--
 Reporter:  HashikD  |  Owner:  (none)
 Type:  task | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-mobile |  Actual Points:
Parent ID:   | Points:
 Reviewer:  cohosh   |Sponsor:
-+--
Changes (by cohosh):

 * status:  merge_ready => needs_review
 * reviewer:   => cohosh


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

Re: [tor-bugs] #32179 [Internal Services/Tor Sysadmin Team]: retire orestis

[Tor Bug Tracker & Wiki]

#32179: retire orestis
-+-
 Reporter:  weasel   |  Owner:  weasel
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #31659   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 already shutdown, removed from nagios and puppet

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

Re: [tor-bugs] #34306 [Internal Services/Tor Sysadmin Team]: retire omeiense

[Tor Bug Tracker & Wiki]

#34306: retire omeiense
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #31659   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 already shutdown, removed from nagios and puppet

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

Re: [tor-bugs] #34267 [Circumvention/Snowflake]: Compiling the WebRTC Google library.

[Tor Bug Tracker & Wiki]

#34267: Compiling the WebRTC Google library.
-+-
 Reporter:  HashikD  |  Owner:  (none)
 Type:  task | Status:  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-mobile |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by HashikD):

 * status:  new => merge_ready


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

Re: [tor-bugs] #34267 [Circumvention/Snowflake]: Compiling the WebRTC Google library.

[Tor Bug Tracker & Wiki]

#34267: Compiling the WebRTC Google library.
-+
 Reporter:  HashikD  |  Owner:  (none)
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-mobile |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by HashikD):

 It is not necessary to compile the WebRTC library any more since Google is
 officially making WebRTC available through Gradle, precompiled which is
 compatible with Android. [https://bintray.com/google/webrtc/google-webrtc
 Precompile library.]

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #34306 [Internal Services/Tor Sysadmin Team]: retire omeiense

[Tor Bug Tracker & Wiki]

#34306: retire omeiense
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin   |Version:
  Team   |
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:  #31659
   Points:   |   Reviewer:
  Sponsor:   |
-+-


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

Re: [tor-bugs] #34134 [Internal Services/Tor Sysadmin Team]: yahoo hates tor-announce mails: "User is receiving mail too quickly"

[Tor Bug Tracker & Wiki]

#34134: yahoo hates tor-announce mails: "User is receiving mail too quickly"
-+-
 Reporter:  arma |  Owner:  tpa
 Type:  enhancement  | 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):

 another, similar approach:

 {{{
 /yahoo(\.[a-z]{2,3}){1,2}$/  hotmail:
 # hotmail crap
 /hotmail(\.[a-z]{2,3}){1,2}$/  hotmail:
 /live(\.[a-z]{2,3}){1,2}$/  hotmail:
 /outlook(\.[a-z]{2,3}){1,2}$/  hotmail:
 }}}

 {{{
 notsopolite_initial_destination_concurrency = 2
 notsopolite_destination_recipient_limit = 200
 notsopolite_destination_concurrency_limit = 10
 notsopolite_destination_rate_delay = 2

 polite_initial_destination_concurrency = 2
 polite_destination_recipient_limit = 20
 polite_destination_concurrency_limit = 10
 polite_destination_rate_delay = 3

 megamailservers_destination_concurrency_failed_cohort_limit = 100
 megamailservers_destination_recipient_limit = 2
 megamailservers_destination_concurrency_limit = 4
 megamailservers_destination_rate_delay = 5

 hotmail_initial_destination_concurrency = 2
 hotmail_destination_recipient_limit = 20
 hotmail_destination_concurrency_limit = 10
 hotmail_destination_rate_delay = 3

 slow_initial_destination_concurrency = 1
 # tolerate more errors before considering destination as failed
 slow_destination_concurrency_failed_cohort_limit = 100
 slow_destination_recipient_limit = 2
 slow_destination_concurrency_limit = 4
 slow_destination_rate_delay = 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] #32802 [Internal Services/Tor Sysadmin Team]: retire kvm4, 8 VMs to migrate

[Tor Bug Tracker & Wiki]

#32802: retire kvm4, 8 VMs to migrate
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  project  | Status:
 |  accepted
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Major| Resolution:
 Keywords:  tpa-roadmap-may  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Old description:

> kvm4 is getting fairly old. it's been setup in 2015 and is showing sign
> of old age. for example today it freaked us all out by not returning
> after a reboot right before the holidays (#32801). considering how
> critical that server is (email, puppet, ldap, jenkins, dns, web mirror,
> all the windows buildboxes!) we should start considering a
> decomissionning process.
>
> at the very least, we need to get eugeni the heck out of there.
>
> we have budget to provision another ganeti cluster, so let's use it to
> replace this, and hopefully more. the existing cluster has already taken
> more than its share by taking machines from both kvm1/textile and moly,
> so it's time we provision more hardware for this.
>
> this requires a new ganeti node (fsn-node-06, #33907).
>
> machines to be migrated:
>
>  * [x] alberti.torproject.org (LDAP) #33908
>  * [/] build-x86-09.torproject.org (build server) - RETIRE - replaced
> with build-x86-11 on gnt-fsn
>  * [x] eugeni.torproject.org (email) #32803
>  * [x] meronense.torproject.org (metrics) #33909
>  * [x] neriniflorum.torproject.org (DNS) #33910
>  * [ ] oo-hetzner-03.torproject.org (metrics) #33911
>  * [x] pauli.torproject.org (puppet) #33912
>  * [x] rouyi.torproject.org (jenkins) #33913
>  * [x] web-hetzner-01.torproject.org (static mirror) RETIRE
>  * [x] weissii.torproject.org (windows build box) #33914
>  * [ ] winklerianum.torproject.org (windows build box) turned off,
> RETIRE?
>  * [ ] woronowii.torproject.org (windows build box) turned off, RETIRE?

New description:

 kvm4 is getting fairly old. it's been setup in 2015 and is showing sign of
 old age. for example today it freaked us all out by not returning after a
 reboot right before the holidays (#32801). considering how critical that
 server is (email, puppet, ldap, jenkins, dns, web mirror, all the windows
 buildboxes!) we should start considering a decomissionning process.

 at the very least, we need to get eugeni the heck out of there.

 we have budget to provision another ganeti cluster, so let's use it to
 replace this, and hopefully more. the existing cluster has already taken
 more than its share by taking machines from both kvm1/textile and moly, so
 it's time we provision more hardware for this.

 this requires a new ganeti node (fsn-node-06, #33907).

 machines to be migrated:

  * [x] alberti.torproject.org (LDAP) #33908
  * [x] build-x86-09.torproject.org (build server) - RETIRE - replaced with
 build-x86-11 on gnt-fsn
  * [x] eugeni.torproject.org (email) #32803
  * [x] meronense.torproject.org (metrics) #33909
  * [x] neriniflorum.torproject.org (DNS) #33910
  * [x] oo-hetzner-03.torproject.org (metrics) #33911
  * [x] pauli.torproject.org (puppet) #33912
  * [x] rouyi.torproject.org (jenkins) #33913
  * [x] web-hetzner-01.torproject.org (static mirror) RETIRE
  * [x] weissii.torproject.org (windows build box) #33914
  * [x] winklerianum.torproject.org (windows build box) turned off,
 migrated along weissii, but turned off
  * [x] woronowii.torproject.org (windows build box) turned off, migrated
 along weissii, but turned off

--

Comment (by anarcat):

 i just retired oo-hetzner-03, the next step here is to retire kvm4 itself,
 it seems.

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

Re: [tor-bugs] #34305 [Applications/Tor Browser]: NoScript inconsistent behaviour in Firefox 77 (currently beta)

[Tor Bug Tracker & Wiki]

#34305: NoScript inconsistent behaviour in Firefox 77 (currently beta)
-+-
 Reporter:  acat |  Owner:  acat
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  noscript TorBrowserTeam202005,   |  Actual Points:
  ff78-esr   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by acat):

 * status:  assigned => needs_information


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

Re: [tor-bugs] #33911 [Internal Services/Tor Sysadmin Team]: oo-hetzner-03 retirement

[Tor Bug Tracker & Wiki]

#33911: oo-hetzner-03 retirement
-+-
 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):

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


Comment:

 1. done as part of #31659
  2. removed from nagios
  3. already stopped
  4. ran `./retire -v -H oo-hetzner-03.torproject.org retire-all --parent-
 host=kvm4.torproject.org`, which: undefined the host, scheduled deleting
 on kvm4, scheduled backup removal in 30 days, revoked from puppet:
 {{{
 $ ./retire -v -H oo-hetzner-03.torproject.org retire-all --parent-
 host=kvm4.torproject.org
 starting tasks at 2020-05-25 11:24:58.481377
 checking for ganeti master on host kvm4.torproject.org
 instance oo-hetzner-03.torproject.org not running, no shutdown required
 undefining instance oo-hetzner-03.torproject.org on host
 kvm4.torproject.org
 Domain oo-hetzner-03.torproject.org has been undefined

 scheduling oo-hetzner-03.torproject.org disk deletion on host
 kvm4.torproject.org
 checking for path "/srv/vmstore/oo-hetzner-03.torproject.org/" on
 kvm4.torproject.org
 scheduling rm -rf "/srv/vmstore/oo-hetzner-03.torproject.org/" to run on
 kvm4.torproject.org in 7 days
 warning: commands will be executed using /bin/sh
 job 5 at Mon Jun  1 15:25:00 2020
 scheduling oo-hetzner-03.torproject.org backup disks removal on host
 bungei.torproject.org
 checking for path "/srv/backups/bacula/oo-hetzner-03.torproject.org/" on
 bungei.torproject.org
 scheduling rm -rf "/srv/backups/bacula/oo-hetzner-03.torproject.org/" to
 run on bungei.torproject.org in 30 days
 warning: commands will be executed using /bin/sh
 job 30 at Wed Jun 24 15:25:00 2020
 Notice: Revoked certificate with serial 53
 Notice: Removing file Puppet::SSL::Certificate oo-
 hetzner-03.torproject.org at '/var/lib/puppet/ssl/ca/signed/oo-
 hetzner-03.torproject.org.pem'
 oo-hetzner-03.torproject.org
 Submitted 'deactivate node' for oo-hetzner-03.torproject.org with UUID
 cc3ae307-0abe-445d-9795-4edc49198bc5
 completed tasks, elasped: 0:00:15.307500 (user 4.66 system 0.14 chlduser
 0.03 chldsystem 0.05 RSS 43.2 MB)
 }}}
  5. deleted this blob from LDAP:
 {{{
 383 host=oo-hetzner-03,ou=hosts,dc=torproject,dc=org
 host: oo-hetzner-03
 hostname: oo-hetzner-03.torproject.org
 objectClass: top
 objectClass: debianServer
 l: Falkenstein, Saxony, Germany
 distribution: Debian
 access: restricted
 admin: torproject-ad...@torproject.org
 architecture: amd64
 sshRSAHostKey: ssh-rsa
 
B3NzaC1yc2EDAQABAAABAQDNLYaiN/+rbaDxU3ng1PE18TFwACbrph/0rBJVPsbJJJZt8QJ8JmkRYaOdEtR/BaT1lsyFAi+oLGbqqdAZ2WXfz6p292qs3zT+JnkkDaYmh3v3i2m7eJsDTegL9agsM7RFHNyiEYilRDzIdVA9h2Rl+mKnMe/cd+qDzK93JFcTc0F1nbgPIE4OrPPCZ+85/OJEDEkNHzRFzuFbcAf6XXGQJlEvGrETBAAyV28BeAY07V7Kyp9Pd5fIJn4wCqWqH7RMTMFTLbLg7d8B9BLHNwwXYeUEn4+zZA8pWL59s9uhnRDXJS7+yTvBG81YizwJryYSfe2G4bWLThPdKywHcq2f
 root@oo-hetzner-03
 sshRSAHostKey: ssh-ed25519
 C3NzaC1lZDI1NTE5IGU3yePQ+5QjfGqqjr7Fa7t+FGPiVMvaheQRxRRMhF3E root
 @oo-hetzner-03
 physicalHost: kvm4.torproject.org
 ipHostNumber: 94.130.28.199
 ipHostNumber: 2a01:4f8:10b:239f:0:ab4:199:1
 allowedGroups: onionoo
 allowedGroups: onionoo-unpriv
 description: onionoo
 purpose: onionoo.torproject.org
 rebootPolicy: rotation
 }}}

  6. removed from source code (mostly nagios, but also in the buster
 upgrade notes!)
  7. removed from tor-passwords
  8. N/A DNSwl
  9. remove from spreadsheet
  10. N/A
  11. N/A will be purged along with kvm4

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

Re: [tor-bugs] #34305 [Applications/Tor Browser]: NoScript inconsistent behaviour in Firefox 77 (currently beta)

[Tor Bug Tracker & Wiki]

#34305: NoScript inconsistent behaviour in Firefox 77 (currently beta)
-+-
 Reporter:  acat |  Owner:  acat
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  noscript TorBrowserTeam202005,   |  Actual Points:
  ff78-esr   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by acat):

 * status:  needs_information => assigned
 * cc: tbb-team (added)
 * 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] #34305 [Applications/Tor Browser]: NoScript inconsistent behaviour in Firefox 77 (currently beta)

[Tor Bug Tracker & Wiki]

#34305: NoScript inconsistent behaviour in Firefox 77 (currently beta)
-+-
 Reporter:  acat |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  noscript TorBrowserTeam202005,   |  Actual Points:
  ff78-esr   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  noscript TorBrowserTeam202005 => noscript
 TorBrowserTeam202005, ff78-esr


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

Re: [tor-bugs] #34305 [Applications/Tor Browser]: NoScript inconsistent behaviour in Firefox 77 (currently beta)

[Tor Bug Tracker & Wiki]

#34305: NoScript inconsistent behaviour in Firefox 77 (currently beta)
---+---
 Reporter:  acat   |  Owner:  tbb-team
 Type:  defect | Status:
   |  needs_information
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  noscript TorBrowserTeam202005  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by gk):

 * keywords:  noscript TorBrowserTeam201905 => noscript TorBrowserTeam202005


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

Re: [tor-bugs] #34305 [Applications/Tor Browser]: NoScript inconsistent behaviour in Firefox 77 (currently beta)

[Tor Bug Tracker & Wiki]

#34305: NoScript inconsistent behaviour in Firefox 77 (currently beta)
---+---
 Reporter:  acat   |  Owner:  tbb-team
 Type:  defect | Status:
   |  needs_information
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  noscript TorBrowserTeam201905  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by acat):

 * cc: ma1 (added)
 * keywords:  noscript => noscript TorBrowserTeam201905
 * status:  new => needs_information


Comment:

 I bisected the issue down to
 https://bugzilla.mozilla.org/show_bug.cgi?id=1462989. Without that change,
 I cannot reproduce the bug. Of course, the underlying problem might be
 different, but at least it looks like that change exposed this.

 ma1, could you please confirm this is a Firefox issue and not a NoScript
 one (which by some reason got exposed by
 https://bugzilla.mozilla.org/show_bug.cgi?id=1462989)? If so, I think we
 should file a bugzilla ticket for this.

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

Re: [tor-bugs] #33111 [Metrics]: upgrade all metrics hosts to Debian buster

[Tor Bug Tracker & Wiki]

#33111: upgrade all metrics hosts to Debian buster
-+--
 Reporter:  anarcat  |  Owner:  metrics-team
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Old description:

> We (TPA) want to upgrade all Torproject.org machines from Debian
> 9/stretch ("oldstable") to 10/buster ("stable") by the time the
> "oldstable" release becomes end of life (EOL). This is expected to
> happen somewhere around july 2020, this summer.
>
> Your team is responsible for these machines relevant for this
> transition, which are currently running Debian stretch:
>
>  * colchicifolium
>  * corsicum
>  * materculae
>  * omeiense
>  * oo-hetzner-03
>  * orestis
>
> Would you please review the changes expected to happen during the
> upgrade? You can see a summary of major package changes here:
>
> ​https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-
> new.en.html#newdistro
>
> and here:
>
> ​https://help.torproject.org/tsa/howto/upgrades/buster/#Notable_changes
>
> Let us know if you need an advance notice before we perform the upgrade,
> and how long it should be. If you need assistance or coordination, also
> do let us know.
>
> Otherwise the upgrade can proceed at any time and will be performed
> before summer.
>
> (In this specific case, I'm wondering if there are some boxes that we
> should decomission. In particular, there seems to be a lot of onionoo
> boxes in the fleet right now, with more under way (#32268). What's the
> plan for those? Should we upgrade the older boxes or phase them out when
> the new cluster is online?)
>
> Thanks!

New description:

 We (TPA) want to upgrade all Torproject.org machines from Debian
 9/stretch ("oldstable") to 10/buster ("stable") by the time the
 "oldstable" release becomes end of life (EOL). This is expected to
 happen somewhere around july 2020, this summer.

 Your team is responsible for these machines relevant for this
 transition, which are currently running Debian stretch:

  * colchicifolium
  * corsicum
  * materculae
  * omeiense
  * ~~oo-hetzner-03~~
  * orestis

 Would you please review the changes expected to happen during the
 upgrade? You can see a summary of major package changes here:

 ​https://www.debian.org/releases/buster/amd64/release-notes/ch-whats-
 new.en.html#newdistro

 and here:

 ​https://help.torproject.org/tsa/howto/upgrades/buster/#Notable_changes

 Let us know if you need an advance notice before we perform the upgrade,
 and how long it should be. If you need assistance or coordination, also
 do let us know.

 Otherwise the upgrade can proceed at any time and will be performed
 before summer.

 (In this specific case, I'm wondering if there are some boxes that we
 should decomission. In particular, there seems to be a lot of onionoo
 boxes in the fleet right now, with more under way (#32268). What's the
 plan for those? Should we upgrade the older boxes or phase them out when
 the new cluster is online?)

 Thanks!

--

Comment (by anarcat):

 oo-hetzner-03 is being retired, so that's 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

[tor-bugs] #34305 [Applications/Tor Browser]: NoScript inconsistent behaviour in Firefox 77 (currently beta)

[Tor Bug Tracker & Wiki]

#34305: NoScript inconsistent behaviour in Firefox 77 (currently beta)
--+--
 Reporter:  acat  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  noscript
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 While working on fixing the testsuite (#27105) I ran into some
 inconsistent blocking behaviour of NoScript in a Tor Browser WIP build
 based on Firefox 77 beta.

 Basically, the issue is that with Tor Browser `Safer` NoScript
 configuration when visiting a `http:` page (containing a https: iframe)
 and then going to the `https:` version of the same page results in
 JavaScript being blocked, but it should not be. Manually reloading the
 `https:` page results in JavaScript being executed correctly.

 After some effort, I managed to reproduce in current Firefox 77 beta
 directly, more specifically:
 `f2e0df68e569b43ca337535927ed63068ed01c664eea7e397378cae668f63d0a
 firefox-77.0b9.tar.bz2`. Tested with NoScript 11.0.26 and 11.0.25.

 Steps to reproduce (in a fresh profile):

 - Install NoScript addon.

 - Go to NoScript options page (either via about:addons or via NoScript
 toolbar badge).

 - Enable "script" option and "Cascade top document's restrictions to
 subdocuments" in the General + Default tab.

 - Still in General, go to "UNTRUSTED" and enable "frame".

 - Go to "Per-site permission" tab and add a new rule: "http:" and mark it
 as "untrusted" (basically, setting non-https pages as untrusted).

 - Open a new tab and visit http://alltaken.xyz/https_iframe.html

 - When loaded, open a new tab and visit
 https://alltaken.xyz/https_iframe.html

 - Result: JavaScript is blocked, but it should not be. When the page is
 manually reloaded (press F5), the script is executed correctly, and the
 `JavaScriptEnabled` text is displayed.

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

Re: [tor-bugs] #33911 [Internal Services/Tor Sysadmin Team]: oo-hetzner-03 retirement

[Tor Bug Tracker & Wiki]

#33911: oo-hetzner-03 retirement
-+-
 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:  #32802   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * status:  assigned => 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] #34023 [Metrics/Onionperf]: Reduce the number of 50 KiB downloads

[Tor Bug Tracker & Wiki]

#34023: Reduce the number of 50 KiB downloads
---+
 Reporter:  karsten|  Owner:  karsten
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:  implemented
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.3
Parent ID:  #33321 | Points:  1.0
 Reviewer: |Sponsor:  Sponsor59-must
---+
Changes (by karsten):

 * status:  needs_review => closed
 * points:  1 => 1.0
 * resolution:   => implemented
 * actualpoints:   => 0.3


Comment:

 I just merged this together with the other two commits in that branch. And
 in retrospect, this patch didn't need review as badly anyway. 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] #34286 [Applications/GetTor]: gettor appears to be in an email loop war with a .sk address

[Tor Bug Tracker & Wiki]

#34286: gettor appears to be in an email loop war with a .sk address
-+--
 Reporter:  arma |  Owner:  cohosh
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/GetTor  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:  phw  |Sponsor:
-+--
Changes (by cohosh):

 * status:  assigned => needs_review


Comment:

 Okay here's another patch that should be more complete:
 https://gitlab.torproject.org/torproject/anti-censorship/gettor-
 project/gettor/-/merge_requests/11

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: 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:  karsten
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:  implemented
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.2
Parent ID:  #33321 | Points:  1
 Reviewer:  acute  |Sponsor:  Sponsor59-must
---+
Changes (by karsten):

 * status:  merge_ready => closed
 * resolution:   => implemented
 * actualpoints:  0.1 => 0.2


Comment:

 Thanks for the review! Pushed to master, adding my 0.1 actual points, 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] #33434 [Metrics/Onionperf]: Allow users to select Onion Service version to measure

[Tor Bug Tracker & Wiki]

#33434: Allow users to select Onion Service version to measure
---+
 Reporter:  acute  |  Owner:  karsten
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:  implemented
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:  0.3
Parent ID:  #33321 | Points:  0.5
 Reviewer:  phw|Sponsor:  Sponsor59-must
---+
Changes (by karsten):

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


Comment:

 Thanks for the review! Pushed to master, followed by
 
[https://gitweb.torproject.org/onionperf.git/commit/?id=b42512fec5fc8263d546e10b1948a3d28f156f37
 commit b42512f] to update the documentation as pointed out above. 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] #34134 [Internal Services/Tor Sysadmin Team]: yahoo hates tor-announce mails: "User is receiving mail too quickly"

[Tor Bug Tracker & Wiki]

#34134: yahoo hates tor-announce mails: "User is receiving mail too quickly"
-+-
 Reporter:  arma |  Owner:  tpa
 Type:  enhancement  | 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):

 one thing we could try would be to setup a different transport for hosts.
 this would be, for example, in `master.cf`:

 {{{
 smtp-extradelay unix --n-1smtp -o syslog_name=smtp-
 extradelay
 }}}

 in `transport`:

 {{{
 ymail.com   smtp-extradelay:
 yahoo.com   smtp-extradelay:
 yahoo.co.uk smtp-extradelay:
 yahoo.grsmtp-extradelay:
 }}}

 and in `main.cf`:

 {{{
 smtp-extradelay_destination_rate_delay = 10s
 smtp-extradelay_destination_concurrency_limit = 1
 smtp-extradelay_destination_recipient_limit = 1
 smtp-extradelay_initial_destination_concurrency=1
 }}}

 different policies could be set that way. i'll check with my old job, we
 did setup something like this as well, now that i think of 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] #30611 [Metrics/Website]: Include partial download times in Time to complete request graphs

[Tor Bug Tracker & Wiki]

#30611: Include partial download times in Time to complete request graphs
-+-
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:  implemented
 Keywords:   |  Actual Points:  0.6
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by karsten):

 * status:  accepted => closed
 * resolution:   => implemented
 * actualpoints:   => 0.6


Comment:

 Implemented in [https://gitweb.torproject.org/metrics-
 web.git/commit/?id=110cb010bd29b24902b62273b96566bf086da270 ​commit
 110cb01], pushed to master, and deployed on the server. 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] #34304 [Internal Services/Tor Sysadmin Team]: new gnt-fsn node (fsn-node-07)

[Tor Bug Tracker & Wiki]

#34304: new gnt-fsn node (fsn-node-07)
-+-
 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):

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


Comment:

 i ordered the box from hetzner, ETA 12-14 days, by which time kvm4 will
 probably be retired.

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

Re: [tor-bugs] #34302 [Metrics/Website]: Include version 3 onion service measurements in all performance graphs

[Tor Bug Tracker & Wiki]

#34302: Include version 3 onion service measurements in all performance graphs
-+-
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:  implemented
 Keywords:   |  Actual Points:  0.1
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by karsten):

 * status:  assigned => closed
 * resolution:   => implemented
 * actualpoints:   => 0.1


Comment:

 Implemented in [https://gitweb.torproject.org/metrics-
 web.git/commit/?id=575741e33edcdd6085628b1c56140c84f49cc196 commit
 575741e] (with wrong ticket number in the commit message--oops!), pushed
 to master, and deployed on the server. 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

[tor-bugs] #34304 [Internal Services/Tor Sysadmin Team]: new gnt-fsn node (fsn-node-07)

[Tor Bug Tracker & Wiki]

#34304: new gnt-fsn node (fsn-node-07)
-+-
 Reporter:  anarcat  |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin   |Version:
  Team   |   Keywords:  tpa-
 Severity:  Normal   |  roadmap-may
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 need to create one last ganeti node to replace kvm5 (#33084)

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

Re: [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:  acute
 Type:  enhancement| Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #33321 | Points:  0.5
 Reviewer: |Sponsor:  Sponsor59-must
---+
Changes (by acute):

 * status:  new => accepted
 * owner:  metrics-team => acute


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

[tor-bugs] [Tor Bug Tracker & Wiki] Batch modify: #34263, #34264, #34265, #34266, ...

[Tor Bug Tracker & Wiki]

Batch modification to #34263, #34264, #34265, #34266, #34267, #34268, #34269, 
#34270, #34271, #34272, #34273, #34274, #34275, #34276, #34277, #34278, #34279, 
#34280, #34281, #34282, #34283 by cohosh:


--
Tickets URL: 

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

Re: [tor-bugs] #33911 [Internal Services/Tor Sysadmin Team]: oo-hetzner-03 retirement (was: oo-hetzner-03 IP address change planned for Ganeti migration)

[Tor Bug Tracker & Wiki]

#33911: oo-hetzner-03 retirement
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tpa-roadmap-may  |  Actual Points:
Parent ID:  #32802   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 new onionoo infra was setup in #31659, this this host will actually just
 be retired.

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

Re: [tor-bugs] #34303 [Metrics/Onionperf]: Find out why onion service measurements have gotten slower

[Tor Bug Tracker & Wiki]

#34303: Find out why onion service measurements have gotten slower
---+
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  Sponsor59-must
---+
Changes (by karsten):

 * cc: asn (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] [Tor Bug Tracker & Wiki] Batch modify: #32803, #33908, #33909, #33910, ...

[Tor Bug Tracker & Wiki]

Batch modification to #32803, #33908, #33909, #33910, #33912, #33914 by anarcat:


Action: resolve

--
Tickets URL: 

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

[tor-bugs] [Tor Bug Tracker & Wiki] Batch modify: #32803, #33908, #33909, #33910, ...

[Tor Bug Tracker & Wiki]

Batch modification to #32803, #33908, #33909, #33910, #33912, #33914 by anarcat:


Action: reassign

--
Tickets URL: 

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

[tor-bugs] [Tor Bug Tracker & Wiki] Batch modify: #32803, #33908, #33909, #33910, ...

[Tor Bug Tracker & Wiki]

Batch modification to #32803, #33908, #33909, #33910, #33912, #33914 by anarcat:


Action: reopen

Comment:
reassigning to weasel, who did all that work

--
Tickets URL: 

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

Re: [tor-bugs] #34303 [Metrics/Onionperf]: Find out why onion service measurements have gotten slower

[Tor Bug Tracker & Wiki]

#34303: Find out why onion service measurements have gotten slower
---+
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  Sponsor59-must
---+

Comment (by karsten):

 Regarding my confidence in these graphs, I found comparable numbers in the
 [https://trac.torproject.org/projects/tor/ticket/33434#comment:4 graphs
 attached to #33434], just without a comparison to the earlier OnionPerf
 instances, which is why these high numbers didn't stand out. However, not
 ruling out that I made a mistake in those graphs, too.

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

Re: [tor-bugs] #34303 [Metrics/Onionperf]: Find out why onion service measurements have gotten slower

[Tor Bug Tracker & Wiki]

#34303: Find out why onion service measurements have gotten slower
---+
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  Sponsor59-must
---+

Comment (by karsten):

 [[Image(torperf-onion-2020-02-25-2020-05-25-50kb.png, 700px)]]

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

Re: [tor-bugs] #34303 [Metrics/Onionperf]: Find out why onion service measurements have gotten slower

[Tor Bug Tracker & Wiki]

#34303: Find out why onion service measurements have gotten slower
---+
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  Sponsor59-must
---+
Changes (by karsten):

 * Attachment "torperf-onion-2020-02-25-2020-05-25-50kb.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] #34303 [Metrics/Onionperf]: Find out why onion service measurements have gotten slower

[Tor Bug Tracker & Wiki]

#34303: Find out why onion service measurements have gotten slower
---+--
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor:  Sponsor59-must |
---+--
 Today I changed the [https://metrics.torproject.org/torperf.html "Time to
 download files over Tor" graph] to include version 3 onion service
 measurements.

 By chance, I also looked at the
 
[https://metrics.torproject.org/torperf.html?start=2020-02-25=2020-05-25=onion=50kb
 onion server measurements] and found that the onion service measurements
 made by op-nl2, op-us2, and op-hk2 have gotten much slower as compared to
 their op-nl, op-us, and op-hk predecessors.

 I'm 95% certain that this is not a bug in the graphs.

 My current best guess is that something in `tor` has changed. I'd like to
 set up a small number of experimental OnionPerf instances all in the same
 place but with different `tor` versions. Any suggestions on locations
 (Amsterdam, Florida, Hong Kong) or `tor` versions?

 This is also relevant to Sponsor 59 in order to make sure that our current
 measurements are going to be a baseline for future experiments.
 Classifying as potential defect.

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

Re: [tor-bugs] #34257 [Metrics/Onionperf]: Analyze unusual distribution of time to extend to first hop in circuit

[Tor Bug Tracker & Wiki]

#34257: Analyze unusual distribution of time to extend to first hop in circuit
---+
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  Sponsor59-must
---+

Comment (by karsten):

 Not an answer to the questions, but some additional information: The
 experimental Hong Kong instance only measures onion service, because I
 didn't want to mess with firewalls. You might need to take that into
 account by comparing the numbers to onion service results from the other
 instances. I can't say whether that makes a difference.

 Additionally, the experimental instance only downloads 5 MiB files. That
 very likely doesn't matter here, but it might turn out to be useful if we
 compare fb2lb (first byte to last byte) of these few days to the two weeks
 of existing measurements from the other instances.

 Bug in OnionPerf? What do you mean, eh? ;) (Thanks for digging into this!)

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

Re: [tor-bugs] #34285 [Internal Services/Tor Sysadmin Team]: mit.edu is rejecting mail from eugeni

[Tor Bug Tracker & Wiki]

#34285: mit.edu is rejecting mail from eugeni
-+
 Reporter:  arma |  Owner:  tpa
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by anarcat):

 i think we can followup in #34134

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

Re: [tor-bugs] #34257 [Metrics/Onionperf]: Analyze unusual distribution of time to extend to first hop in circuit

[Tor Bug Tracker & Wiki]

#34257: Analyze unusual distribution of time to extend to first hop in circuit
---+
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  Sponsor59-must
---+

Comment (by dennis.jackson):

 Okay, this extra data is pretty helpful!

 Looking at the Histograms for `req2fb` they are look consistent:
 [https://github.com/galadran/onionperf-guard-
 analysis/blob/master/images/histograms/req2fb_ip-172-31-5-27.png 1],
 [https://github.com/galadran/onionperf-guard-
 analysis/blob/master/images/histograms/req2fb_op-hk2.png 2],
 [https://github.com/galadran/onionperf-guard-
 analysis/blob/master/images/histograms/req2fb_op-nl2.png 3],
 [https://github.com/galadran/onionperf-guard-
 analysis/blob/master/images/histograms/req2fb_op-us2.png 4]. So I would
 guess the actual circuits are performing reasonably similarly once built.

 Looking at the Histograms for `start2req` shows a very different pattern
 for each region. The distribution is offset roughly in proportion to the
 offset observed in the `bt1` distribution, but scaled up:
 [[Image(https://raw.githubusercontent.com/galadran/onionperf-guard-
 analysis/master/images/histograms/start2req_op-nl2.png, width=70%)]]
 [[Image(https://raw.githubusercontent.com/galadran/onionperf-guard-
 analysis/master/images/histograms/start2req_op-us2.png, width=70%)]]
 [[Image(https://raw.githubusercontent.com/galadran/onionperf-guard-
 analysis/master/images/histograms/start2req_op-hk2.png, width=70%)]]
 [[Image(https://raw.githubusercontent.com/galadran/onionperf-guard-
 analysis/master/images/histograms/start2req_ip-172-31-5-27.png,
 width=70%)]].
 I think the spikes in the last graph are just an artefact of the lower
 sample count, but it is pretty interesting that this is the only graph
 without a peak around 0.

 Why does the new Hong Kong node not see very fast circuit build times? Why
 does the time between initiation and success vary on geographic region in
 the same pattern as the first extension, but scaled up? It can't be caused
 purely by the `bt1` offset, because that is only on the order of ~1 second
 rather than ~8 seconds.

 I wonder if there is a bug in Onionperf? Some kind of race condition /
 incorrect mapping between requests and successful circuit builds? I'll try
 to find some time to sit down with the raw files.

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

Re: [tor-bugs] #32179 [Internal Services/Tor Sysadmin Team]: retire orestis (was: move orestis to be a new-style onionoo frontend)

[Tor Bug Tracker & Wiki]

#32179: retire orestis
-+-
 Reporter:  weasel   |  Owner:  weasel
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #31659   | Points:
 Reviewer:   |Sponsor:
-+-

Old description:

> this is an (old-style) onionoo frontend going only to the old backends.
> cf. #31659.

New description:

 this is an (old-style) onionoo frontend going only to the old backends.
 cf. #31659.

 onionoo-frontend-0[12] are perfectly able to handle the current load.  We
 can retire this instance.

--

Comment (by weasel):

 onionoo-frontend-0[12] are perfectly able to handle the current load.  We
 can retire this instance.

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

Re: [tor-bugs] #28325 [Applications/Tor Browser]: Use go 1.11 module versioning support

[Tor Bug Tracker & Wiki]

#28325: Use go 1.11 module versioning support
-+-
 Reporter:  boklm|  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-rbm, tbb-maint,  |  Actual Points:
  TorBrowserTeam202004   |
Parent ID:  #33659   | Points:  3
 Reviewer:  sysrqb   |Sponsor:
 |  Sponsor58
-+-
Changes (by gk):

 * keywords:  tbb-rbm, ReleaseTrainMigration, TorBrowserTeam202004 => tbb-
 rbm, tbb-maint, TorBrowserTeam202004


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

Re: [tor-bugs] #34257 [Metrics/Onionperf]: Analyze unusual distribution of time to extend to first hop in circuit

[Tor Bug Tracker & Wiki]

#34257: Analyze unusual distribution of time to extend to first hop in circuit
---+
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  Sponsor59-must
---+

Comment (by dgoulet):

 That is quite impressive results...

 So for some reasons, in the Netherlands, everything is the same time to
 extend to whatever hops but then it increases by a factor of 2 for US and
 then to some crazy values for HK... huh...

 If this was a problem within little-t tor, I would have expected to see
 the .nl with a longer latency as well

 The big difference I can see is that the first graph is `client -> relay`
 where the rest is `relay -> relay`.

 Suggestion: is there any chance you can run your Onionperf _from_ a relay
 IP just to rule out some sort of traffic shaping for `client->relay`
 versus `relay->relay` connection only based on the source IP? Then I think
 we might want, again if possible, try with `client->bridge`?

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

Re: [tor-bugs] #33433 [Metrics/Onionperf]: Add error handling for older stem versions

[Tor Bug Tracker & Wiki]

#33433: Add error handling for older stem versions
---+
 Reporter:  acute  |  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID:  #33321 | Points:  0.5
 Reviewer: |Sponsor:  Sponsor59-must
---+
Changes (by acute):

 * Attachment "0001-Adds-required-stem-version.patch" added.


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

Re: [tor-bugs] #33433 [Metrics/Onionperf]: Add error handling for older stem versions

[Tor Bug Tracker & Wiki]

#33433: Add error handling for older stem versions
---+
 Reporter:  acute  |  Owner:  metrics-team
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID:  #33321 | Points:  0.5
 Reviewer: |Sponsor:  Sponsor59-must
---+
Changes (by acute):

 * status:  new => needs_review


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

Re: [tor-bugs] #33433 [Metrics/Onionperf]: Add error handling for older stem versions

[Tor Bug Tracker & Wiki]

#33433: Add error handling for older stem versions
---+
 Reporter:  acute  |  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID:  #33321 | Points:  0.5
 Reviewer: |Sponsor:  Sponsor59-must
---+

Comment (by acute):

 It appears we already document the required stem version in README.md as
 1.7.0 - Attaching a patch to include this in requirements.txt

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

Re: [tor-bugs] #33433 [Metrics/Onionperf]: Add error handling for older stem versions

[Tor Bug Tracker & Wiki]

#33433: Add error handling for older stem versions
---+
 Reporter:  acute  |  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID:  #33321 | Points:  0.5
 Reviewer: |Sponsor:  Sponsor59-must
---+
Changes (by acute):

 * status:  needs_information => new


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

Re: [tor-bugs] #33433 [Metrics/Onionperf]: Add error handling for older stem versions

[Tor Bug Tracker & Wiki]

#33433: Add error handling for older stem versions
---+---
 Reporter:  acute  |  Owner:  metrics-team
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-team-roadmap-2020  |  Actual Points:
Parent ID:  #33321 | Points:  0.5
 Reviewer: |Sponsor:  Sponsor59-must
---+---

Comment (by acute):

 IIRC, this was an issue before Debian Buster, when the Stretch (now
 oldstable) distribution had `stem` version 1.5, and we had to install a
 newer version (1.7) from backports. I'd say it's very unlikely anyone
 would end up using this old a version when following our instructions on a
 Debian system now - perhaps we should just could a note in the
 documentation and optionally add a versioned dependency in
 `requirements.txt` (e.g `stem >= 1.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] #34257 [Metrics/Onionperf]: Analyze unusual distribution of time to extend to first hop in circuit

[Tor Bug Tracker & Wiki]

#34257: Analyze unusual distribution of time to extend to first hop in circuit
---+
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  Sponsor59-must
---+

Comment (by karsten):

 Here's an updated graph with the testing instance in another Hong Kong
 data center (labelled as ip-172-31-5-27):

 [[Image(onionperf-circuit-extend-2020-05-25.png, 700px)]]

 The updated CSV file is attached, and the logs and OnionPerf analysis
 files can be found in [https://people.torproject.org:~/karsten/op-hk-ec2
 -onionperf-data.tar.xz this tarball] (114M).

 This distribution of build times to the first relay looks unusual to me,
 too.

 Should I keep this new instance running? Right now it costs ~3 USD per
 day, so I'm happy to keep it running if we hope to learn something new
 from more data. But if we have enough data, I'll stop it for now. We can
 always set up a new instance to collect more or different data.

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

Re: [tor-bugs] #34257 [Metrics/Onionperf]: Analyze unusual distribution of time to extend to first hop in circuit

[Tor Bug Tracker & Wiki]

#34257: Analyze unusual distribution of time to extend to first hop in circuit
---+
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  Sponsor59-must
---+
Changes (by karsten):

 * Attachment "onionperf-circuit-extend-2020-05-25.csv.xz" 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] #34257 [Metrics/Onionperf]: Analyze unusual distribution of time to extend to first hop in circuit

[Tor Bug Tracker & Wiki]

#34257: Analyze unusual distribution of time to extend to first hop in circuit
---+
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Onionperf  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  Sponsor59-must
---+
Changes (by karsten):

 * Attachment "onionperf-circuit-extend-2020-05-25.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] #34302 [Metrics/Website]: Include version 3 onion service measurements in all performance graphs

[Tor Bug Tracker & Wiki]

#34302: Include version 3 onion service measurements in all performance graphs
-+--
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 In #33434 we found that the results of version 2 and version 3 onion
 service measurements are almost identical. But so far we're not plotting
 the version 3 measurements at all. We need to fix that, in particular due
 to version 2 measurements going away soon.

 I started working on a patch over the weekend that includes version 3
 onion service measurements in all performance graphs. I'll merge and
 deploy that today.

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

Re: [tor-bugs] #31659 [Internal Services/Tor Sysadmin Team]: new onionoo hosts

[Tor Bug Tracker & Wiki]

#31659: new onionoo hosts
-+-
 Reporter:  weasel   |  Owner:  tpa
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by weasel):

 oo-hetzner-03 and omeiense shut down (but not yet deleted/retired)

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

Re: [tor-bugs] #30610 [Metrics/Statistics]: Extend onionperf module to import new PARTIAL* and ERRORCODE fields

[Tor Bug Tracker & Wiki]

#30610: Extend onionperf module to import new PARTIAL* and ERRORCODE fields
+--
 Reporter:  karsten |  Owner:  metrics-team
 Type:  enhancement | Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:  duplicate
 Keywords:  |  Actual Points:
Parent ID:  #29507  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by karsten):

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


Comment:

 With #30612 being undecided, it's unlikely that we're graphing
 `ERRORCODE`s anytime soon. When we do, we should import the `ERRORCODE`
 field as part of that ticket.

 Importing the new `PARTIAL*` fields will be part of #30611. I'll work on
 that as part of that ticket.

 Closing as duplicate, because the actual work will be done on those other
 tickets.

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

Re: [tor-bugs] #30611 [Metrics/Website]: Include partial download times in Time to complete request graphs

[Tor Bug Tracker & Wiki]

#30611: Include partial download times in Time to complete request graphs
-+--
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * owner:  metrics-team => karsten
 * status:  new => accepted


Comment:

 I started working on this over the weekend and will merge and deploy a
 patch today.

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

[tor-bugs] #34301 [Applications/Tor Browser]: Fix shellcheck issues in our tor-browser-build scripts

[Tor Bug Tracker & Wiki]

#34301: Fix shellcheck issues in our tor-browser-build scripts
--+
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-rbm, tbb-maint
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 We add more and more shell scripts for different tasks into our `tor-
 browser-build` repo, which is great. We should go over the already
 existing ones and fix `shellcheck` issues.

 This is the parent ticket for that effort.

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