[tor-bugs] #31423 [Circumvention/Snowflake]: Improve building documentation

[Tor Bug Tracker & Wiki]

#31423: Improve building documentation
-+-
 Reporter:  serna|  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Component:
 |  Circumvention/Snowflake
  Version:   |   Severity:  Normal
 Keywords:  snowflake,   |  Actual Points:
  documentation  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
 In the snowflake monorepo it isn't clear which project does what.

 For example the server-webrtc's readme doesn't specify clearly what it is
 nor what it does, it also has some config and bash lines without much
 explanation of why.

 It would be useful to be more detailed in this kind of documentation for
 those interested in running a broker, snowflake/proxy or server.

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

Re: [tor-bugs] #29360 [Applications/Tor Browser]: Tor-Browser Linux: no audio playback (pulseaudio) on CentOS 6

[Tor Bug Tracker & Wiki]

#29360: Tor-Browser Linux: no audio playback (pulseaudio) on CentOS 6
--+---
 Reporter:  tries |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by arkadiy):

 Replying to [comment:11 dodonnell]:
 > > But my best guess to get around this would be to place a symlink to
 the .pulse directory in the real home directory - if this directory should
 exists in the users $HOME (similar to what has been done in #9353).
 >
 > I did this. But instead of symlinking the files, I copied them. As I
 sandbox the Tor browser process.
 The same problem on Debian bullseye/sid. Copying the files does no favor.

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

Re: [tor-bugs] #31027 [Core Tor/Tor]: Coverity: circpadding: dead code in circpad_machine_remove_token

[Tor Bug Tracker & Wiki]

#31027: Coverity: circpadding: dead code in  circpad_machine_remove_token
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  coverity  |  Actual Points:
Parent ID:| Points:
 Reviewer:  mikeperry |Sponsor:
--+
Changes (by mikeperry):

 * status:  needs_review => merge_ready


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] #31111 [Core Tor/Tor]: negotiate one machine per index

[Tor Bug Tracker & Wiki]

#3: negotiate one machine per index
--+
 Reporter:  pulls |  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.4.1.3-alpha
 Severity:  Normal| Resolution:
 Keywords:  wtf-pad   |  Actual Points:
Parent ID:| Points:
 Reviewer:  mikeperry |Sponsor:
--+
Changes (by mikeperry):

 * keywords:   => wtf-pad
 * status:  needs_review => 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] #31392 [Core Tor/Tor]: Explain Padding 1 and 2 in tor-spec.txt

[Tor Bug Tracker & Wiki]

#31392: Explain Padding 1 and 2 in tor-spec.txt
-+
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  merge_ready
 Priority:  Medium   |  Milestone:  Tor: 0.4.1.x-final
Component:  Core Tor/Tor |Version:  Tor: 0.4.0.5
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad, 041-should  |  Actual Points:
Parent ID:  #31356   | Points:  0.1
 Reviewer:  mikeperry|Sponsor:  Sponsor2
-+
Changes (by mikeperry):

 * status:  needs_review => merge_ready


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] #31376 [Circumvention/Snowflake]: Make a /metrics handle at the snowflake broker for the stats collector

[Tor Bug Tracker & Wiki]

#31376: Make a /metrics handle at the snowflake broker for the stats collector
-+---
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics, stats, broker   |  Actual Points:
Parent ID:   | Points:  1
 Reviewer:  phw  |Sponsor:  Sponsor28
-+---
Changes (by phw):

 * status:  needs_review => needs_information


Comment:

 I only had a
 
[https://github.com/cohosh/snowflake/commit/e0988a3612164ff6f2f160fcc87066a34666fe98#r34711453
 minor comment], which may or may not need a revision. Otherwise the patch
 looks good to me.

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

Re: [tor-bugs] #31422 [Circumvention/BridgeDB]: Make BridgeDB report internal metrics

[Tor Bug Tracker & Wiki]

#31422: Make BridgeDB report internal metrics
+---
 Reporter:  phw |  Owner:  (none)
 Type:  enhancement | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  metrics |  Actual Points:
Parent ID:  | Points:  2
 Reviewer:  |Sponsor:  Sponsor30-can
+---
Description changed by phw:

Old description:

> We're done with #9316, which means that we have code in place that allows
> BridgeDB to export metrics. So far, all metrics are user-centric, meaning
> that they focus on how BridgeDB users interact with the system. BridgeDB-
> centric metrics would help us debug and understand BridgeDB. The
> following come to mind:
>
> * Number of bridges per distribution ring.
> * Number of requests for which we had no bridges.
>
> We could also incorporate bridge assignments in our metrics, so we don't
> have to report them separately in the assignments.log file (see #29480).

New description:

 We're done with #9316, which means that we have code in place that allows
 BridgeDB to export metrics. So far, all metrics are user-centric, meaning
 that they focus on how BridgeDB users interact with the system. BridgeDB-
 centric metrics would help us debug and understand BridgeDB. The following
 come to mind:

 * Number of bridges per distribution ring.
 * Number of bridges per transport, similar to assignments.log (originally
 proposed in #14453)
 * Number of requests for which we had no bridges.

 We could also incorporate bridge assignments in our metrics, so we don't
 have to report them separately in the assignments.log file (see #29480).

--

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

Re: [tor-bugs] #14453 [Circumvention/BridgeDB]: Implement statistics gathering for number of Bridges-per-Transport in BridgeDB

[Tor Bug Tracker & Wiki]

#14453: Implement statistics gathering for number of Bridges-per-Transport in
BridgeDB
-+-
 Reporter:  isis |  Owner:  (none)
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-bridge, bridgedb, anti-  |  duplicate
  censorship-roadmap-august  |  Actual Points:
Parent ID:  #31274   | Points:  5
 Reviewer:   |Sponsor:
 |  Sponsor30-must
-+-
Changes (by phw):

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


Comment:

 I'm marking this as a duplicate because we can collect these statistics as
 part of our work for #31422. Basically, this can be just another BridgeDB-
 internal metric if I understand this ticket's description correctly.

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

Re: [tor-bugs] #29480 [Circumvention/BridgeDB]: Expose bridge pool assignments again

[Tor Bug Tracker & Wiki]

#29480: Expose bridge pool assignments again
+---
 Reporter:  irl |  Owner:  phw
 Type:  defect  | Status:  needs_information
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---
Changes (by phw):

 * status:  assigned => needs_information


Comment:

 Glancing at [https://collector.torproject.org/archive/bridge-pool-
 assignments/ archived bridge pool assignments], the format does not seem
 to have changed. #14082's description mentions that these files were once
 rsynced over to metrics. I'm happy to set up a cronjob on polyanthum to
 make that happen again.

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

Re: [tor-bugs] #22755 [Circumvention/BridgeDB]: Use stem to create test descriptors

[Tor Bug Tracker & Wiki]

#22755: Use stem to create test descriptors
-+-
 Reporter:  atagar   |  Owner:  phw
 Type:  enhancement  | Status:  closed
 Priority:  Low  |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Minor| Resolution:
 Keywords:  python, stem, bridgedb-parsers,  |  implemented
  bridgedb-ci|  Actual Points:  1
Parent ID:   | Points:  1
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30-can
-+-
Changes (by phw):

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


Comment:

 Replying to [comment:20 cohosh]:
 > Do we want to add a make clean step that removes the descriptors from
 the current directory?
 [[br]]
 Hmm, I don't think we should because our Makefile's clean target handles
 build artifacts that are created during installation. The test descriptors
 are only for testing, and not needed during installation.

 I just merged and deployed the branch.

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

Re: [tor-bugs] #30310 [Circumvention/Snowflake]: Snowflake localization

[Tor Bug Tracker & Wiki]

#30310: Snowflake localization
-+-
 Reporter:  cohosh   |  Owner:  arlolra
 Type:  task | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  l10n, snowflake-webextension, anti-  |  Actual Points:
  censorship-roadmap-august  |
Parent ID:   | Points:
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor28-can
-+-

Comment (by arlolra):

 > Nice, this looks good to merge what we have right now.

 Merged as,
 https://gitweb.torproject.org/pluggable-
 transports/snowflake.git/commit/?id=4e5a50f2b54db62991e4ce3313aa9b7f92a1c573

 > do we need to do something more for the proxy page?

 Yeah, here's a follow up for that,
 
https://github.com/keroserene/snowflake/commit/7bab95d1458859c94513b2e238858eb4f5e1cd69

 > I would like to add this file to our translation cycle, but I would like
 it to be on our repo first.

 This is now here,
 https://gitweb.torproject.org/pluggable-
 transports/snowflake.git/tree/proxy/static/_locales/en_US/messages.json

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

Re: [tor-bugs] #9316 [Circumvention/BridgeDB]: BridgeDB should export statistics

[Tor Bug Tracker & Wiki]

#9316: BridgeDB should export statistics
-+-
 Reporter:  asn  |  Owner:  phw
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics, bridgedb, prometheus,   |  implemented
  anti-censorship-roadmap-september  |  Actual Points:  2.3
Parent ID:  #31274   | Points:  3
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30-must
-+-
Changes (by phw):

 * actualpoints:   => 2.3


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

Re: [tor-bugs] #9316 [Circumvention/BridgeDB]: BridgeDB should export statistics

[Tor Bug Tracker & Wiki]

#9316: BridgeDB should export statistics
-+-
 Reporter:  asn  |  Owner:  phw
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics, bridgedb, prometheus,   |  implemented
  anti-censorship-roadmap-september  |  Actual Points:
Parent ID:  #31274   | Points:  3
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30-must
-+-
Changes (by phw):

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


Comment:

 Replying to [comment:35 cohosh]:
 > Thanks, this looks good to me!
 [[br]]
 Merged and deployed, thanks!

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

Re: [tor-bugs] #30310 [Circumvention/Snowflake]: Snowflake localization

[Tor Bug Tracker & Wiki]

#30310: Snowflake localization
-+-
 Reporter:  cohosh   |  Owner:  arlolra
 Type:  task | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  l10n, snowflake-webextension, anti-  |  Actual Points:
  censorship-roadmap-august  |
Parent ID:   | Points:
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor28-can
-+-
Changes (by cohosh):

 * status:  needs_review => merge_ready


Comment:

 Nice, this looks good to merge what we have right now.

 It looks like while the webextension locale is set automatically once we
 populate the `_local` folder with translations, but do we need to do
 something more for the proxy page? Right now it looks like it will only
 display the English strings:
 
[https://github.com/keroserene/snowflake/commit/ecadbe3d869ae3dcdde02d24b6246859621bd34a
 #diff-c371ea9d4448f98b3fda1dfca95c925eR174 R174]

 I like the modification from #31109 to just display that the snowflake is
 ready if there are zero users.

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

Re: [tor-bugs] #28804 [Core Tor/Tor]: Add circuit padding to padding-spec.txt and write a doc for researchers

[Tor Bug Tracker & Wiki]

#28804: Add circuit padding to padding-spec.txt and write a doc for researchers
-+-
 Reporter:  asn  |  Owner:
 |  mikeperry
 Type:  defect   | Status:
 |  assigned
 Priority:  High |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad, tor-relay, tor-cell,|  Actual Points:
  padding, tor-spec, 041-proposed, network-  |
  team-roadmap-august, scalability-roadmap   |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor2
-+-

Comment (by mikeperry):

 Developer doc WIP lives here for now: https://github.com/mikeperry-
 tor/tor/blob/circuitpadding-dev-doc/doc/circuitpadding-dev-readme.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] #30880 [Internal Services/Tor Sysadmin Team]: document backup/restore procedures

[Tor Bug Tracker & Wiki]

#30880: document backup/restore procedures
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * status:  assigned => accepted


Comment:

 i documented postgresql and mysql backup design and restore procedures.

 one thing that's missing is barebones recovery. i also wonder how to
 recover from a failure on the directory server.

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

Re: [tor-bugs] #30020 [Internal Services/Tor Sysadmin Team]: switch from our custom YAML implementation to Hiera

[Tor Bug Tracker & Wiki]

#30020: switch from our custom YAML implementation to Hiera
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  project  | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #29387   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * status:  assigned => accepted


Old description:

> We currently use a custom-made YAML database for assigning roles to
> servers and other metadata. I started using Hiera for some hosts and it
> seems to be working well.
>
> Hiera is officially supported in Puppet and shipped by default in Puppet
> 5 and later. It's the standard way of specifying metadata and class
> parameters for hosts. I suspect it covers most of our needs in terms of
> metadata and should cover most if not all of what we're currently doing
> with the YAML stuff in Puppet.
>
> We should therefore switch to using Hiera instead of our homegrown
> solution.
>
> This involves converting:
>
>  * `if has_role('foo') { include foo }` into `classes: [ 'foo' ]` in
> hiera
>  * hardcoded macros in the ferm module's `me.conf.erb` into exported
> resources
>  * templates looping over allnodeinfo into exported resources
>  * the `$roles` array into Hiera
>  * the `$localinfo` into Hiera (assuming all the data is there)
>  * the `$nodeinfo` and `$allnodeinfo` arrays into Hiera (assuming we can
> switch from LDAP for host inventory)
>  * basically any other stuff of the kind
>
> Ideally, all YAML data should end up in the hiera/ directory somehow.
> This is the first step in making our repository public (#29387) but also
> using Hiera as a more elaborate inventory system (#30273).
>
> The idea of switching from LDAP to Hiera for host inventory will
> definitely need to be evaluated more thoroughly before going ahead with
> that part of the conversion, but YAML stuff in Puppet should definitely
> be converted.
>
> The general goal of this is both to allow for a better inventory system
> but also make it easier for people to get onboarded with Puppet. By using
> community standards like Hiera, we make it easier for new people to get
> familiar with the puppet infrastructures and do things meaningfully.

New description:

 We currently use a custom-made YAML database for assigning roles to
 servers and other metadata. I started using Hiera for some hosts and it
 seems to be working well.

 Hiera is officially supported in Puppet and shipped by default in Puppet 5
 and later. It's the standard way of specifying metadata and class
 parameters for hosts. I suspect it covers most of our needs in terms of
 metadata and should cover most if not all of what we're currently doing
 with the YAML stuff in Puppet.

 We should therefore switch to using Hiera instead of our homegrown
 solution.

 This involves converting:

  * `if has_role('foo') { include foo }` into `classes: [ 'foo' ]` in hiera
  * hardcoded macros in the ferm module's `me.conf.erb` into exported
 resources
  * templates looping over allnodeinfo into exported resources
  * the `$roles` array into Hiera
  * the `$localinfo` into Hiera (assuming all the data is there)
  * the `$nodeinfo` and `$allnodeinfo` arrays into Hiera (assuming we can
 switch from LDAP for host inventory)
  * basically any other stuff of the kind, including those files:
{{{
 ./modules/torproject_org/misc/hoster.yaml
 ./modules/torproject_org/misc/local.yaml
 ./modules/ipsec/misc/config.yaml
 ./modules/roles/misc/static-components.yaml
 ./modules/roles/files/spec/spec-redirects.yaml
 }}}

 Ideally, all YAML data should end up in the hiera/ directory somehow. This
 is the first step in making our repository public (#29387) but also using
 Hiera as a more elaborate inventory system (#30273).

 The idea of switching from LDAP to Hiera for host inventory will
 definitely need to be evaluated more thoroughly before going ahead with
 that part of the conversion, but YAML stuff in Puppet should definitely be
 converted.

 The general goal of this is both to allow for a better inventory system
 but also make it easier for people to get onboarded with Puppet. By using
 community standards like Hiera, we make it easier for new people to get
 familiar with the puppet infrastructures and do things meaningfully.

--

Comment:

 we now have:

 * 3 `has_role` references
 * 4 roles left (`haproxy`, `mail_processing`, `natted`, `no_hw_clock`)
 * 2 `localinfo` references (in postfix, related to 

Re: [tor-bugs] #30310 [Circumvention/Snowflake]: Snowflake localization

[Tor Bug Tracker & Wiki]

#30310: Snowflake localization
-+-
 Reporter:  cohosh   |  Owner:  arlolra
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  l10n, snowflake-webextension, anti-  |  Actual Points:
  censorship-roadmap-august  |
Parent ID:   | Points:
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor28-can
-+-
Changes (by cohosh):

 * 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] #31252 [Circumvention/BridgeDB]: Equip BridgeDB with anti-bot mechanism

[Tor Bug Tracker & Wiki]

#31252: Equip BridgeDB with anti-bot mechanism
+-
 Reporter:  phw |  Owner:  phw
 Type:  enhancement | Status:  merge_ready
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:  4
 Reviewer:  cohosh  |Sponsor:
+-
Changes (by cohosh):

 * status:  needs_review => merge_ready


Comment:

 This looks good to me. Do we need to add this to the
 [https://gitweb.torproject.org/torspec.git/tree/bridgedb-spec.txt
 specification]?

 I'm interested in how the decisions on what headers to blacklist will be
 made. Since the files are meant to not be public, is there some process we
 go through to add new things to the blacklist or ensure that we're not
 introducing too many false positives here?

 The idea of giving out a decoy bridge is very nice. It would be
 interesting to see where/when this bridge gets blocked.

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

Re: [tor-bugs] #30471 [Circumvention/Obfs4]: Improve UX for obfs4 bridge operation

[Tor Bug Tracker & Wiki]

#30471: Improve UX for obfs4 bridge operation
--+
 Reporter:  arma  |  Owner:  (none)
 Type:  project   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Circumvention/Obfs4   |Version:
 Severity:  Normal| Resolution:
 Keywords:  anti-censorship-roadmap-december  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
  |  Sponsor28-must
--+
Changes (by gaba):

 * keywords:  anti-censorship-roadmap-august => anti-censorship-roadmap-
 december


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

Re: [tor-bugs] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220, network-team-roadmap-   |
  november   |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by gaba):

 * keywords:  tor-pt, tor-doc, 040-deferred-20190220 => tor-pt, tor-doc,
 040-deferred-20190220, network-team-roadmap-november


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

Re: [tor-bugs] #30477 [Core Tor/Tor]: Tor should self-test reachability of TCP listeners exposed by PT's

[Tor Bug Tracker & Wiki]

#30477: Tor should self-test reachability of TCP listeners exposed by PT's
-+-
 Reporter:  ahf  |  Owner:  (none)
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, network-team-roadmap-|  Actual Points:
  november   |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by gaba):

 * keywords:  tor-pt, ex-sponsor19 => tor-pt, network-team-roadmap-november


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

Re: [tor-bugs] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
-+-
 Reporter:  phoul|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt, tor-doc, |  Actual Points:
  040-deferred-20190220  |
Parent ID:  #30471   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by gaba):

 * sponsor:  Sponsor28 => Sponsor28-must


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

Re: [tor-bugs] #31103 [Core Tor/Tor]: Support ORPort picking a random port that persists across restarts

[Tor Bug Tracker & Wiki]

#31103: Support ORPort picking a random port that persists across restarts
---+---
 Reporter:  phw|  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  network-team-roadmap-november  |  Actual Points:
Parent ID:  #30471 | Points:  1
 Reviewer: |Sponsor:
   |  Sponsor28-must
---+---
Changes (by gaba):

 * sponsor:  Sponsor28-can => Sponsor28-must


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

Re: [tor-bugs] #30477 [Core Tor/Tor]: Tor should self-test reachability of TCP listeners exposed by PT's

[Tor Bug Tracker & Wiki]

#30477: Tor should self-test reachability of TCP listeners exposed by PT's
--+--
 Reporter:  ahf   |  Owner:  (none)
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  tor-pt, ex-sponsor19  |  Actual Points:
Parent ID:  #30471| Points:
 Reviewer:|Sponsor:  Sponsor28-must
--+--
Changes (by gaba):

 * sponsor:   => Sponsor28-must


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

Re: [tor-bugs] #31376 [Circumvention/Snowflake]: Make a /metrics handle at the snowflake broker for the stats collector

[Tor Bug Tracker & Wiki]

#31376: Make a /metrics handle at the snowflake broker for the stats collector
-+--
 Reporter:  cohosh   |  Owner:  cohosh
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics, stats, broker   |  Actual Points:
Parent ID:   | Points:  1
 Reviewer:  phw  |Sponsor:  Sponsor28
-+--
Changes (by phw):

 * reviewer:   => phw


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

Re: [tor-bugs] #31391 [Circumvention/Snowflake]: Do a reachability check before polling for clients

[Tor Bug Tracker & Wiki]

#31391: Do a reachability check before polling for clients
-+--
 Reporter:  cypherpunks  |  Owner:  arlolra
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by arlolra):

 * status:  new => assigned
 * owner:  (none) => arlolra


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

Re: [tor-bugs] #29461 [Metrics/CollecTor]: Add a Snowflake module

[Tor Bug Tracker & Wiki]

#29461: Add a Snowflake module
-+-
 Reporter:  irl  |  Owner:
 |  metrics-team
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Metrics/CollecTor|Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-roadmap-august, anti-|  Actual Points:
  censorship-roadmap-september   |
Parent ID:   | Points:  8
 Reviewer:  irl  |Sponsor:
 |  Sponsor28
-+-

Comment (by karsten):

 Replying to [comment:15 irl]:
 > I would like to have things becoming immutable after we think they will
 not receive more data, as it makes it easier to manage archives in the
 longer term and do things like monitor for bitrot.

 Works for me. Will revise 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] #29461 [Metrics/CollecTor]: Add a Snowflake module

[Tor Bug Tracker & Wiki]

#29461: Add a Snowflake module
-+-
 Reporter:  irl  |  Owner:
 |  metrics-team
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Metrics/CollecTor|Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-roadmap-august, anti-|  Actual Points:
  censorship-roadmap-september   |
Parent ID:   | Points:  8
 Reviewer:  irl  |Sponsor:
 |  Sponsor28
-+-

Comment (by karsten):

 Replying to [comment:12 cohosh]:
 > Replying to [comment:9 karsten]:
 > Thanks karsten!
 > >  - As indicated before, I'm using `snowflake-stats-end` as descriptor
 type identifier, which means that future data format versions will have to
 keep that line as their first line. A better choice would have been to use
 something like `snowflake-stats $version` or similar. (If it's any relief,
 we're forced to use `[0-9]{10}` as descriptor type identifier for
 bandwidth files, so there would have been plenty of room to do worse.)
 > Oh this is a good point. I can make this change pretty easily now.

 Okay, in that case please make this change and let me know where to find
 the new spec and a new sample.

 > >  - The current format only supports a single snowflake broker. Maybe
 this is acceptable for the snowflake design. But just in case that you'll
 one day want to add a second broker, you'll have to include some sort of
 broker identifier in the format.
 > This will definitely be the case for quite a while, I think a spec
 change (and version bump of the spec) will be a good way to handle this.
 How difficult will it be to have data with different spec versions on your
 end?

 Not difficult at all. Okay, let's keep this unchanged then.

 > >  - The current format is not signed, which is somewhat related to not
 having a broker identifier in the format.
 > >  - As a consequence of the above, CollecTor needs to make a decision
 whether it wants to archive a newly downloaded snowflake-stats snippet, if
 it already has another snippet with the same timestamp and different
 contents. Possible strategies for this specific case are to a) never
 overwrite, b) always overwrite, c) keep all versions by including a digest
 in the file name, d) maybe something else. I implemented a) for now.
 > I didn't think about signing, that would take while to implement I
 think. I agree that the best decision here is (a) for now.
 > >
 > > I think we can start with what we have, without changing anything of
 the above. Of course, if you want to change something with regard to
 future maintenance effort, now's the time!

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

