Re: [tor-bugs] #31684 [Core Tor/Tor]: Add control port GETINFO support for dumping the local consensus

[Tor Bug Tracker & Wiki]

#31684: Add control port GETINFO support for dumping the local consensus
---+
 Reporter:  asn|  Owner:  (none)
 Type:  task   | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  control-port easy  |  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:
---+

Comment (by ltbringer):

 > This ticket creates a small reduction in code quality, because it turns
 a 300-line function into a 320-line function. If you would like to improve
 code quality, please add a commit that splits the two dir/status-vote/*
 GETINFOs into their own static function. Otherwise, our reviewer can do
 that for you, before they approve your pull request.

 I will create the static function. I feel the entire function could use
 some help as I see the if-else blocks having some degree of similarity (my
 commit creates almost identical blocks, which differ only by a string
 argument).

 Also, I was unaware of the spec. I'll fix that 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

[tor-bugs] #31763 [Metrics/Relay Search]: relay-search lists flakey as down for an hour or two, when it's never been reachable

[Tor Bug Tracker & Wiki]

#31763: relay-search lists flakey as down for an hour or two, when it's never 
been
reachable
--+--
 Reporter:  arma  |  Owner:  metrics-team
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 
https://metrics.torproject.org/rs.html#details/5481936581E23D2D178105D44DB6915AB06BFB7F
 is marked as offline, and the "downtime" section varies over time but it
 always seems to be more than one hour and less than two hours.

 That's because the bridge firewalled its ORPort, so it never gets the
 Running flag from Serge, so bridgedb won't give it out. Makes sense -- it
 is the snowflake bridge, so it receives its connections via the bridge-
 side snowflake proxy, not direct to the ORPort.

 But metrics seems to have hit an edge case: it does something weird when
 it has no known "time it was last up" value.

 (Not a big deal, but it's been sitting in a tab for some days now and I
 figured I should file the 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] #31607 [Applications/Tor Browser]: App menu items stop working

[Tor Bug Tracker & Wiki]

#31607: App menu items stop working
-+-
 Reporter:  mcs  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff68-esr, tbb-9.0-must-alpha,|  Actual Points:
  TorBrowserTeam201909   |
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
-+-

Comment (by mcs):

 A quick update: this bug occurs without any of our Tor Browser patches.
 Specifically, I checked out revision
 a37fc1d6835dcebc36ae80f1d81f06d7807988b4 and then applied the #28044 patch
 (e05db1ef99bf1fa0717e357d7359ab6f7104a8c6). It is easy to reproduce this
 bug by starting with TOR_FORCE_NET_CONFIG=1, clicking "Connect", and then
 hitting Cmd+, (which should open the about:preferences but does not).

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

Re: [tor-bugs] #31576 [Core Tor/Tor]: Fix shellcheck errors in contrib/dist/rc.subr, and add to test-shellcheck

[Tor Bug Tracker & Wiki]

#31576: Fix shellcheck errors in contrib/dist/rc.subr, and add to 
test-shellcheck
--+--
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Minor | Resolution:
 Keywords:  shellcheck|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 Ok, I'll ask about both unmaintained service files:

 * contrib/dist
   * rc.subr - script
   * tor.service.in - systemd service ini file

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

Re: [tor-bugs] #30797 [Core Tor/Tor]: Stop shipping an abandoned systemd script?

[Tor Bug Tracker & Wiki]

#30797: Stop shipping an abandoned systemd script?
--+--
 Reporter:  arma  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #31576| Points:
 Reviewer:|Sponsor:
--+--
Changes (by teor):

 * parent:   => #31576


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

Re: [tor-bugs] #31576 [Core Tor/Tor]: Fix shellcheck errors in contrib/dist/rc.subr, and add to test-shellcheck

[Tor Bug Tracker & Wiki]

#31576: Fix shellcheck errors in contrib/dist/rc.subr, and add to 
test-shellcheck
--+--
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Minor | Resolution:
 Keywords:  shellcheck|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by arma):

 Replying to [comment:3 nickm]:
 > Maybe we should sent a message to the tor-packagers list, asking if
 anybody is currently using any of the init scripts from our repository?

 See also #30797. I'm not sure what the right outcome should be, but the
 discussions there seem very related to this question.

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

Re: [tor-bugs] #31743 [Internal Services/Tor Sysadmin Team]: SMTP on carinatum

[Tor Bug Tracker & Wiki]

#31743: SMTP on carinatum
-+-
 Reporter:  atagar   |  Owner:  anarcat
 Type:  defect   | Status:  closed
 Priority:  Very High|  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by atagar):

 Wonderful anarcat, thank you! I just received a DocTor notification email
 so looks great on my end. Much appreciated. :)

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

Re: [tor-bugs] #31576 [Core Tor/Tor]: Fix shellcheck errors in contrib/dist/rc.subr, and add to test-shellcheck

[Tor Bug Tracker & Wiki]

#31576: Fix shellcheck errors in contrib/dist/rc.subr, and add to 
test-shellcheck
--+--
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Minor | Resolution:
 Keywords:  shellcheck|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 Replying to [comment:3 nickm]:
 > Hm. I think this one is probably safe to remove: it has decorations
 indicating that it came from FreeBSD's CVS repository, which suggests to
 me that the FreeBSD people are probably maintaining their own version.

 +1

 > There are other scripts of this kind, however.  Maybe we should sent a
 message to the tor-packagers list, asking if anybody is currently using
 any of the init scripts from our repository?  If we find that some are in
 use, we can decide whether to keep them or to give other projects
 responsibility for them.

 I tried looking for these other scripts, and I could only find:
 * contrib/dist
   * rc.subr - script
   * tor.service.in - systemd service ini file

 Do you want me to ask tor-packagers about these two files?
 Or are there other files you are thinking of?

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

Re: [tor-bugs] #31483 [Core Tor/Tor]: token_bucket_ctr_adjust() does not convert rate to step

[Tor Bug Tracker & Wiki]

#31483: token_bucket_ctr_adjust() does not convert rate to step
--+
 Reporter:  teor  |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Very High |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:  0.5
 Reviewer:  asn   |Sponsor:  Sponsor31-can
--+
Changes (by nickm):

 * keywords:  042-must =>
 * sponsor:  Sponsor31-must => Sponsor31-can
 * milestone:  Tor: 0.4.2.x-final => Tor: 0.4.3.x-final


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

Re: [tor-bugs] #31483 [Core Tor/Tor]: token_bucket_ctr_adjust() does not convert rate to step

[Tor Bug Tracker & Wiki]

#31483: token_bucket_ctr_adjust() does not convert rate to step
--+
 Reporter:  teor  |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Very High |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  042-must  |  Actual Points:
Parent ID:| Points:  0.5
 Reviewer:  asn   |Sponsor:  Sponsor31-must
--+

Comment (by teor):

 I feel like the answer is "none of it".

 If the code works, but it's just ugly, that's an 0.4.3 issue.

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

Re: [tor-bugs] #30527 [Core Tor/Tor]: Fix coverity warnings in test_parsecommon.c

[Tor Bug Tracker & Wiki]

#30527: Fix coverity warnings in test_parsecommon.c
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:  Tor:
|  0.4.2.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
|  worksforme
 Keywords:  coverity technical-debt 042-should  |  Actual Points:  0.1
Parent ID:  | Points:  .5
 Reviewer:  teor|Sponsor:
|  Sponsor31-can
+--
Changes (by teor):

 * status:  needs_review => closed
 * resolution:   => worksforme
 * actualpoints:  0 => 0.1


Comment:

 I spent some time searching for this coverity issue, and I couldn't find
 it.
 Coverity has purged all historical source code and metadata, so it may be
 impossible to locate it.

 However, I have confirmed that it is not a current open issue in coverity.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: 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 [Circumvention/Snowflake]: 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:  closed
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tor-spec BugSmashFund|  Actual Points:
Parent ID:   | Points:
 Reviewer:  phw  |Sponsor:
-+
Changes (by gaba):

 * keywords:  tor-spec => tor-spec BugSmashFund


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

Re: [tor-bugs] #31425 [Circumvention/Snowflake]: Snowflake broker is sluggish and sometimes fails

[Tor Bug Tracker & Wiki]

#31425: Snowflake broker is sluggish and sometimes fails
-+--
 Reporter:  cohosh   |  Owner:  dcf
 Type:  defect   | Status:  assigned
 Priority:  Low  |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  broker   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by gaba):

 * keywords:  broker BugSmashFund => broker


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

Re: [tor-bugs] #31425 [Circumvention/Snowflake]: Snowflake broker is sluggish and sometimes fails

[Tor Bug Tracker & Wiki]

#31425: Snowflake broker is sluggish and sometimes fails
-+--
 Reporter:  cohosh   |  Owner:  dcf
 Type:  defect   | Status:  assigned
 Priority:  Low  |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  broker BugSmashFund  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by gaba):

 * keywords:  broker => broker BugSmashFund


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

Re: [tor-bugs] #29801 [Core Tor/Tor]: Write a proposal for IPv6 "Happy Eyeballs" on Tor clients

[Tor Bug Tracker & Wiki]

#29801: Write a proposal for IPv6 "Happy Eyeballs" on Tor clients
---+
 Reporter:  neel   |  Owner:  neel
 Type:  enhancement| Status:  needs_revision
 Priority:  Medium |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ipv6, prop299  |  Actual Points:
Parent ID:  #17835 | Points:
 Reviewer:  nickm  |Sponsor:
---+

Comment (by neel):

 Thank you so much!

 I could not update Prop306 as I was busy and couldn't attend to 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

[tor-bugs] #31762 [Core Tor/Tor]: Add GETINFO dir/status-vote/current/consensus-microdesc to the control spec

[Tor Bug Tracker & Wiki]

#31762: Add GETINFO dir/status-vote/current/consensus-microdesc to the control 
spec
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  control-port easy tor-spec
Actual Points:|  Parent ID:  #31684
   Points:|   Reviewer:
  Sponsor:|
--+
 Here:
 https://gitweb.torproject.org/torspec.git/tree/control-spec.txt#n811

 With "added in Tor 0.4.3.1-alpha"

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

Re: [tor-bugs] #31684 [Core Tor/Tor]: Add control port GETINFO support for dumping the local consensus

[Tor Bug Tracker & Wiki]

#31684: Add control port GETINFO support for dumping the local consensus
---+
 Reporter:  asn|  Owner:  (none)
 Type:  task   | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  control-port easy  |  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:
---+

Comment (by teor):

 Hi, thanks for this pull request!

 Replying to [comment:3 ltbringer]:
 > https://github.com/torproject/tor/pull/1328
 >
 > This adds `GETINFO dir/status-vote/microdesc/consensus`

 How did you come up with this GETINFO name?
 If we want the control spec to match the directory spec, it should be:
 GETINFO dir/status-vote/current/consensus-microdesc
 See https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n3895

 This ticket creates a small reduction in code quality, because it turns a
 300-line function into a 320-line function. If you would like to improve
 code quality, please add a commit that splits the two dir/status-vote/*
 GETINFOs into their own static function. Otherwise, our reviewer can do
 that for you, before they approve your pull request.

 We also need to update the control-spec, I'll open a child ticket.

 (We could do #28982 instead of this ticket, but that's a much more complex
 refactor.)

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

Re: [tor-bugs] #31190 [Core Tor/Tor]: List all valid DirPort urls

[Tor Bug Tracker & Wiki]

#31190: List all valid DirPort urls
--+--
 Reporter:  atagar|  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-spec  |  Actual Points:
Parent ID:  #28982| Points:
 Reviewer:|Sponsor:
--+--
Changes (by teor):

 * parent:   => #28982


Comment:

 If we do #28982, and turn all DirPort URLs into GETINFOs, stem will be
 able to get this listing over the control port.
 And we can add any missing URLs to the dir-spec as stem finds new ones.
 We can then update the control-spec to reference the list in the dir-spec.

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

Re: [tor-bugs] #31757 [Core Tor/Tor]: test_parseconf.sh: apparently not reliable on Appveyor

[Tor Bug Tracker & Wiki]

#31757: test_parseconf.sh: apparently not reliable on Appveyor
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:  accepted
 Priority:  High |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-ci 042-should asn-merge  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  ahf  |Sponsor:  Sponsor31-can
-+-

Comment (by teor):

 This is a strange bug: we have other tests that run Tor on Windows:
 {{{
 PASS: src/test/test_zero_length_keys.sh
 PASS: src/test/test_cmdline.sh
 }}}

 Are we doing something in the script that doesn't work with Tor on
 Windows?
 What's the smallest script that reproduces the issue?

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

Re: [tor-bugs] #30527 [Core Tor/Tor]: Fix coverity warnings in test_parsecommon.c

[Tor Bug Tracker & Wiki]

#30527: Fix coverity warnings in test_parsecommon.c
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  defect  | Status:
|  needs_review
 Priority:  Medium  |  Milestone:  Tor:
|  0.4.2.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  coverity technical-debt 042-should  |  Actual Points:  0
Parent ID:  | Points:  .5
 Reviewer:  teor|Sponsor:
|  Sponsor31-can
+--

Comment (by teor):

 I don't have a copy of the coverity email with these defects: it may have
 been eaten by a spam filter.
 (In future, let's copy the defect text into the ticket?)

 I'll use the online interface to check for coverity issues in
 test_parsecommon.c from approximately May 2019.

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

Re: [tor-bugs] #28849 [Core Tor/Tor]: Handle dormant mode in process library and for PT's

[Tor Bug Tracker & Wiki]

#28849: Handle dormant mode in process library and for PT's
-+-
 Reporter:  ahf  |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_information
 Priority:  High |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:
 Keywords:  042-proposed, anti-censorship-   |  Actual Points:  2.5
  roadmap-july   |
Parent ID:   | Points:  3
 Reviewer:  dcf  |Sponsor:
 |  Sponsor28-must
-+-
Changes (by teor):

 * status:  needs_review => needs_information


Comment:

 This ticket is on the network team review list, but there's nothing we can
 do about it.
 Putting in needs_information until the external reviews have been
 completed.

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

Re: [tor-bugs] #30909 [Core Tor/sbws]: sbws consensus timestamp updates incorrectly use the current time

[Tor Bug Tracker & Wiki]

#30909: sbws consensus timestamp updates incorrectly use the current time
+---
 Reporter:  teor|  Owner:  teor
 Type:  defect  | Status:  needs_revision
 Priority:  Medium  |  Milestone:  sbws: 1.1.x-final
Component:  Core Tor/sbws   |Version:  sbws: 1.1.0
 Severity:  Normal  | Resolution:
 Keywords:  sbws-ci-fail-sometimes  |  Actual Points:  0.2
Parent ID:  #30733  | Points:  0.2
 Reviewer:  juga|Sponsor:
+---
Changes (by teor):

 * status:  needs_review => 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] #31589 [Core Tor/Tor]: hs-v3: Simplify decrypt_desc_layer interface

[Tor Bug Tracker & Wiki]

#31589: hs-v3: Simplify decrypt_desc_layer interface
---+---
 Reporter:  asn|  Owner:  (none)
 Type:  defect | Status:
   |  needs_review
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-hs easy refactoring tech-debt  |  Actual Points:
Parent ID: | Points:
 Reviewer:  asn|Sponsor:
---+---
Changes (by teor):

 * milestone:  Tor: unspecified => Tor: 0.4.3.x-final


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

Re: [tor-bugs] #25568 [Core Tor/Tor]: hs: Lookup failure cache when introducing to an intro point

[Tor Bug Tracker & Wiki]

#25568: hs: Lookup failure cache when introducing to an intro point
-+-
 Reporter:  dgoulet  |  Owner:  neel
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  security, tor-hs,|  Actual Points:
  034-triage-20180328, 034-removed-20180328, |
  035-backport-maybe, 040-backport-maybe, 041|
  -backport-maybe, 042-backport-maybe|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  security, tor-hs, 034-triage-20180328, 034-removed-20180328 =>
 security, tor-hs, 034-triage-20180328, 034-removed-20180328, 035
 -backport-maybe, 040-backport-maybe, 041-backport-maybe, 042-backport-
 maybe
 * reviewer:  dgoulet =>
 * milestone:  Tor: unspecified => Tor: 0.4.3.x-final


Comment:

 dgoulet is on leave, please re-assign this 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] #31147 [Core Tor/Tor]: Check tor_vasprintf for error return values.

[Tor Bug Tracker & Wiki]

#31147: Check tor_vasprintf for error return values.
-+-
 Reporter:  paldium  |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Low  |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.0.5
 Severity:  Normal   | Resolution:
 Keywords:  035-backport 040-backport|  Actual Points:
  041-backport   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * reviewer:  mikeperry =>


Comment:

 Mike is not doing reviews this month, please re-assign.

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

Re: [tor-bugs] #29801 [Core Tor/Tor]: Write a proposal for IPv6 "Happy Eyeballs" on Tor clients

[Tor Bug Tracker & Wiki]

#29801: Write a proposal for IPv6 "Happy Eyeballs" on Tor clients
---+
 Reporter:  neel   |  Owner:  neel
 Type:  enhancement| Status:  needs_revision
 Priority:  Medium |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ipv6, prop299  |  Actual Points:
Parent ID:  #17835 | Points:
 Reviewer:  nickm  |Sponsor:
---+
Changes (by teor):

 * status:  needs_review => needs_revision


Comment:

 We have at least 2 outstanding reviews on this proposal, but the author
 has not updated it.
 We merged it to tor-spec as a draft.

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

Re: [tor-bugs] #31336 [Core Tor/Tor]: Fix usage for add_c_file.py

[Tor Bug Tracker & Wiki]

#31336: Fix usage for add_c_file.py
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  043-should, 042-can network-team-|  Actual Points:
  roadmap-september  |
Parent ID:  #29217   | Points:  0.1
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by Jigsaw52):

 * cc: danielpinto52@… (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] #31733 [Internal Services/Service - lists]: Add gus@tpo as moderator for community team mailing list

[Tor Bug Tracker & Wiki]

#31733: Add gus@tpo as moderator for community team mailing list
---+
 Reporter:  ggus   |  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:
---+
Changes (by ggus):

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


Comment:

 Thanks! I'm also adding Pili and you as moderators.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31761 [Core Tor/Tor]: new

[Tor Bug Tracker & Wiki]

#31761: new
-+-
 Reporter:  RomeoTyler   |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Component:  Core
 |  Tor/Tor
  Version:   |   Severity:  Normal
 Keywords:  practracker, tech-debt,  |  Actual Points:
  refactoring, easy, 041-deferred-20190530,  |
  network-team-roadmap-july, dgoulet-merge   |
Parent ID:  #29746   | 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] #31687 [Core Tor/Tor]: FreeBSD compilation warns with Tor 0.4.1.5

[Tor Bug Tracker & Wiki]

#31687: FreeBSD compilation warns with Tor 0.4.1.5
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.5
 Severity:  Normal   | Resolution:
 Keywords:  warning compiler 042-should  |  Actual Points:  .1
  041-backport 040-backport 035-backport |
  BugSmashFund asn-merge |
Parent ID:   | Points:
 Reviewer:  ahf  |Sponsor:
-+-
Changes (by nickm):

 * keywords:
 warning compiler 042-should 041-backport 040-backport 035-backport
 BugSmashFund
 =>
 warning compiler 042-should 041-backport 040-backport 035-backport
 BugSmashFund asn-merge


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

Re: [tor-bugs] #31336 [Core Tor/Tor]: Fix usage for add_c_file.py

[Tor Bug Tracker & Wiki]

#31336: Fix usage for add_c_file.py
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  043-should, 042-can network-team-|  Actual Points:
  roadmap-september  |
Parent ID:  #29217   | Points:  0.1
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by nickm):

 * keywords:  043-should, network-team-roadmap-september => 043-should,
 042-can network-team-roadmap-september


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

Re: [tor-bugs] #31483 [Core Tor/Tor]: token_bucket_ctr_adjust() does not convert rate to step

[Tor Bug Tracker & Wiki]

#31483: token_bucket_ctr_adjust() does not convert rate to step
--+
 Reporter:  teor  |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Very High |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  042-must  |  Actual Points:
Parent ID:| Points:  0.5
 Reviewer:  asn   |Sponsor:  Sponsor31-must
--+

Comment (by nickm):

 So, I don't think we have a real misbehavior here, but we do have a small
 piece of ugliness.

 The reason that I think we don't have a bug is that
 token_bucket_ctr_refill() doesn't use TICKS_PER_STEP, so it isn't
 necessary to convert the rate in "units per tick" into "units per step"
 when using a tocken_bucket_ctr_t.  So that computation is correct.

 To make matters more complicated, it's not clear to me that we want to
 harmonize both systems to use the same units. Right now, both
 "token_bucket_rw_t" and "token_bucket_ctr_t" are built to take their time
 in abstract ticks, and to track a resource measured in abstract units.
 For token_bucket_rw_t as it is used, the units are 1 byte, and the ticks
 are about 1 ms.  To avoid rounding errors, we consider time as in "steps"
 of 16 ticks.

 But for token_bucket_ctr_t as it is used for onion service DOS defenses,
 the units are 1 introduction cell, and the ticks are 1 second.  25 cells
 per second is the default rate.  There's no reason to group these ticks
 into a 16-tick step.  On the other hand, if we moved to a tick size that
 was smaller than 1 second, we'd have rounding errors with the cells-per-
 second calculation.

 I think that if we want to harmonize these two types, we should do it by
 having them both use the same step/tick logic, and by fixing ticks around
 1 ms.  We should also say that units have to be chosen so that they have a
 meaningful resolution with respect to the tick size: instead of introduce
 cells per tick, we would have to use units something like "hundredths of
 an introduce cell per tick".

 How much of this should we do in 0.4.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] #31336 [Core Tor/Tor]: Fix usage for add_c_file.py

[Tor Bug Tracker & Wiki]

#31336: Fix usage for add_c_file.py
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  043-should, network-team-roadmap-|  Actual Points:
  september  |
Parent ID:  #29217   | Points:  0.1
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by Jigsaw52):

 * status:  new => needs_review


Comment:

 I've created a patch that fixes this by using os.path.relpath to get the
 path relative to ./src.
 Both ./src/foo.c and src/foo.c are supported.

 Pull request here: https://github.com/torproject/tor/pull/1329

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

Re: [tor-bugs] #19332 [Metrics/CollecTor]: Add a BridgeDB module

[Tor Bug Tracker & Wiki]

#19332: Add a BridgeDB module
-+-
 Reporter:  mrphs|  Owner:  karsten
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Metrics/CollecTor|Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-roadmap-2019-q2, anti-   |  Actual Points:
  censorship-roadmap-september   |
Parent ID:   | Points:  8
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30-must
-+-
Changes (by phw):

 * owner:  phw => karsten
 * status:  merge_ready => assigned


Comment:

 Replying to [comment:21 cohosh]:
 > These changes look good to me.
 [[br]]
 Merged to [https://gitweb.torproject.org/project/bridges/bridgedb-
 admin.git/commit/?id=7b534da219c25bb48fe511288f8e3289cd643d4f master].
 [[br]]
 > Since all logs (including previously rotated ones) are synced each time
 with rsync, is there a way to detect if old logs have been corrupted and
 are overwriting the previously synced logs? Not sure how we want to handle
 a case where logs that have previously been synced have changed for some
 reason, or what the easiest way to deal with this is.
 [[br]]
 I left the patch as it is according to Karsten's suggestion. I also
 reassigned the ticket to Karsten because BridgeDB's side is looking good
 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] #19332 [Metrics/CollecTor]: Add a BridgeDB module

[Tor Bug Tracker & Wiki]

#19332: Add a BridgeDB module
-+-
 Reporter:  mrphs|  Owner:  phw
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Metrics/CollecTor|Version:
 Severity:  Normal   | Resolution:
 Keywords:  metrics-roadmap-2019-q2, anti-   |  Actual Points:
  censorship-roadmap-september   |
Parent ID:   | Points:  8
 Reviewer:  cohosh   |Sponsor:
 |  Sponsor30-must
-+-

Comment (by phw):

 Replying to [comment:22 karsten]:
 > Okay, please let me know when I need to do something on colchicifolium's
 side.
 [[br]]
 The rsync is done from our side. We are already trying to sync data to
 `/srv/collector.torproject.org/collector/in/bridgedb-stats/`.

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

Re: [tor-bugs] #31687 [Core Tor/Tor]: FreeBSD compilation warns with Tor 0.4.1.5

[Tor Bug Tracker & Wiki]

#31687: FreeBSD compilation warns with Tor 0.4.1.5
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.5
 Severity:  Normal   | Resolution:
 Keywords:  warning compiler 042-should  |  Actual Points:  .1
  041-backport 040-backport 035-backport |
  BugSmashFund   |
Parent ID:   | Points:
 Reviewer:  ahf  |Sponsor:
-+-
Changes (by ahf):

 * status:  needs_review => merge_ready


Comment:

 Looks good.

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

Re: [tor-bugs] #29655 [Metrics]: Tor Metrics / Users / Bridge users by country and transport / Source: China, fails to render graph lines clearly

[Tor Bug Tracker & Wiki]

#29655: Tor Metrics / Users / Bridge users by country and transport / Source:
China, fails to render graph lines clearly
-+--
 Reporter:  monmire  |  Owner:  metrics-team
 Type:  defect   | Status:  reopened
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  Tor-Metrics-graph issue  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by monmire):

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


Comment:

 Graphs of `Bridge users by country and transport Source` do not show solid
 lines for the average number of connections.

 For example, the graph of `Bridge users by country and transport Source:
 Venezuela` https://metrics.torproject.org/userstats-bridge-
 combined.html?start=2019-09-10=2019-09-16=ve  shows ribbons
 and solid lines for the `low` and `high` bounds of  , meek, and obfs4
 connections, but it does not show solid lines for the `average` number of
 , meek, and obfs4 connections.

 Would not solid lines showing the average number of , meek, and obfs4
 connections allow users to gauge visually, more quickly and more
 accurately, the average number of connections during a defined date
 interval or on certain dates?

 For each Source, can we have solid lines showing the average number of
 connections for , meek, and obfs4?

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

Re: [tor-bugs] #25140 [Core Tor/Tor]: Parse only .torrc files in torrc.d directory

[Tor Bug Tracker & Wiki]

#25140: Parse only .torrc files in torrc.d directory
-+-
 Reporter:  iry  |  Owner:
 |  Jigsaw52
 Type:  task | Status:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.1-alpha
 Severity:  Major| Resolution:
 Keywords:  034-triage-20180328, |  Actual Points:
  035-removed-20180711   |
Parent ID:   | Points:
 Reviewer:  ahf  |Sponsor:
-+-
Changes (by ahf):

 * status:  needs_review => needs_revision


Comment:

 Hey!

 My apologies for the delay with this one. I still have no idea why Trac
 ate my comment after our meeting. The comment I wrote back then is the
 following according to my notes:

 We are concerned right now about the complexity of these patches,
 particularly around the `glob()` implementation, but also the size of the
 changes to the `conffile.c` file.

 Nick and I discussed the patches and came up with the following rather
 radical suggestions to make the code simpler:

 - Switch to use `fnmatch()` on the platforms where that function is
 available.

   This would allow you to implement more or less the same functionality in
 a simpler way using `fnmatch()` and `listdir()` while simplifying the code
 rather a lot and reducing the overall size of the patches.

 - For platforms that DOES NOT support `fnmatch()`, we bundle an
 implementation from another project (with a similar license as Tor) in the
 `src/ext/'. This could for example be this one from Git (which they took
 from the OpenBSD project):
 https://github.com/libgit2/libgit2/blob/master/src/fnmatch.c

   You can see how we do this with other functions by looking at the other
 code imports found in the `src/ext` directory tree.

 This would make the code more edible for us and overall much less complex
 than before. `fnmatch()` and `listdir()` would not support the same amount
 of features as a real `glob()` implementation would, but do we really need
 those features?

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

Re: [tor-bugs] #31408 [Core Tor/Tor]: torrc : ClientOnionAuthDir after include directives breaks client to v2 services

[Tor Bug Tracker & Wiki]

#31408: torrc : ClientOnionAuthDir after include directives breaks client to v2
services
+--
 Reporter:  xaho|  Owner:  asn
 Type:  defect  | Status:  assigned
 Priority:  Very High   |  Milestone:  Tor:
|  0.4.2.x-final
Component:  Core Tor/Tor|Version:  Tor: 0.4.0.5
 Severity:  Normal  | Resolution:
 Keywords:  tor-hs regression 042-must  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by Jigsaw52):

 I think it might be useful to have both torrc and the actual files within
 /etc/tor/torrc.d/ with any sensitive information replaced by 'x'. I am
 thinking this could be a parsing bug and things like whitespace and new
 line differences and empty files vs files with only comments/whitespace
 could matter here.

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

Re: [tor-bugs] #31684 [Core Tor/Tor]: Add control port GETINFO support for dumping the local consensus

[Tor Bug Tracker & Wiki]

#31684: Add control port GETINFO support for dumping the local consensus
---+
 Reporter:  asn|  Owner:  (none)
 Type:  task   | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  control-port easy  |  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:
---+
Changes (by ltbringer):

 * 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] #31700 [Internal Services/Service - jabber]: decomission jabber server

[Tor Bug Tracker & Wiki]

#31700: decomission jabber server
+--
 Reporter:  anarcat |  Owner:  anarcat
 Type:  project | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Internal Services/Service - jabber  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  #31686  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by anarcat):

 * parent:  #30608 => #31686


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

Re: [tor-bugs] #30608 [Internal Services/Tor Sysadmin Team]: Have a SMTP out only server

[Tor Bug Tracker & Wiki]

#30608: Have a SMTP out only server
-+-
 Reporter:  dgoulet  |  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):

 weasel disagrees we should reuse the webRTC password, which changes the
 roadmap and frees us from blocking on the jabber server, which is spun off
 completely separately in #31700 (and not #31686 as previously mentioned).

 So our procedure should now be:

  1. create a new field (`emailPassword`?) in the LDAP schema
  2. update the mail gateway to support changes to the field
  3. update the web interface (to support changing the field as well?)
  4. optionally, setup a separate email server to accept submissions and
 keep mail servers aware that not only eugeni sends email
  5. hook up the password field as authentication in Postfix in the server
 (probably through ud-generate?)
  4. do tests with the users in this ticket, and if this works, propagate
 to all current LDAP users
  5. create LDAP accounts for more users who want to use the system

 i'm not very familiar with the first steps here, so that might be more
 complicated than i thought.

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

Re: [tor-bugs] #31760 [Internal Services/Service - trac]: swati needs a trac account

[Tor Bug Tracker & Wiki]

#31760: swati needs a trac account
--+-
 Reporter:  gaba  |  Owner:  qbi
 Type:  task  | Status:  closed
 Priority:  High  |  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:  invalid
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by gaba):

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


Comment:

 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] #31244 [Internal Services/Tor Sysadmin Team]: long term prometheus metrics

[Tor Bug Tracker & Wiki]

#31244: long term prometheus metrics
-+-
 Reporter:  anarcat  |  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):

 so far, the 20-30GiB storage on nbg1 is struggling a bit, so i'm tempted
 to downgrade to 15 minutes samples. but maybe we can start by 5min/1yr
 (12GiB) and see how that goes 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] #31568 [Applications/Tor Browser]: Update How to Create Gradle Dependencies

[Tor Bug Tracker & Wiki]

#31568: Update How to Create Gradle Dependencies
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-rbm, ff68-esr, tbb-9.0-must- |  Actual Points:
  alpha, TorBrowserTeam201909|
Parent ID:  #30324   | Points:  0.25
 Reviewer:   |Sponsor:
-+-
Changes (by sisbell):

 * status:  needs_revision => needs_review


Comment:

 Try these changes. I'll do some more testing as well

 https://github.com/sisbell/tor-browser-
 build/commit/80c7ad7e56c4106c063ec63ecd6acf66e3859daf

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

Re: [tor-bugs] #31700 [Internal Services/Service - jabber]: decomission jabber server

[Tor Bug Tracker & Wiki]

#31700: decomission jabber server
+--
 Reporter:  anarcat |  Owner:  anarcat
 Type:  project | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Internal Services/Service - jabber  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  #30608  | Points:
 Reviewer:  |Sponsor:
+--
Description changed by anarcat:

Old description:

> the jabber server is not really used anymore, and we need the LDAP field
> for the new email service (in #30608).
>
> decommission the server (chamaemoly) with a warning period for users to
> have time to migrate their rosters off the server.
>
> roadmap:
>
>  1. T-30d: warn users about impeding shutdown,
>  2. T: shutdown the jabber service itself
>  3. T+7d: start the server decommissioning process

New description:

 the jabber server is not really used anymore, and we need the LDAP field
 for the new email service (in #30608).

 decommission the server (chamaemoly) with a warning period for users to
 have time to migrate their rosters off the server.

 roadmap:

  1. T-30d (2019-09-16): warn users about impeding shutdown,
  2. T (2019-10-16): shutdown the jabber service itself (`service prosody
 stop`)
  3. T+7d (2019-10-23): start the server decommissioning process
 * remove from nagios
 * "undefine" the VM
 * queue disk destruction in another +7d
 * remove from LDAP
 * remove from DNS
 * remove from Puppet
 * remove from tor-passwords
 * remove from documentation
 * schedule backup cleanup (+30d?)

--

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

Re: [tor-bugs] #31700 [Internal Services/Service - jabber]: decomission jabber server

[Tor Bug Tracker & Wiki]

#31700: decomission jabber server
+--
 Reporter:  anarcat |  Owner:  anarcat
 Type:  project | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Internal Services/Service - jabber  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  #30608  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by anarcat):

 reviewed, approved, and sent to t...@list.tpo.

 https://lists.torproject.org/pipermail/tor-
 project/2019-September/002485.html

 next step: host shutdown and retirement procedure, in 30 days.

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

Re: [tor-bugs] #31684 [Core Tor/Tor]: Add control port GETINFO support for dumping the local consensus

[Tor Bug Tracker & Wiki]

#31684: Add control port GETINFO support for dumping the local consensus
---+
 Reporter:  asn|  Owner:  (none)
 Type:  task   | Status:  new
 Priority:  Medium |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  control-port easy  |  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:
---+

Comment (by ltbringer):

 https://github.com/torproject/tor/pull/1328

 This adds `GETINFO dir/status-vote/microdesc/consensus`

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: 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 [Circumvention/Snowflake]: 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:  closed
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tor-spec |  Actual Points:
Parent ID:   | Points:
 Reviewer:  phw  |Sponsor:
-+
Changes (by cohosh):

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


Comment:

 Merged in `b29b49fc1c`

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

Re: [tor-bugs] #31760 [Internal Services/Service - trac]: swati needs a trac account

[Tor Bug Tracker & Wiki]

#31760: swati needs a trac account
--+-
 Reporter:  gaba  |  Owner:  qbi
 Type:  task  | Status:  new
 Priority:  High  |  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by qbi):

 Please just direct her to
 https://trac.torproject.org/projects/tor/register
 She needs to fill in a username and an email address. Probably a CAPTCHA
 appears and needs to be solved and trac sends an email to verify the
 address. After this is done, she can login and use our trac.

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

Re: [tor-bugs] #31760 [Internal Services/Service - trac]: swati needs a trac account

[Tor Bug Tracker & Wiki]

#31760: swati needs a trac account
--+-
 Reporter:  gaba  |  Owner:  qbi
 Type:  task  | Status:  new
 Priority:  High  |  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by arma):

 She can make a trac account on her own -- that's how people make trac
 accounts.

 Once it exists, anybody in the GRP_admin group (including you, gaba) can
 add her to some of the groups, so using trac is more fun.

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

Re: [tor-bugs] #28996 [Applications/Tor Browser]: Tor Browser on Windows creates a file in %APPDATA%\Microsoft\Windows\Recent\CustomDestinations containing the Tor Browser install location

[Tor Bug Tracker & Wiki]

#28996: Tor Browser on Windows creates a file in
%APPDATA%\Microsoft\Windows\Recent\CustomDestinations containing the Tor
Browser install location
+--
 Reporter:  pospeselr   |  Owner:
|  pospeselr
 Type:  defect  | Status:  assigned
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorBrowserTeam201901, BugSmashFund  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by pospeselr):

 * keywords:  TorBrowserTeam201901 => TorBrowserTeam201901, BugSmashFund


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

Re: [tor-bugs] #28810 [Applications/Tor Browser]: Have tor operate on different ports by default for alpha, release and nightly Tor Browser builds

[Tor Bug Tracker & Wiki]

#28810: Have tor operate on different ports by default for alpha, release and
nightly Tor Browser builds
--+---
 Reporter:  pospeselr |  Owner:  pospeselr
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  BugSmashFund  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by pospeselr):

 * keywords:   => BugSmashFund


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31760 [Internal Services/Service - trac]: swati needs a trac account

[Tor Bug Tracker & Wiki]

#31760: swati needs a trac account
--+-
 Reporter:  gaba  |  Owner:  qbi
 Type:  task  | Status:  new
 Priority:  High  |  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 Hi!

 Swati, our technical writer for the google season of docs is in needs of a
 trac account. Can somebody create one for her? Her email is  swati.kgp13
 at gmail.

 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] #31564 [Applications/Tor Browser]: Android bundles based on ESR 68 are not built reproducibly anymore

[Tor Bug Tracker & Wiki]

#31564: Android bundles based on ESR 68 are not built reproducibly anymore
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-9.0-must-alpha,  |  Actual Points:
  TorBrowserTeam201909R, GeorgKoppen201909   |
Parent ID:  #30324   | Points:  5
 Reviewer:   |Sponsor:
-+-
Changes (by boklm):

 * keywords:  tbb-9.0-must-alpha, TorBrowserTeam201909, GeorgKoppen201909 =>
 tbb-9.0-must-alpha, TorBrowserTeam201909R, GeorgKoppen201909


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31759 [Core Tor/Tor]: Make "annotate_ifdef_directives" script comply with line-width limits

[Tor Bug Tracker & Wiki]

#31759: Make "annotate_ifdef_directives" script comply with line-width limits
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  042-should
Actual Points:|  Parent ID:  #31713
   Points:|   Reviewer:
  Sponsor:|
--+
 Right now, our annotate_ifdef_directives script generates output that is
 wider than 80 columns.  This is okay for now, when we're applying it by
 hand, but won't be okay in the long run, when we eventually want to have
 autostyle run before every commit.

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

Re: [tor-bugs] #31192 [Applications/Tor Browser]: TBA - Support x86_64 target

[Tor Bug Tracker & Wiki]

#31192: TBA - Support x86_64 target
-+-
 Reporter:  cypherpunks  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-rbm, ff68-esr,   |  Actual Points:
  GeorgKoppen201907, TorBrowserTeam201909|
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor44-can
-+-

Comment (by eighthave):

 FYI, I think this is relevant, I got 64-bit builds going in @n8fr8's
 ''tor-android'' which is used to provide Tor binaries for Orbot:
 https://gitlab.com/eighthave/tor-android  I'm working on finalizing that,
 and getting merged there.

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

Re: [tor-bugs] #31718 [Internal Services/Tor Sysadmin Team]: Update DNS records for .ooni.torproject.org domains

[Tor Bug Tracker & Wiki]

#31718: Update DNS records for .ooni.torproject.org domains
-+-
 Reporter:  hellais  |  Owner:  anarcat
 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 => anarcat
 * status:  new => assigned


Comment:

 we agreed that we'd add a CNAME record and keep the CNAMEs until may 7th
 2020, at which point they'd turn into HTTP redirects. we'll do this
 tomorrow at 1200 EDT (1600 UTC).

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

Re: [tor-bugs] #31483 [Core Tor/Tor]: token_bucket_ctr_adjust() does not convert rate to step

[Tor Bug Tracker & Wiki]

#31483: token_bucket_ctr_adjust() does not convert rate to step
--+
 Reporter:  teor  |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Very High |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  042-must  |  Actual Points:
Parent ID:| Points:  0.5
 Reviewer:  asn   |Sponsor:  Sponsor31-must
--+
Changes (by nickm):

 * reviewer:   => asn


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

Re: [tor-bugs] #31483 [Core Tor/Tor]: token_bucket_ctr_adjust() does not convert rate to step

[Tor Bug Tracker & Wiki]

#31483: token_bucket_ctr_adjust() does not convert rate to step
--+
 Reporter:  teor  |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Very High |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  042-must  |  Actual Points:
Parent ID:| Points:  0.5
 Reviewer:|Sponsor:  Sponsor31-must
--+
Changes (by nickm):

 * owner:  dgoulet => nickm
 * 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] #31107 [Core Tor/Tor]: channel: channel_tls_handle_cell() CELL_VERSIONS code reached

[Tor Bug Tracker & Wiki]

#31107: channel: channel_tls_handle_cell() CELL_VERSIONS code reached
-+-
 Reporter:  dgoulet  |  Owner:  nickm
 Type:  defect   | Status:
 |  accepted
 Priority:  Very High|  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, tor-channel security  |  Actual Points:
  crash 042-must |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

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


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

Re: [tor-bugs] #10416 [Core Tor/Tor]: Tor won't start on Windows when path contains non-ascii characters

[Tor Bug Tracker & Wiki]

#10416: Tor won't start on Windows when path contains non-ascii characters
-+-
 Reporter:  iktsuarpok   |  Owner:  ahf
 Type:  defect   | Status:
 |  assigned
 Priority:  High |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.3.25
 Severity:  Major| Resolution:
 Keywords:  tor-client, windows, unicode,|  Actual Points:
  win32, tbb-needs, 042-should   |
Parent ID:  #25729   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by ahf):

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


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

Re: [tor-bugs] #31091 [Core Tor/Tor]: Bug stracktrace when pluggable transport cannot bind to port

[Tor Bug Tracker & Wiki]

#31091: Bug stracktrace when pluggable transport cannot bind to port
--+
 Reporter:  s7r   |  Owner:  ahf
 Type:  defect| Status:  assigned
 Priority:  Very High |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  042-must  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by ahf):

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


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

Re: [tor-bugs] #28966 [Core Tor/Tor]: HSv3 client auth insufficiently documented (was: HiddenServiceAuthorizeClient incompatible)

[Tor Bug Tracker & Wiki]

#28966: HSv3 client auth insufficiently documented (was:
HiddenServiceAuthorizeClient incompatible)
-+-
 Reporter:  roo  |  Owner:  asn
 Type:  defect   | Status:
 |  assigned
 Priority:  High |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.5.6-rc
 Severity:  Minor| Resolution:
 Keywords:  tor-hs, client-auth, hsv3,   |  Actual Points:
  postfreeze-ok, network-team-roadmap-october,   |
  042-should |
Parent ID:  #14389   | Points:  0.5
 Reviewer:   |Sponsor:
 |  Sponsor27-must
-+-
Changes (by asn):

 * milestone:  Tor: 0.4.2.x-final => Tor: 0.4.3.x-final


Comment:

 Pushing to 043. Too many things happening.

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

Re: [tor-bugs] #31703 [Internal Services/Service - dist]: Downloading Tor Browser from 2620:0:6b0:b:225:dada:19:1 is painfully slow

[Tor Bug Tracker & Wiki]

#31703: Downloading Tor Browser from 2620:0:6b0:b:225:dada:19:1 is painfully 
slow
--+-
 Reporter:  pospeselr |  Owner:  anarcat
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - dist  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by anarcat):

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


Comment:

 forgot to close 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] #31657 [Core Tor/Tor]: Rephrase "missing descriptors" notice log to be less confusing

[Tor Bug Tracker & Wiki]

#31657: Rephrase "missing descriptors" notice log to be less confusing
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.3.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  consider-backport-after-0421, fast-  |  Actual Points:  0.1
  fix, log, tor-guard, tor-bridge, tor-client,   |
  BugSmashFund, 042-should 041-backport? |
  040-backport? 035-backport?|
Parent ID:  #21969   | Points:  0.1
 Reviewer:  ahf  |Sponsor:
-+-
Changes (by ahf):

 * reviewer:  asn => ahf


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

Re: [tor-bugs] #28942 [Circumvention/Snowflake]: Evaluate pion WebRTC

[Tor Bug Tracker & Wiki]

#28942: Evaluate pion WebRTC
+--
 Reporter:  backkem |  Owner:  cohosh
 Type:  enhancement | Status:  accepted
 Priority:  Medium  |  Milestone:
Component:  Circumvention/Snowflake |Version:
 Severity:  Normal  | Resolution:
 Keywords:  anti-censorship-roadmap-august  |  Actual Points:
Parent ID:  | Points:  5
 Reviewer:  |Sponsor:
|  Sponsor28-must
+--

Comment (by cohosh):

 Replying to [comment:59 dcf]:
 >
 > Here is the build. It's working!
 >
 >  * [https://gitweb.torproject.org/user/dcf/tor-browser-build.git/log/?h
 =pion-webrtc=f52281ae5bca107414a5292e74e2f1eca0608a3b pion-webrtc]
 branch
 >  * https://people.torproject.org/~dcf/pt-bundle/tor-browser-pion-
 webrtc-20190905-f52281ae5/
 >
 I built tor browser using this branch and got the following sums:
 {{{
 a95656c0a1d220f51ebb7c02264ca14a6dfcaf1f49f9c1eb2b100b8912202fbb  tor-
 browser-9.0a4-linux-x86_64-95fcd7/mar-tools-linux64.zip
 313467567d9f85b11f9fc075f2a450d0fa5daa575a17635a0852fbdecbe7163f  tor-
 browser-9.0a4-linux-x86_64-95fcd7/tor-browser-linux64-9.0a4_en-US.tar.xz
 f2e28bd473b7fc21dc3a4ce0b1c4931de1cc2bbba643cb790a94cd23b5f8a44f  tor-
 browser-9.0a4-linux-x86_64-95fcd7/tor-browser-linux64-debug.tar.xz
 05be2469134ab700ff06a464eaef4c5ae95252810158c6490ab1830d65c1e5df  tor-
 browser-9.0a4-linux-x86_64-95fcd7/tor-linux64-debug.tar.xz
 3c44f8039334230540ca09eeea7b478eb6d2b94186b4f15f65b39d5b5afa8654  tor-
 browser-9.0a4-linux-i686-7088f9/mar-tools-linux32.zip
 b154ec37b41f515a4618a4f2602c5fca082e7cbeb8c14ef6cc85788c156cd200  tor-
 browser-9.0a4-linux-i686-7088f9/tor-browser-linux32-9.0a4_en-US.tar.xz
 08d05d0573f41f55d95bcca4c61374491469ddde220ddd51d9f32e754c395a16  tor-
 browser-9.0a4-linux-i686-7088f9/tor-browser-linux32-debug.tar.xz
 0261e8109dc380f197a24e3e4799182916a060065a97bf66926f7e3f01a0523b  tor-
 browser-9.0a4-linux-i686-7088f9/tor-linux32-debug.tar.xz
 aaf162ecc77e214c04ce78c4eb68ed2f7d239efbc6ad61daeb8af9f9e8d41018  tor-
 browser-9.0a4-osx-x86_64-bae6f1/TorBrowser-9.0a4-osx64_en-US.dmg
 659e4e31ac2875ff24f667040f13a93caaddf2be73a742229bc64c6552af55dd  tor-
 browser-9.0a4-osx-x86_64-bae6f1/mar-tools-mac64.zip
 7d5a8353bde39d0bafb40d9c03eb4f2b28cddd8306bf429e811f1caa9435189c  tor-
 browser-9.0a4-windows-i686-bc4573/mar-tools-win32.zip
 27bee134cf8f4c700729c6d4662bee2c23db3ddf27164e878592091e9c5d6fc8  tor-
 browser-9.0a4-windows-i686-bc4573/torbrowser-install-9.0a4_en-US.exe
 f3fadbac79c94e22eacb5902582bec5dbd303862768fc07c8d4f1bba469a8c5c  tor-
 browser-9.0a4-windows-x86_64-745fee/mar-tools-win64.zip
 ed2a538d8e4b1aecc555e6b1683a93f4096184015549ed9992526b43759f0c9c  tor-
 browser-9.0a4-windows-x86_64-745fee/torbrowser-install-win64-9.0a4_en-
 US.exe
 }}}

 Weirdly the sum for `TorBrowser-9.0a4-osx64_en-US.dmg` differs, but all
 others look the same.

 I couldn't build for android due to #31293

 I'm going to update the version of pion used here since we had our fixes
 upstreamed.

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

Re: [tor-bugs] #31448 [Applications/Tor Browser]: gold and lld break linking 32bit Linux bundles we need to resort to bfd

[Tor Bug Tracker & Wiki]

#31448: gold and lld break linking 32bit Linux bundles we need to resort to bfd
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-rbm, ff68-esr, tbb-9.0-must- |  Actual Points:
  alpha, TorBrowserTeam201909R   |
Parent ID:  #30321   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor44-can
-+-
Changes (by boklm):

 * keywords:  tbb-rbm, ff68-esr, tbb-9.0-must-alpha, TorBrowserTeam201909 =>
 tbb-rbm, ff68-esr, tbb-9.0-must-alpha, TorBrowserTeam201909R
 * status:  new => needs_review


Comment:

 Replying to [comment:9 boklm]:
 > Replying to [comment:8 gk]:
 > > boklm: are you building the browser part with commit
 4458b4e8a09aaa759f1735b36aec860aa61f3ba7 applied? (i.e. after the `tor-
 browser` patch for #31621 landed) I ask, because that's exactly the error
 you would get if the nodejs problem was not solved.
 >
 > Oh, I probably did an alpha build by mistake instead of nightly. I will
 try again doing a nightly.

 This was indeed the issue.

 In branch `bug_31448_v5` I made a patch disabling debug symbols and
 switching back to `ld.gold`:
 https://gitweb.torproject.org/user/boklm/tor-browser-
 build.git/commit/?h=bug_31448_v5=8cc9eaf22abf0c9d98b88bb60aaa1476e4a6555c

 I did builds on two machines with this patch to see that is is also fixing
 #31618.

 However I did not find why it is failing with debug symbols.

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

Re: [tor-bugs] #31652 [Core Tor/Tor]: hs-v3: Service circuit retry limit should not close a valid circuit

[Tor Bug Tracker & Wiki]

#31652: hs-v3: Service circuit retry limit should not close a valid circuit
-+-
 Reporter:  dgoulet  |  Owner:  neel
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, tor-circuit, 042-should  |  Actual Points:
Parent ID:  #30200   | Points:  0.1
 Reviewer:  asn  |Sponsor:
 |  Sponsor27-must
-+-
Changes (by asn):

 * reviewer:  dgoulet => asn


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

Re: [tor-bugs] #31720 [Applications/Tor Browser]: Address bar auto-complete is broken on Android

[Tor Bug Tracker & Wiki]

#31720: Address bar auto-complete is broken on Android
-+-
 Reporter:  sysrqb   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, ff68-esr,|  Actual Points:
  TorBrowserTeam201909   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by sysrqb):

 * points:   => 1


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

Re: [tor-bugs] #31538 [Applications/Tor Browser]: Windows bundles based on ESR 68 are not built reproducibly

[Tor Bug Tracker & Wiki]

#31538: Windows bundles based on ESR 68 are not built reproducibly
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  tbb-rbm, ff68-esr, tbb-9.0-must- |  Actual Points:
  alpha, TorBrowserTeam201909R,  |
  GeorgKoppen201909  |
Parent ID:  #30322   | Points:  2
 Reviewer:   |Sponsor:
-+-

Comment (by boklm):

 Replying to [comment:21 gk]:
 > `bug_31538_v2` (https://gitweb.torproject.org/user/gk/tor-browser-
 build.git/log/?h=bug_31538_v2) has wo patches for review (on top of
 #31732), which should fix the problem. I rebuilt the macOS bundles as well
 and they are still matching. Doing currently Linux.

 The patches look good to me. I am currently doing builds to confirm that
 it is fixing the issue.

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

Re: [tor-bugs] #31653 [Core Tor/Tor]: Padding cells sent with 0ms delay cause circuit failures

[Tor Bug Tracker & Wiki]

#31653: Padding cells sent with 0ms delay cause circuit failures
-+-
 Reporter:  pulls|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.5
 Severity:  Normal   | Resolution:
 Keywords:  wtf-pad circpad-researchers-want |  Actual Points:
  042-should |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  wtf-pad circpad-researchers-want => wtf-pad circpad-
 researchers-want 042-should


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

Re: [tor-bugs] #31721 [Applications/Tor Browser]: Onboarding screen is not shown immediately on Android

[Tor Bug Tracker & Wiki]

#31721: Onboarding screen is not shown immediately on Android
-+-
 Reporter:  sysrqb   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, ff68-esr,|  Actual Points:
  TorBrowserTeam201909   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by sysrqb):

 * points:   => 1


Comment:

 But, hopefully only `.5` if it doesn't require rewriting the whole thing.

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

Re: [tor-bugs] #31295 [Webpages/Website]: please server Tor signature files with Content-Disposition that encourages a download rather than inline viewing

[Tor Bug Tracker & Wiki]

#31295: please server Tor signature files with Content-Disposition that 
encourages
a download rather than inline viewing
--+--
 Reporter:  dkg   |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by anarcat):

 it seems strange to make people download a text file instead of displaying
 it. after all, a `.asc` file is exactly *designed* to be user-readable and
 transported as text.

 if we want users to download a blob, why don't we use the standard
 extension (as far as such a thing exists) which is `.sig`?

 {{{
 anarcat@curie:~(master)$ grep pgp /etc/mime.types
 application/pgp-encrypted   pgp
 application/pgp-keyskey
 application/pgp-signature   sig
 }}}

 (you'll note that .asc is not listed there, interestingly...)

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

Re: [tor-bugs] #31295 [Webpages/Website]: please server Tor signature files with Content-Disposition that encourages a download rather than inline viewing

[Tor Bug Tracker & Wiki]

#31295: please server Tor signature files with Content-Disposition that 
encourages
a download rather than inline viewing
--+--
 Reporter:  dkg   |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by sysrqb):

 * cc: anarcat (added)


Comment:

 I wonder if this requires a configuration change on the webserver (instead
 of the webpage or templating). If it is, then the component of this ticket
 can be changed, 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] #31758 [Internal Services/Tor Sysadmin Team]: upgrade postfix configurations to stretch/buster

[Tor Bug Tracker & Wiki]

#31758: upgrade postfix configurations to stretch/buster
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:  closed
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Major| Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

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


Comment:

 fix on rouyi, perdulce and carinatum. i deployed the changes to postfix
 everywhere with puppet after a test with eugeni.

 i think this is mostly fixed now, although we still need to enabled
 `postlogd` in buster, but that's incompatible with stretch, unfortunately.
 this can be fixed when we add a `postfix_version` fact or when we upgrade
 all to buster. since things seem to be working fine without it, i prefer
 the latter.

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

Re: [tor-bugs] #31564 [Applications/Tor Browser]: Android bundles based on ESR 68 are not built reproducibly anymore

[Tor Bug Tracker & Wiki]

#31564: Android bundles based on ESR 68 are not built reproducibly anymore
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-9.0-must-alpha,  |  Actual Points:
  TorBrowserTeam201909, GeorgKoppen201909|
Parent ID:  #30324   | Points:  5
 Reviewer:   |Sponsor:
-+-
Changes (by sisbell):

 * status:  new => needs_review


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

Re: [tor-bugs] #31564 [Applications/Tor Browser]: Android bundles based on ESR 68 are not built reproducibly anymore

[Tor Bug Tracker & Wiki]

#31564: Android bundles based on ESR 68 are not built reproducibly anymore
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-9.0-must-alpha,  |  Actual Points:
  TorBrowserTeam201909, GeorgKoppen201909|
Parent ID:  #30324   | Points:  5
 Reviewer:   |Sponsor:
-+-

Comment (by sisbell):

 I did the apktool decompile/decompile approach. The apktool that can be
 added in config/arch_deps is an old version of apktool with a bug


 {{{
 I: Using Apktool 2.2.1-dirty on tor-browser-unsigned-unaligned.apk
 I: Loading resource table...
 I: Decoding AndroidManifest.xml with resources...
 I: Loading resource table from file:
 /home/rbm/.local/share/apktool/framework/1.apk
 I: Regular manifest package...
 I: Decoding file-resources...
 I: Decoding values */* XMLs...
 Exception in thread "main" java.lang.NullPointerException
 at
 