Re: [tor-bugs] #31339 [Applications/GetTor]: GitHub blocked in Iran affecting gettor circumvention

[Tor Bug Tracker & Wiki]

#31339: GitHub blocked in Iran affecting gettor circumvention
-+--
 Reporter:  ggus |  Owner:  hiro
 Type:  enhancement  | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/GetTor  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by phw):

 Replying to [comment:3 phw]:
 > Replying to [comment:2 cypherpunks]:
 > > Is `web.archive.org` censored in Iran?
 > [[br]]
 > A friendly user from Iran just tested the site for us and it was
 reachable
 [[br]]
 Apparently, archive.is is blocked by some Iranian ISPs:
 https://github.com/citizenlab/test-lists/issues/493

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

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

[Tor Bug Tracker & Wiki]

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

Comment (by anarcat):

 asssooome! :)

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

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

[Tor Bug Tracker & Wiki]

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

Comment (by karsten):

 We're tracking work related to retiring the host in #29650 and its
 children.

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

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

[Tor Bug Tracker & Wiki]

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

Comment (by anarcat):

 awesome karsten, thanks! should we create a separate ticket for that or
 assign this one to someone or something?

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

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

[Tor Bug Tracker & Wiki]

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

Comment (by karsten):

 This is in our current roadmap. We're going to start in October and expect
 to be done by end of December.

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

Re: [tor-bugs] #27768 [Applications/Tor Browser]: Menu button does not work in Tor Browser 8 on Windows

[Tor Bug Tracker & Wiki]

#27768: Menu button does not work in Tor Browser 8 on Windows
+--
 Reporter:  therapid|  Owner:  tbb-team
 Type:  defect  | Status:
|  needs_information
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-8.0-issues, tbb-regression  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by Thorin):

 Issue 1 (empty menu item in help menu) is now #31421

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

Re: [tor-bugs] #31421 [Applications/Tor Browser]: Empty Select Field in Help Menu of Tor Browser

[Tor Bug Tracker & Wiki]

#31421: Empty Select Field in Help Menu of Tor Browser
--+--
 Reporter:  Bronami   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Very Low  |  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor: unspecified
 Severity:  Trivial   | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by Thorin):

 That would be #27768 which mentions the `menu bar`, this mentions a
 `hamburger menu` but I think they share the same source

 gk said:
 > Please consider next time to open a bug for a single issue. It's hard to
 work on 6 bugs in one ticket.

 -
 Maybe keep this one open. The other one almost looks like it's all dealt
 with?

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

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

[Tor Bug Tracker & Wiki]

#31407: Create a broker spec for metrics collection
--+---
 Reporter:  cohosh|  Owner:  cohosh
 Type:  enhancement   | Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-spec  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by cohosh):

 Makes sense to me, karsten had recommend torspec but I think the snowflake
 repository sounds fine. Afaik all we need is someplace other than the
 comments of the source code for the metrics team to 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] #31418 [Core Tor/Tor]: Fix some typos in the man page