brut.androlib.res.data.value.ResStyleValue.serializeToResValuesXml(ResStyleValue.java:58)
 at
 
brut.androlib.res.AndrolibResources.generateValuesFile(AndrolibResources.java:516)
 at
 brut.androlib.res.AndrolibResources.decode(AndrolibResources.java:267)
 at brut.androlib.Androlib.decodeResourcesFull(Androlib.java:132)
 at brut.androlib.ApkDecoder.decode(ApkDecoder.java:108)
 at brut.apktool.Main.cmdDecode(Main.java:166)
 at brut.apktool.Main.main(Main.java:81)
 }}}

 https://github.com/iBotPeaches/Apktool/issues/1399

 So I'm using apktool 2.4.0, downloading it as part of the build.

 When re-zipping the file, I was getting some zip entry extra field flags
 that would change each build. I'm not exactly sure what the extra field
 info was as its platform specific and not standard fields like timestamp..
 I removed these using the -X option. After that, multiple builds of the
 apk result in the same checksum. I'll need someone to verify that the
 checksum matches across different build machine OSes.

 There is some room to cleanup the build further if it is verified to fix
 this bug.

 The code is at https://github.com/sisbell/tor-browser-
 build/commit/694de9f7431b022cf974aa5bd8b6150e59f0bcbf

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