[Tor Bug Tracker & Wiki]

#31418: Fix some typos in the man page
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  doc, no-backport, fast-fix, tor-hs,  |  Actual Points:
  nickm-merge asn-merge  |
Parent ID:   | Points:
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by dgoulet):

 * status:  needs_review => merge_ready
 * reviewer:   => dgoulet
 * keywords:  doc, no-backport, fast-fix, tor-hs => doc, no-backport, fast-
 fix, tor-hs, nickm-merge asn-merge


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] #31407 [Core Tor/Tor]: Create a broker spec for metrics collection

[Tor Bug Tracker & Wiki]

#31407: Create a broker spec for metrics collection
--+---
 Reporter:  cohosh|  Owner:  cohosh
 Type:  enhancement   | Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-spec  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by dgoulet):

 * status:  needs_review => needs_information


Comment:

 So this is specific to Snowflake if I read correctly. Or more specifically
 Snowflake -> CollecTor.

 `torspec.git` repository usually has specification related to "How Tor
 works" that ultimately creates the network.

 Most spec files are about how little-t tor components interacts with each
 other within the tor network. There is also all the exposed ABI/API from
 tor like the ControlPort spec.

 So I'm wondering if this Snowflake -> Metrics spec should be in there. I
 would say that it might be better to put it directly into the Snowflake
 repository since this describes a data format exposed by Snowflake itself
 for Metrics to digest.

 It feels more "natural" for someone looking for Snowflake's specs to go to
 the Snowflake repository no?

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

Re: [tor-bugs] #9316 [Circumvention/BridgeDB]: BridgeDB should export statistics

[Tor Bug Tracker & Wiki]

#9316: BridgeDB should export statistics
-+-
 Reporter:  asn  |  Owner:  phw
 Type:  task | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics, bridgedb, prometheus,   |  Actual Points:
  anti-censorship-roadmap-september  |
Parent ID:  #31274   | Points:  3
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30-must
-+-

Comment (by phw):

 Replying to [comment:34 phw]:
 > We probably also want BridgeDB-centric metrics such as "number of
 bridges per ring" and "number of requests that were answered with 0
 bridges". I suggest that we discuss these in a separate ticket, ok?
 [[br]]
 I filed #31422 for this enhancement.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31422 [Circumvention/BridgeDB]: Make BridgeDB report internal metrics

[Tor Bug Tracker & Wiki]

#31422: Make BridgeDB report internal metrics
+-
 Reporter:  phw |  Owner:  (none)
 Type:  enhancement | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Circumvention/BridgeDB  |Version:
 Severity:  Normal  |   Keywords:  metrics
Actual Points:  |  Parent ID:
   Points:  2   |   Reviewer:
  Sponsor:  Sponsor30-can   |
+-
 We're done with #9316, which means that we have code in place that allows
 BridgeDB to export metrics. So far, all metrics are user-centric, meaning
 that they focus on how BridgeDB users interact with the system. BridgeDB-
 centric metrics would help us debug and understand BridgeDB. The following
 come to mind:

 * Number of bridges per distribution ring.
 * Number of requests for which we had no bridges.

 We could also incorporate bridge assignments in our metrics, so we don't
 have to report them separately in the assignments.log file (see #29480).

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

Re: [tor-bugs] #31413 [Core Tor/Tor]: Check for null IPv6 addresses/extends in circuit_extend()

[Tor Bug Tracker & Wiki]

#31413: Check for null IPv6 addresses/extends in circuit_extend()
-+--
 Reporter:  neel |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, tor-relay  |  Actual Points:
Parent ID:  #24403   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by dgoulet):

 * milestone:   => Tor: unspecified


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

Re: [tor-bugs] #31419 [Internal Services/Tor Sysadmin Team]: Please update my OpenPGP key in WKD

[Tor Bug Tracker & Wiki]

#31419: Please update my OpenPGP key in WKD
-+-
 Reporter:  ggus |  Owner:  anarcat
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

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


Comment:

 key renewed, thanks!

 {{{
 anarcat@curie:account-keyring(master)$ LANG=C.UTF-8 git d
 diff --git i/torproject-keyring/gus-
 427F2D717664D215378CB4128BDC87FB7215E189.gpg w/torproject-keyring/gus-
 427F2D717664D215378CB4128BDC87FB7215E189.gpg
 index 98ba387..fa88450 100644
 --- i/torproject-keyring/gus-427F2D717664D215378CB4128BDC87FB7215E189.gpg
 +++ w/torproject-keyring/gus-427F2D717664D215378CB4128BDC87FB7215E189.gpg
 @@ -1,15 +1,15 @@
 -pub   rsa4096/8BDC87FB7215E189 2013-07-28 [SC] [expired: 2019-08-04]
 +pub   rsa4096/8BDC87FB7215E189 2013-07-28 [SC] [expires: 2020-07-29]
427F2D717664D215378CB4128BDC87FB7215E189
  uidGus - 
 -sig 38BDC87FB7215E189 2018-08-04  Gus - 
 +sig 38BDC87FB7215E189 2019-07-30  Gus - 
  uidGus - 
 -sig 38BDC87FB7215E189 2018-08-04  Gus - 
 +sig 38BDC87FB7215E189 2019-07-30  Gus - 
  uidGus 
 -sig 38BDC87FB7215E189 2018-08-04  Gus - 
 -sub   rsa2048/8A0BDAA699D5D0FE 2015-05-20 [A] [expired: never ]
 +sig 38BDC87FB7215E189 2019-07-30  Gus - 
 +sub   rsa2048/8A0BDAA699D5D0FE 2015-05-20 [A]
  sig  8BDC87FB7215E189 2015-05-20  Gus - 
 -sub   rsa4096/785040B4E07E52F1 2013-07-28 [E] [expired: 2019-08-04]
 -sig  8BDC87FB7215E189 2018-08-04  Gus - 
 -sub   rsa4096/C8560CEA6042C787 2013-07-31 [S] [expired: 2019-08-04]
 -sig  8BDC87FB7215E189 2018-08-04  Gus - 
 +sub   rsa4096/785040B4E07E52F1 2013-07-28 [E] [expires: 2020-07-29]
 +sig  8BDC87FB7215E189 2019-07-30  Gus - 
 +sub   rsa4096/C8560CEA6042C787 2013-07-31 [S] [expires: 2020-07-29]
 +sig  8BDC87FB7215E189 2019-07-30  Gus - 

 }}}

 some unsollicitated advice for next time: you don't need to show us the
 *full* certificate here. just `gpg --export --export-options export-
 minimal` is sufficient to ship new self-signatures for the expiration
 change... it's what we put in the keyring anyways. :)

 committed and pushed, should show up on mirrors fairly soon.

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

Re: [tor-bugs] #29461 [Metrics/CollecTor]: Add a Snowflake module

[Tor Bug Tracker & Wiki]

#29461: Add a Snowflake module
-+-
 Reporter:  irl  |  Owner:
 |  metrics-team
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Metrics/CollecTor|Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-roadmap-august, anti-|  Actual Points:
  censorship-roadmap-september   |
Parent ID:   | Points:  8
 Reviewer:  irl  |Sponsor:
 |  Sponsor28
-+-

Comment (by irl):

 I would like to have things becoming immutable after we think they will
 not receive more data, as it makes it easier to manage archives in the
 longer term and do things like monitor for bitrot.

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

Re: [tor-bugs] #29461 [Metrics/CollecTor]: Add a Snowflake module

[Tor Bug Tracker & Wiki]

#29461: Add a Snowflake module
-+-
 Reporter:  irl  |  Owner:
 |  metrics-team
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Metrics/CollecTor|Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-roadmap-august, anti-|  Actual Points:
  censorship-roadmap-september   |
Parent ID:   | Points:  8
 Reviewer:  irl  |Sponsor:
 |  Sponsor28
-+-

Comment (by karsten):

 Replying to [comment:13 irl]:
 > The SnowflakeStatsUrl doesn't look right at all. There's an ampersat in
 it?

 You mean the default URL in `collector.properties`? That's known, I need
 to put in the actual URL once that's available (#31376).

 > > 'snowflakes' contains a single compressed tarball with snowflake
 statistics:
 >
 > It is nice that we can have archives that after a while become read-
 only. Why are we not splitting this by month?

 The reason is that these statistics are tiny and that processing these
 files would be simpler with a single tarball. But changing this is
 trivial, if you think that doing so has more advantages.

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

Re: [tor-bugs] #31419 [Internal Services/Tor Sysadmin Team]: Please update my OpenPGP key in WKD

[Tor Bug Tracker & Wiki]

#31419: Please update my OpenPGP key in WKD
-+-
 Reporter:  ggus |  Owner:  anarcat
 Type:  task | 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 => anarcat
 * 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] #29461 [Metrics/CollecTor]: Add a Snowflake module

[Tor Bug Tracker & Wiki]

#29461: Add a Snowflake module
-+-
 Reporter:  irl  |  Owner:
 |  metrics-team
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Metrics/CollecTor|Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-roadmap-august, anti-|  Actual Points:
  censorship-roadmap-september   |
Parent ID:   | Points:  8
 Reviewer:  irl  |Sponsor:
 |  Sponsor28
-+-
Changes (by irl):

 * status:  needs_review => needs_revision


Comment:

 The SnowflakeStatsUrl doesn't look right at all. There's an ampersat in
 it?

 > 'snowflakes' contains a single compressed tarball with snowflake
 statistics:

 It is nice that we can have archives that after a while become read-only.
 Why are we not splitting this by month?

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

Re: [tor-bugs] #30979 [Core Tor/Tor]: pre-push hook runs practracker unconditionally

[Tor Bug Tracker & Wiki]

#30979: pre-push hook runs practracker unconditionally
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  merge_ready
 Priority:  Medium |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  git-scripts asn-merge  |  Actual Points:  0
Parent ID: | Points:
 Reviewer:  dgoulet|Sponsor:
---+
Changes (by dgoulet):

 * keywords:  git-scripts => git-scripts asn-merge
 * status:  needs_review => merge_ready


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] #29206 [Circumvention/Snowflake]: New design for client -- server protocol for Snowflake