Re: [tor-bugs] #31757 [Core Tor/Tor]: test_parseconf.sh: apparently not reliable on Appveyor

[Tor Bug Tracker & Wiki]

#31757: test_parseconf.sh: apparently not reliable on Appveyor
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:  accepted
 Priority:  High |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-ci 042-should asn-merge  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  ahf  |Sponsor:  Sponsor31-can
-+-
Changes (by nickm):

 * keywords:  tor-ci 042-must asn-merge => tor-ci 042-should asn-merge


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

Re: [tor-bugs] #30957 [Applications/Tor Browser]: Allow '.asc' files to be downloaded using Tor browser (PGP ascii)

[Tor Bug Tracker & Wiki]

#30957: Allow '.asc' files to be downloaded using Tor browser (PGP ascii)
--+---
 Reporter:  torlove   |  Owner:  tbb-team
 Type:  enhancement   | Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by sysrqb):

 Replying to [comment:7 pili]:
 > Even though one is to do with how the browser handles the files and the
 other one is about how we serve the files, I wonder if #31295 is related
 to this also...

 Yes, I agree #31295 is the correct bug here. Thanks for noticing that!

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

Re: [tor-bugs] #31757 [Core Tor/Tor]: test_parseconf.sh: apparently not reliable on Appveyor

[Tor Bug Tracker & Wiki]

#31757: test_parseconf.sh: apparently not reliable on Appveyor
---+---
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  accepted
 Priority:  High   |  Milestone:  Tor:
   |  0.4.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-ci 042-must asn-merge  |  Actual Points:
Parent ID: | Points:
 Reviewer:  ahf|Sponsor:  Sponsor31-can
---+---
Changes (by nickm):

 * status:  reopened => 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] #31757 [Core Tor/Tor]: test_parseconf.sh: apparently not reliable on Appveyor

[Tor Bug Tracker & Wiki]

#31757: test_parseconf.sh: apparently not reliable on Appveyor
---+---
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  reopened
 Priority:  High   |  Milestone:  Tor:
   |  0.4.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-ci 042-must asn-merge  |  Actual Points:
Parent ID: | Points:
 Reviewer:  ahf|Sponsor:  Sponsor31-can
---+---
Changes (by nickm):

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


Comment:

 Reopening because the patch doesn't actually '''fix''' the test failure:
 it just makes the test failure not break the build on Windows.

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

Re: [tor-bugs] #30957 [Applications/Tor Browser]: Allow '.asc' files to be downloaded using Tor browser (PGP ascii)

[Tor Bug Tracker & Wiki]

#30957: Allow '.asc' files to be downloaded using Tor browser (PGP ascii)
--+--
 Reporter:  torlove   |  Owner:  tbb-team
 Type:  enhancement   | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  wontfix
 Keywords:  tbb-mobile|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by sysrqb):

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


Comment:

 Replying to [comment:6 torlove]:
 > Thanks for above responses. It's not good behaviour. It doesn't make
 sense and makes Fennec, and by extension Tor, less user friendly.

 I agree this is not user friendly, unfortunately I highly doubt this will
 be fixed in Fennec. If there is any hope of fixing this in Firefox on
 Android then we should look at Firefox Preview (Fenix) and advocate for
 this functionality there.

 I'm going to close this as wontfix because we'll be migrating to Fenix in
 the near future, and implementing this in the current browser will require
 significant time which won't yield much benefit. We can look at this again
 in the future if Fenix doesn't provide a good experience - but #31295
 should solve this for `torproject.org` signatures, at least.

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

Re: [tor-bugs] #31679 [Core Tor/Tor]: Make checkShellScripts.sh handle path errors better

[Tor Bug Tracker & Wiki]

#31679: Make checkShellScripts.sh handle path errors better
+--
 Reporter:  teor|  Owner:  teor
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:  Tor:
|  0.4.2.x-final
Component:  Core Tor/Tor|Version:  Tor:
|  unspecified
 Severity:  Normal  | Resolution:  fixed
 Keywords:  testing, 042-should, asn-merge  |  Actual Points:  0
Parent ID:  | Points:  0
 Reviewer:  nickm   |Sponsor:
+--
Changes (by asn):

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


Comment:

 Merged!

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

Re: [tor-bugs] #31677 [Core Tor/Tor]: Add usage help option to git scripts

[Tor Bug Tracker & Wiki]

#31677: Add usage help option to git scripts
---+---
 Reporter:  teor   |  Owner:  teor
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.2.x-final
Component:  Core Tor/Tor   |Version:  Tor:
   |  unspecified
 Severity:  Normal | Resolution:  fixed
 Keywords:  git-scripts, dev-tools, asn-merge  |  Actual Points:  0.1
Parent ID: | Points:  0.1
 Reviewer:  nickm  |Sponsor:
   |  Sponsor31-can
---+---
Changes (by asn):

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


Comment:

 Cool! Merged!

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

Re: [tor-bugs] #31757 [Core Tor/Tor]: test_parseconf.sh: apparently not reliable on Appveyor

[Tor Bug Tracker & Wiki]

#31757: test_parseconf.sh: apparently not reliable on Appveyor
---+---
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  closed
 Priority:  High   |  Milestone:  Tor:
   |  0.4.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  tor-ci 042-must asn-merge  |  Actual Points:
Parent ID: | Points:
 Reviewer:  ahf|Sponsor:  Sponsor31-can
---+---
Changes (by asn):

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


Comment:

 Merged!

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

Re: [tor-bugs] #23024 [Applications/Tor Browser]: Flags to increase hardening on Windows

[Tor Bug Tracker & Wiki]

#23024: Flags to increase hardening on Windows
---+---
 Reporter:  arthuredelstein|  Owner:  tbb-team
 Type:  defect | Status:
   |  needs_revision
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201711, tbb-rbm  |  Actual Points:
Parent ID:  #21448 | Points:
 Reviewer: |Sponsor:
---+---

Comment (by tom):

 Replying to [comment:13 cypherpunks]:
 > What about `--icf=all` automatically? https://github.com/llvm/llvm-
 project/blob/d0f63f83e7c5c6fc11e964f848d1496234695182/lld/MinGW/Driver.cpp#L265

 Haven't heard of it; but https://clang.llvm.org/docs/UsersManual.html says
 that the arguements needed for ICF to work (-faddrsig) are ELF only...


 > > --forceinteg - not applicablt to clang/lld
 > What do you mean? Just disabled by default: https://github.com/llvm
 /llvm-
 project/blob/ee6fbebbaff5af0a0fbe58a0e33ef191340223ea/lld/COFF/Driver.cpp#L1507

 Ahhah; I was wrong. So it looks like this sets
 IMAGE_DLLCHARACTERISTICS_FORCE_INTEGRITY which requires a file be signed
 before it's loaded.

 Frankly it seems kind of useless to me, an attacker who can modify the dll
 would invalidate the signature; but they could just strip the signature
 and the unset the flag. But if it cost nothing, I'd say sure, flip it: but
 I'm not sure which Tor Browser releases we Authenticode sign; which this
 would require.

 > > --no-seh - set by lld automatically ​https://reviews.llvm.org/D41252
 (but this would be good to confirm manually
 > What about `--safeseh` automatically? https://github.com/llvm/llvm-
 project/blob/ee6fbebbaff5af0a0fbe58a0e33ef191340223ea/lld/COFF/Driver.cpp#L1617

 Oh good catch: on by default except for MinGW.  We should investigate why
 that is and if we can enable it.


 > > --tsaware - I'm not sure but I really hope that this is completely
 unneeded by now.
 > Because it is enabled and should be enabled by default, you mean?
 https://github.com/llvm/llvm-
 project/blob/ee6fbebbaff5af0a0fbe58a0e33ef191340223ea/lld/COFF/Driver.cpp#L1513

 https://docs.microsoft.com/en-us/cpp/build/reference/tsaware-create-
 terminal-server-aware-application?view=vs-2019 "When an application is not
 Terminal Server aware (also known as a legacy application), Terminal
 Server makes certain modifications to the legacy application to make it
 work properly in a multiuser environment. For example, Terminal Server
 will create a virtual Windows folder, such that each user gets a Windows
 folder instead of getting the system's Windows directory. This gives users
 access to their own INI files. In addition, Terminal Server makes some
 adjustments to the registry for a legacy application. These modifications
 slow the loading of the legacy application on Terminal Server."

 I had hoped that all this nonsense was not needed/performed in Windows 10
 or at least the compiler set the flag automatically. The code makes it
 seem like it does not; but I can't find the flag in Firefox's code, which
 implies that it would not be setting it either...

 More investigation needed, specifically what Firefox sets and if this has
 any effect on Windows 7+

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

Re: [tor-bugs] #23024 [Applications/Tor Browser]: Flags to increase hardening on Windows

[Tor Bug Tracker & Wiki]

#23024: Flags to increase hardening on Windows
---+---
 Reporter:  arthuredelstein|  Owner:  tbb-team
 Type:  defect | Status:
   |  needs_revision
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201711, tbb-rbm  |  Actual Points:
Parent ID:  #21448 | Points:
 Reviewer: |Sponsor:
---+---

Comment (by cypherpunks):

 What about `--icf=all` automatically? https://github.com/llvm/llvm-
 project/blob/d0f63f83e7c5c6fc11e964f848d1496234695182/lld/MinGW/Driver.cpp#L265
 > --forceinteg - not applicablt to clang/lld
 What do you mean? Just disabled by default: https://github.com/llvm/llvm-
 project/blob/ee6fbebbaff5af0a0fbe58a0e33ef191340223ea/lld/COFF/Driver.cpp#L1507
 > --no-seh - set by lld automatically ​https://reviews.llvm.org/D41252
 (but this would be good to confirm manually
 What about `--safeseh` automatically? https://github.com/llvm/llvm-
 project/blob/ee6fbebbaff5af0a0fbe58a0e33ef191340223ea/lld/COFF/Driver.cpp#L1617
 > --tsaware - I'm not sure but I really hope that this is completely
 unneeded by now.
 Because it is enabled and should be enabled by default, you mean?
 https://github.com/llvm/llvm-
 project/blob/ee6fbebbaff5af0a0fbe58a0e33ef191340223ea/lld/COFF/Driver.cpp#L1513

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

Re: [tor-bugs] #31758 [Internal Services/Tor Sysadmin Team]: upgrade postfix configurations to stretch/buster

[Tor Bug Tracker & Wiki]

#31758: upgrade postfix configurations to stretch/buster
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Major| Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

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


Comment:

 Looking for the magic string (`bad command startup -- throttling`) in
 logs:

 {{{
 cumin  -p 0 -b 10 -o txt  '*' 'grep "bad command startup -- throttling"
 /var/log/mail.log'
 }}}

 also yields a match on rouyi and perdulce, so i'll head there next for a
 hotfix.

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

Re: [tor-bugs] #28005 [HTTPS Everywhere/EFF-HTTPS Everywhere]: Officially support onions in HTTPS-Everywhere

[Tor Bug Tracker & Wiki]

#28005: Officially support onions in HTTPS-Everywhere
-+-
 Reporter:  asn  |  Owner:  legind
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  HTTPS Everywhere/EFF-HTTPS   |Version:
  Everywhere |
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs https-everywhere tor-ux   |  Actual Points:
  network-team-roadmap-november  |
Parent ID:  #30029   | Points:  20
 Reviewer:   |Sponsor:
 |  Sponsor27-must
-+-

Comment (by asn):

 Here are some notes from the plans we made in Stockholm in the meeting
 between
 me, antonela, sysrqb, redshiftzero, geko and dgoulet:

 

 Scope of work:
 - First iteration will include onion rules for securedrop websites
   (e.g. `nytimes.securedrop.tor.onion -> nyttips4bmquxfzw.onion`)
 - Need to add a toolbar button in the ffox UI to show that a redirect
 happened
 - Rewrite URL in URL bar (only show the human-readable url)
 - Add support for viewing rulesets (?)
 - See how update channels work and whether we should disable them or not.

 Out of scope:
 - First iteration will not allow people to easily add their own rules

 TLD scheme:
 - Three options for tld scheme:

   a) nytimes.securedrop.onion   (ambiguous and probably unsafe)
   b) nytimes.securedrop.tor.onion   (safe but bad UX)
   c) nytimes.securedrop.tor(good UX but DNS leaks in other browsers)

   We decided to ditch (a) from our options and do either (b) or (c). (b)
 is the
   safest and we should probably roll with that (?).

 FPF plan:
 - FPF will change their securedrop directory to include ".tor.onion" links
 for
   their various instances.

 Metadata:
 - 3 months of work are enough

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

Re: [tor-bugs] #30304 [Applications/Tor Browser]: Browser locale can be obtained via DTD strings

[Tor Bug Tracker & Wiki]

#30304: Browser locale can be obtained via DTD strings
-+-
 Reporter:  acat |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_revision
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff68-esr, tbb-fingerprinting-|  Actual Points:  2
  locale, TorBrowserTeam201909   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor44-can
-+-
Changes (by acat):

 * actualpoints:   => 2


Comment:

 Yes, let's see if it gets reviewed/accepted 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] #31743 [Internal Services/Tor Sysadmin Team]: SMTP on carinatum

[Tor Bug Tracker & Wiki]

#31743: SMTP on carinatum
-+-
 Reporter:  atagar   |  Owner:  anarcat
 Type:  defect   | Status:  closed
 Priority:  Very High|  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:

 This is the problem:

 {{{
 Sep 16 15:21:45 carinatum/carinatum postfix/smtpd[18138]: fatal: in
 parameter smtpd_relay_restrictions or smtpd_recipient_restrictions,
 specify at least one working instance of: reject_unauth_destination,
 defer_unauth_destination, reject, defer, defer_if_permit or
 check_relay_domains
 }}}

 {{{
 root@carinatum:/etc/postfix# postconf smtpd_relay_restrictions
 smtpd_relay_restrictions = ${{$compatibility_level} < {1} ? {} :
 {permit_mynetworks, permit_sasl_authenticated, defer_unauth_destination}}
 root@carinatum:/etc/postfix# postconf smtpd_recipient_restrictions
 smtpd_recipient_restrictions =
 root@carinatum:/etc/postfix# postconf compatibility_level
 compatibility_level = 0
 }}}

 This is the last change to Postfix's `main.cf` before july 8th:

 {{{
 commit 0dbf5557fc3dec867c63482b0255ba9acffa4a29
 Author: Peter Palfrader 
 Date:   Thu Jun 27 09:02:42 2019 +0200

 set unverified_recipient_reject_code to 550, this should address
 #30911

 diff --git a/modules/postfix/templates/main.cf.erb
 b/modules/postfix/templates/m
 ain.cf.erb
 index 4b789ca5..f713d407 100644
 --- a/modules/postfix/templates/main.cf.erb
 +++ b/modules/postfix/templates/main.cf.erb
 @@ -99,6 +99,7 @@ maximal_queue_lifetime = 7d
  address_verify_map = btree:${data_directory}/verify
  address_verify_negative_refresh_time = 840s
  unverified_sender_reject_code = 450
 +unverified_recipient_reject_code = 550
  address_verify_sender = <>

  <% if @hostname == "eugeni" -%>

 }}}

 I doubt it's related.

 The host *may* have been upgraded to buster in July, however:

 {{{
 Start-Date: 2019-07-09  19:10:31
 Commandline: apt dist-upgrade
 }}}

 So this could be a matter of upgrading the postfix config template to
 buster.

 I fixed this on this specific host by adding `compatibility_level=2` to
 the configuration, but I'll need to check this across the infra to make
 sure we don't have the problem elsewhere. Will open a different ticket on
 this, however (#31743).

 thanks for the report, I hope this fixes it to your satisfaction. :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31758 [Internal Services/Tor Sysadmin Team]: upgrade postfix configurations to stretch/buster

[Tor Bug Tracker & Wiki]

#31758: upgrade postfix configurations to stretch/buster
-+-
 Reporter:  anarcat  |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Major|   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 our postfix configuration as delivered by puppet is pretty old, probably
 pre-stretch. it's generally not a problem until some upgrade breaks
 certain assertions. buster seems to have at least broken one, as described
 in #31743, so it seems it would be a good idea to upgrade our configs
 everywhere.

 first I'll look on all hosts to see if we have this problem elsewhere and
 then I'll cleanup the configs to port to the brave new world...

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

Re: [tor-bugs] #31740 [Applications/Tor Browser]: Review RemoteSettings usages in esr68

[Tor Bug Tracker & Wiki]

#31740: Review RemoteSettings usages in esr68
---+--
 Reporter:  acat   |  Owner:  tbb-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ff68-esr TorBrowserTeam201909  |  Actual Points:
Parent ID: | Points:  0.5
 Reviewer: |Sponsor:
---+--
Changes (by pili):

 * points:   => 0.5


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

Re: [tor-bugs] #31743 [Internal Services/Tor Sysadmin Team]: SMTP on carinatum

[Tor Bug Tracker & Wiki]

#31743: SMTP on carinatum
-+-
 Reporter:  atagar   |  Owner:  anarcat
 Type:  defect   | Status:
 |  assigned
 Priority:  Very High|  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] #31757 [Core Tor/Tor]: test_parseconf.sh: apparently not reliable on Appveyor

[Tor Bug Tracker & Wiki]

#31757: test_parseconf.sh: apparently not reliable on Appveyor
---+---
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  merge_ready
 Priority:  High   |  Milestone:  Tor:
   |  0.4.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-ci 042-must asn-merge  |  Actual Points:
Parent ID: | Points:
 Reviewer:  ahf|Sponsor:  Sponsor31-can
---+---
Changes (by nickm):

 * keywords:  tor-ci 042-must => tor-ci 042-must asn-merge


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

Re: [tor-bugs] #31757 [Core Tor/Tor]: test_parseconf.sh: apparently not reliable on Appveyor

[Tor Bug Tracker & Wiki]

#31757: test_parseconf.sh: apparently not reliable on Appveyor
-+
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:  merge_ready
 Priority:  High |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-ci 042-must  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  ahf  |Sponsor:  Sponsor31-can
-+

Comment (by nickm):

 I've made a squashed branch as `ticket31757_workaround_squashed` . PR at
 https://github.com/torproject/tor/pull/1327

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

Re: [tor-bugs] #31757 [Core Tor/Tor]: test_parseconf.sh: apparently not reliable on Appveyor

[Tor Bug Tracker & Wiki]

#31757: test_parseconf.sh: apparently not reliable on Appveyor
-+
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:  merge_ready
 Priority:  High |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-ci 042-must  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  ahf  |Sponsor:  Sponsor31-can
-+
Changes (by ahf):

 * status:  assigned => merge_ready
 * reviewer:   => ahf


Comment:

 PR looks good.

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

Re: [tor-bugs] #31718 [Internal Services/Tor Sysadmin Team]: Update DNS records for .ooni.torproject.org domains

[Tor Bug Tracker & Wiki]

#31718: Update DNS records for .ooni.torproject.org domains
-+-
 Reporter:  hellais  |  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 anarcat):

 i don't exactly know what the policy is regarding CNAMEs, to be honest. :)
 the best source I know of is this:

 https://help.torproject.org/tsa/doc/naming-scheme/

 ... which outlines the distinction between TPO (torproject.org) and TPN
 (torproject.net) that weasel was refering to. The problem might not be
 CNAMEs per se, but pointing to outside stuff.

 Another thing is that CNAMEs are not a great way to move stuff around,
 because they are transparent to clients. An web browser or crawler will
 not treat a CNAME as "this is now hosted over there", it's just an alias.
 For those kind of transitions, you want to do a HTTP redirect, that is
 respond with a 301 (Moved Permanently) or 302 (Found) status code:

 https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#3xx_Redirection

 Then we can deprecate the *.ooni.tpo namespace and eventually transition
 to ooni.io cleanly.

 This is why I was asking about non-HTTP (and non-HTTPS) clients: those
 redirections will work only for HTTP clients. If you have people using
 this over SSH or Git or whatever non-HTTP protocol, those would break of
 course.

 (Sorry if you already know all of this about HTTP status codes vs CNAMEs,
 but I thought it was useful to get back to the specs to clarify my
 thoughts.)

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

Re: [tor-bugs] #22029 [Core Tor/Tor]: Allow ed25519 keys to be banned in the approved-routers file

[Tor Bug Tracker & Wiki]

#22029: Allow ed25519 keys to be banned in the approved-routers file
-+-
 Reporter:  teor |  Owner:  neel
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  034-triage-20180328, |  Actual Points:
  034-removed-20180328   |
Parent ID:   | Points:  1
 Reviewer:  nickm|Sponsor:
-+-
Changes (by nickm):

 * milestone:  Tor: 0.4.2.x-final => Tor: 0.4.3.x-final


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