[Tor Bug Tracker & Wiki]

#29206: New design for client -- server protocol for Snowflake
---+---
 Reporter:  cohosh |  Owner:  cohosh
 Type:  task   | Status:
   |  needs_revision
 Priority:  Medium |  Milestone:
Component:  Circumvention/Snowflake|Version:
 Severity:  Normal | Resolution:
 Keywords:  anti-censorship-roadmap-september  |  Actual Points:
Parent ID: | Points:  6
 Reviewer:  dcf|Sponsor:
   |  Sponsor28-must
---+---

Comment (by cohosh):

 Updating this for those following along at home.
 [https://github.com/cohosh/snowflake/compare/sequencing branch]

 Recent changes:
 - added a sessionID
 - rewrote the snowflake tests to use `net.Pipe`
 - added a timeout feature to close the underlying connection if sent data
 was not acknowledged

 Next steps:
 - send acknoweldgements
 - correlate the sessionID on both ends

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

Re: [tor-bugs] #31421 [Applications/Tor Browser]: Empty Select Field in Help Menu of Tor Browser

[Tor Bug Tracker & Wiki]

#31421: Empty Select Field in Help Menu of Tor Browser
--+--
 Reporter:  Bronami   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Very Low  |  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor: unspecified
 Severity:  Trivial   | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 This has been reported before, there's a duplicate ticket but I can't find
 it right now.

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

Re: [tor-bugs] #22755 [Circumvention/BridgeDB]: Use stem to create test descriptors

[Tor Bug Tracker & Wiki]

#22755: Use stem to create test descriptors
-+-
 Reporter:  atagar   |  Owner:  phw
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Low  |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Minor| Resolution:
 Keywords:  python, stem, bridgedb-parsers,  |  Actual Points:
  bridgedb-ci|
Parent ID:   | Points:  1
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30-can
-+-
Changes (by cohosh):

 * status:  needs_review => merge_ready


Comment:

 Looks good to me.

 Do we want to add a make clean step that removes the descriptors from the
 current directory?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31421 [Applications/Tor Browser]: Empty Select Field in Help Menu of Tor Browser

[Tor Bug Tracker & Wiki]

#31421: Empty Select Field in Help Menu of Tor Browser
--+--
 Reporter:  Bronami   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Very Low  |  Component:  Applications/Tor Browser
  Version:  Tor: unspecified  |   Severity:  Trivial
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
 Tor Browser 8.5.4 (20190307050101)

 There is a hidden empty selection field in the help menu of the browser.
 If the cursor is placed under "About Tor Browser" the hidden field is
 highlighted. Selecting the field has no visual effect.

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

Re: [tor-bugs] #31421 [Applications/Tor Browser]: Empty Select Field in Help Menu of Tor Browser

[Tor Bug Tracker & Wiki]

#31421: Empty Select Field in Help Menu of Tor Browser
--+--
 Reporter:  Bronami   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Very Low  |  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor: unspecified
 Severity:  Trivial   | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by Bronami):

 * Attachment "Tor_Help_Defect.png" added.

 Screenshot of highlighted empty field in help menu

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

Re: [tor-bugs] #31385 [Circumvention/Snowflake]: Snowflake client fails after bootstrap

[Tor Bug Tracker & Wiki]

#31385: Snowflake client fails after bootstrap
-+--
 Reporter:  cypherpunks  |  Owner:  cohosh
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by cohosh):

 Replying to [comment:17 cypherpunks]:
 > Replying to [comment:15 cypherpunks]:
 > > @cohosh: did you try to setup a Firefox WebExt 0.0.9 vs 0.0.8 test to
 determine if it's not due to the recent patch in #31100?
 > The reason I state this is that there are some snowflakes with which
 this problem doesn't happen *at all*, especially now that the # of WebExt
 Chrome users has overtaken the # of WebExt Firefox users following the
 publication [https://gigazine.net/news/20190812-tor-snowflake/ of this
 article] which has attracted quiet a bit of Japanese Chrom* users.

 Thanks cypherpunks, I'll look into 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] #31030 [Core Tor/Tor]: Coverity: Several warnings from test code

[Tor Bug Tracker & Wiki]

#31030: Coverity: Several warnings from test code
+
 Reporter:  nickm   |  Owner:  nickm
 Type:  defect  | Status:  merge_ready
 Priority:  Medium  |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  coverity asn-merge  |  Actual Points:  .1
Parent ID:  | Points:
 Reviewer:  dgoulet |Sponsor:
+
Changes (by dgoulet):

 * status:  needs_review => merge_ready
 * keywords:  coverity => coverity asn-merge


Comment:

 Replying to [comment:5 nickm]:
 > I think that it's actually okay; I've tried to explain why on the patch.
 Let me know if you buy my reasoning :)

 Oh my yes... I must have been brain dead when making that comment lol...

 ACK!

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

Re: [tor-bugs] #31353 [Core Tor/Tor]: Jenkins failure on windows: Overflow in implicit constant conversion

[Tor Bug Tracker & Wiki]

#31353: Jenkins failure on windows: Overflow in implicit constant conversion
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  merge_ready
 Priority:  Medium |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  compilation asn-merge  |  Actual Points:  0.1
Parent ID: | Points:
 Reviewer:  dgoulet|Sponsor:
---+
Changes (by dgoulet):

 * keywords:  compilation => compilation asn-merge
 * status:  needs_review => 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] #31385 [Circumvention/Snowflake]: Snowflake client fails after bootstrap

[Tor Bug Tracker & Wiki]

#31385: Snowflake client fails after bootstrap
-+--
 Reporter:  cypherpunks  |  Owner:  cohosh
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by cypherpunks):

 Replying to [comment:15 cypherpunks]:
 > @cohosh: did you try to setup a Firefox WebExt 0.0.9 vs 0.0.8 test to
 determine if it's not due to the recent patch in #31100?
 The reason I state this is that there are some snowflakes with which this
 problem doesn't happen *at all*, especially now that the # of WebExt
 Chrome users has overtaken the # of WebExt Firefox users following the
 publication [https://gigazine.net/news/20190812-tor-snowflake/ of this
 article] which has attracted quiet a bit of Japanese Chrom* users.

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

Re: [tor-bugs] #31420 [Applications/Tor Browser]: macOS 10.15

[Tor Bug Tracker & Wiki]

#31420: macOS 10.15
--+---
 Reporter:  warrior3948   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by mcs):

 * owner:  (none) => tbb-team
 * resolution:   => duplicate
 * status:  new => closed
 * component:  - Select a component => Applications/Tor Browser


Comment:

 Replying to [comment:1 warrior3948]:
 > Just saw this is a bug in macOS 10.15 beta 5, please close.

 Yes, please see #31316.

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

Re: [tor-bugs] #31316 [Applications/Tor Browser]: macOS 10.15 crash on startup

[Tor Bug Tracker & Wiki]

#31316: macOS 10.15 crash on startup
--+--
 Reporter:  mprogers  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by mcs):

 * cc: warrior3948 (added)


Comment:

 #31420 is a duplicate.

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

Re: [tor-bugs] #31420 [- Select a component]: macOS 10.15

[Tor Bug Tracker & Wiki]

#31420: macOS 10.15
--+
 Reporter:  warrior3948   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by warrior3948):

 Just saw this is a bug in macOS 10.15 beta 5, please close.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31420 [- Select a component]: macOS 10.15

[Tor Bug Tracker & Wiki]

#31420: macOS 10.15
-+--
 Reporter:  warrior3948  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Component:  - Select a component
  Version:   |   Severity:  Normal
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
 No browsers (alpha or stable) are working on macOS 10.15.

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

Re: [tor-bugs] #9316 [Circumvention/BridgeDB]: BridgeDB should export statistics

[Tor Bug Tracker & Wiki]

#9316: BridgeDB should export statistics
-+-
 Reporter:  asn  |  Owner:  phw
 Type:  task | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Circumvention/BridgeDB   |Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics, bridgedb, prometheus,   |  Actual Points:
  anti-censorship-roadmap-september  |
Parent ID:  #31274   | Points:  3
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30-must
-+-
Changes (by cohosh):

 * status:  needs_review => merge_ready


Comment:

 Thanks, this looks good to me!

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

Re: [tor-bugs] #30910 [Internal Services/Service - git]: Warning when pushing to tor.git: "disabling bitmap writing, as some objects are not being packed."

[Tor Bug Tracker & Wiki]

#30910: Warning when pushing to tor.git: "disabling bitmap writing, as some 
objects
are not being packed."
-+
 Reporter:  nickm|  Owner:  tor-gitadm
 Type:  defect   | Status:  reopened
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by dgoulet):

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


Comment:

 I get it again on my repo: https://git.torproject.org/user/dgoulet/tor.git

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

Re: [tor-bugs] #31406 [Core Tor/Tor]: new ip-address for tor.dizum.com (auth-dir)

[Tor Bug Tracker & Wiki]

#31406: new ip-address for tor.dizum.com (auth-dir)
-+-
 Reporter:  usura|  Owner:  (none)
 Type:  task | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Critical | Resolution:
 Keywords:  ip dir-auth 029-backport |  Actual Points:
  035-backport 040-backport 041-backport |
Parent ID:   | Points:  0.2
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

 * status:  needs_revision => needs_review


Comment:

 029 branch: `ticket31406_029_01`

 It merges forward cleanly up to master.

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

Re: [tor-bugs] #30762 [Metrics/Cloud]: Update OnionPerf ansible playbook to use port 443

[Tor Bug Tracker & Wiki]

#30762: Update OnionPerf ansible playbook to use port 443
---+
 Reporter:  irl|  Owner:  acute
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/Cloud  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by irl):

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


Comment:

 Merged. https://gitweb.torproject.org/metrics-
 cloud.git/commit/?id=35372062656dea6990f44e84796ef060e87fa671

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

Re: [tor-bugs] #31366 [Core Tor/Tor]: Move the connection_edge_process_relay_cell() assignment out of the if statement in circuit_receive_relay_cell()

[Tor Bug Tracker & Wiki]

#31366: Move the connection_edge_process_relay_cell() assignment out of the if
statement in circuit_receive_relay_cell()
--+
 Reporter:  neel  |  Owner:  neel
 Type:  defect| Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  technical-debt, fast-fix  |  Actual Points:
Parent ID:| Points:
 Reviewer:  asn   |Sponsor:
--+
Changes (by asn):

 * status:  needs_review => merge_ready


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] #31352 [Core Tor/Tor]: Jenkins failure on windows: ENETUNREACH undeclared.

[Tor Bug Tracker & Wiki]

#31352: Jenkins failure on windows: ENETUNREACH undeclared.
+
 Reporter:  nickm   |  Owner:  nickm
 Type:  defect  | Status:  merge_ready
 Priority:  Medium  |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  regression windows  |  Actual Points:  0.1
Parent ID:  | Points:
 Reviewer:  asn |Sponsor:
+
Changes (by asn):

 * status:  needs_review => merge_ready


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] #31175 [Core Tor/Tor]: Teach practracker to apply separate rules for C headers

[Tor Bug Tracker & Wiki]

#31175: Teach practracker to apply separate rules for C headers
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-august  |  Actual Points:  .1
Parent ID:  #29746   | Points:  1
 Reviewer:  asn  |Sponsor:  Sponsor31-can
-+-
Changes (by asn):

 * status:  needs_review => merge_ready


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] #31418 [Core Tor/Tor]: Fix some typos in the man page

[Tor Bug Tracker & Wiki]

#31418: Fix some typos in the man page
+--
 Reporter:  teor|  Owner:  teor
 Type:  defect  | Status:
|  needs_review
 Priority:  Medium  |  Milestone:  Tor:
|  0.4.2.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  doc, no-backport, fast-fix, tor-hs  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by teor):

 * status:  assigned => needs_review
 * keywords:  doc, no-backport => doc, no-backport, fast-fix, tor-hs


Comment:

 See my pull request:
 https://github.com/torproject/tor/pull/1233

 I don't think these typos need a backport, or a separate reviewer and
 merger.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31418 [Core Tor/Tor]: Fix some typos in the man page

[Tor Bug Tracker & Wiki]

#31418: Fix some typos in the man page
--+
 Reporter:  teor  |  Owner:  teor
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  doc, no-backport
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+


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