Re: [tor-bugs] #32053 [Applications/Tor Browser]: Tor Browser bundles based on Firefox 68 ESR are not reproducible (LLVM optimization issue)

[Tor Bug Tracker & Wiki]

#32053: Tor Browser bundles based on Firefox 68 ESR are not reproducible (LLVM
optimization issue)
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Immediate|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201911, tbb-9.0-must,  |  Actual Points:
  tbb-9.0-issues, tbb-regression,|
  tbb-9.0.1-can, GeorgKoppen201911   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 Replying to [comment:27 alexcrichton]:
 > I just posted a comment on the bug report with a much more minimal test
 case (only a few hundred KB!), it only took many cpu hours to extract :)
 >
 > From here I'm still trying to reduce it further to increase the
 likelihood that someone from LLVM can help fix (I'm not so good at LLVM
 internals). This test case is small enough though that it may be pretty
 reasonable to bisect LLVM itself with. Dealing with a bitcode file across
 that many LLVM revisions may be pretty difficult though, so bisection
 likely won't be trivial.

 Okay, it seems the optimization being the problem here is in -O1, which is
 unfortunate because I had some hope reducing the current -O2 to it could
 be a workaround... I am not sure whether -O0 is worth it. But it might be
 an option if we don't solve the bug until the next planned release.

 I'll set up some bisecting in parallel to your efforts and see whether
 that gets us anywhere. If you get to the problem with `bugpoint` or some
 LLVM dev is helping meanwhile even better. :)

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

Re: [tor-bugs] #32148 [Community/Translations]: "No Script" translations for MK locale are not updated.

[Tor Bug Tracker & Wiki]

#32148: "No Script" translations for MK locale are not updated.
+--
 Reporter:  Zarko_Gjurov|  Owner:  emmapeel
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Community/Translations  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by gk):

 That's not surprising as NoScript is only translated to
 {{{
 br  da  el  es  he  it  nb nl  pt_BR  sq tr zh_TW
 ca  de  en  fr  is  ms  nb_NO  pl  ru sv_SE  zh_CN
 }}}
 So, there is no `mk` translation. You should contact Giorgio Maone if you
 would like to help with that. I bet he'd be excited about contributions.

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

Re: [tor-bugs] #32394 [Applications/Tor Browser]: Update Progress Bar doesn't use MK translations

[Tor Bug Tracker & Wiki]

#32394: Update Progress Bar doesn't use MK translations
--+--
 Reporter:  Zarko_Gjurov  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * owner:  emmapeel => tbb-team
 * component:  Community/Translations => Applications/Tor Browser


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

Re: [tor-bugs] #32400 [Community]: Cannot obtain GPG keys

[Tor Bug Tracker & Wiki]

#32400: Cannot obtain GPG keys
---+--
 Reporter:  amgems |  Owner:  ggus
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Community  |Version:
 Severity:  Normal | Resolution:
 Keywords:  gpg|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by gk):

 * owner:  (none) => ggus
 * priority:  Immediate => Medium
 * component:  - Select a component => Community
 * severity:  Blocker => Normal


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

Re: [tor-bugs] #32401 [Core Tor/Tor]: Fix variable typos in configure's lzma and zstd support

[Tor Bug Tracker & Wiki]

#32401: Fix variable typos in configure's lzma and zstd support
---+---
 Reporter:  teor   |  Owner:  teor
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  network-team-roadmap-november  |  Actual Points:  0.1
Parent ID:  #32397 | Points:  0.1
 Reviewer: |Sponsor:
---+---
Changes (by teor):

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


Comment:

 Merged to master.

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

Re: [tor-bugs] #31335 [Core Tor/Tor]: make check-includes does not check out of tree builds correctly

[Tor Bug Tracker & Wiki]

#31335: make check-includes does not check out of tree builds correctly
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.5.1-alpha
 Severity:  Normal   | Resolution:  fixed
 Keywords:  043-should, 042-backport, network-   |  Actual Points:  0.1
  team-roadmap-september |
Parent ID:  #29217   | Points:  0.2
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by teor):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * milestone:  Tor: 0.4.3.x-final => Tor: 0.4.2.x-final


Comment:

 Merged to 0.4.2 and later.

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

Re: [tor-bugs] #32397 [Core Tor/Tor]: Add lzma, nss, and zstd support to test_parseconf.sh (was: Add NSS and rust support to test_parseconf.sh)

[Tor Bug Tracker & Wiki]

#32397: Add lzma, nss, and zstd support to test_parseconf.sh
---+---
 Reporter:  teor   |  Owner:  teor
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  network-team-roadmap-november  |  Actual Points:  0.3
Parent ID:  #29211 | Points:  1
 Reviewer:  nickm  |Sponsor:  Sponsor31-can
---+---
Changes (by teor):

 * status:  assigned => needs_review
 * reviewer:   => nickm
 * actualpoints:   => 0.3


Old description:

> We want to allow files like "expected_nss_rust_no_relay_dirauth", for
> cases where the outputs differ.

New description:

 We want to allow files like "expected_nss_no_relay_dirauth", for cases
 where the outputs differ.

--

Comment:

 See my PR:
 * master: https://github.com/torproject/tor/pull/1511

 Hi Nick,
 You can test NSS builds using:
 * one of `expected_nss` or `error_nss`, and
 * one of `expected` or `error`.

 Detailed documentation is in the script.

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

Re: [tor-bugs] #32228 [Applications/Tor Browser]: Bookmark TPO support domains in Tor Browser

[Tor Bug Tracker & Wiki]

#32228: Bookmark TPO support domains in Tor Browser
--+--
 Reporter:  ggus  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by clash):

 I was wondering if it's possible to have a folder with the extra links
 instead of each link occupying their own individual space. The latter
 would feel a tad spammy imo. A folder with all those links would be
 perfect!

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

Re: [tor-bugs] #32020 [Core Tor/Tor]: hsv3: Client do not report failing circuit back into HS subsystem

[Tor Bug Tracker & Wiki]

#32020: hsv3: Client do not report failing circuit back into HS subsystem
+
 Reporter:  dgoulet |  Owner:  dgoulet
 Type:  defect  | Status:  needs_revision
 Priority:  Medium  |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-hs, tor-client  |  Actual Points:  1
Parent ID:  #30200  | Points:  1
 Reviewer:  asn |Sponsor:  Sponsor27-must
+
Changes (by asn):

 * status:  needs_review => needs_revision


Comment:

 Great branch! Review submitted!

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

Re: [tor-bugs] #32402 [Core Tor/Tor]: Actually check most shell scripts for errors

[Tor Bug Tracker & Wiki]

#32402: Actually check most shell scripts for errors
--+
 Reporter:  teor  |  Owner:  teor
 Type:  defect| Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.4.2.1-alpha
 Severity:  Normal| Resolution:
 Keywords:  shellcheck|  Actual Points:  0.2
Parent ID:  #32397| Points:  0.2
 Reviewer:|Sponsor:  Sponsor31-can
--+
Changes (by teor):

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


Comment:

 See my PRs:
 * 0.4.2: https://github.com/torproject/tor/pull/1509
 * master: https://github.com/torproject/tor/pull/1510

 Anyone can merge once CI passes.

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

Re: [tor-bugs] #27953 [Core Tor/Tor]: Authorization types for v3 onion service have to be clarified in documentation

[Tor Bug Tracker & Wiki]

#27953: Authorization types for v3 onion service have to be clarified in
documentation
---+--
 Reporter:  geoip  |  Owner:  (none)
 Type:  defect | Status:  reopened
 Priority:  Medium |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-spec, tor-hs, hs-auth  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by cypherpunks):

 I just stumbled onto this issue when searching for more information about
 v3 stealth client authorizations after seeing the TODO.  At least for
 problem 1, all that's needed is a one-line deletion.  Can't we do this in
 less than a year?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32402 [Core Tor/Tor]: Actually check most shell scripts for errors

[Tor Bug Tracker & Wiki]

#32402: Actually check most shell scripts for errors
---+
 Reporter:  teor   |  Owner:  teor
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor   |Version:  Tor: 0.4.2.1-alpha
 Severity:  Normal |   Keywords:  shellcheck
Actual Points: |  Parent ID:  #32397
   Points:  0.2|   Reviewer:
  Sponsor:  Sponsor31-can  |
---+
 The find command in checkShellScripts.sh is wrong.

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

Re: [tor-bugs] #31371 [Core Tor/Tor]: hs: Add DoS defense counter to DoS heartbeat message

[Tor Bug Tracker & Wiki]

#31371: hs: Add DoS defense counter to DoS heartbeat message
---+---
 Reporter:  dgoulet|  Owner:  dgoulet
 Type:  defect | Status:
   |  needs_revision
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-hs, 042-deferred-20190918  |  Actual Points:
Parent ID: | Points:
 Reviewer:  asn|Sponsor:
   |  Sponsor27-must
---+---
Changes (by asn):

 * status:  needs_review => needs_revision


Comment:

 Looks good but tests are broken! Let's fix those and we are 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] #32401 [Core Tor/Tor]: Fix variable typos in configure's lzma and zstd support

[Tor Bug Tracker & Wiki]

#32401: Fix variable typos in configure's lzma and zstd support
---+---
 Reporter:  teor   |  Owner:  teor
 Type:  defect | Status:  merge_ready
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  network-team-roadmap-november  |  Actual Points:  0.1
Parent ID:  #32397 | Points:  0.1
 Reviewer: |Sponsor:
---+---
Changes (by teor):

 * status:  assigned => merge_ready


Comment:

 * master: https://github.com/torproject/tor/pull/1508

 Anyone can merge once CI passes.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32401 [Core Tor/Tor]: Fix variable typos in configure's lzma and zstd support

[Tor Bug Tracker & Wiki]

#32401: Fix variable typos in configure's lzma and zstd support
--+---
 Reporter:  teor  |  Owner:  teor
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  network-team-roadmap-november
Actual Points:  0.1   |  Parent ID:  #32397
   Points:  0.1   |   Reviewer:
  Sponsor:|
--+---
 No user-visible changes, so no changes file required.

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

Re: [tor-bugs] #32400 [- Select a component]: Cannot obtain GPG keys

[Tor Bug Tracker & Wiki]

#32400: Cannot obtain GPG keys
--+
 Reporter:  amgems|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  - Select a component  |Version:
 Severity:  Blocker   | Resolution:
 Keywords:  gpg   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by amgems):

 I realise now that there is a workaround to be obtained by searching.  I
 tried searching prior to opening this ticket.  There was no obvious search
 mechanism.  So I had to enroll in this Trac system, which is in itself a
 pain in the ass, then open the ticket, and only then was I presented with
 a screen where I could search, and found bunches of old "closed" defects
 matching mine.

 You should not close things as fixed if people such as myself are still
 running into problems.  Until the main download WEB page is updated with
 the correct information, it is not fixed.

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

Re: [tor-bugs] #32362 [Applications/Tor Browser]: NoScript TRUSTED setting doesn't work

[Tor Bug Tracker & Wiki]

#32362: NoScript TRUSTED setting doesn't work
--+--
 Reporter:  nDe15o|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by nDe15o):

 > I'm not sure how long

 I checked it. It happens after 78 hours for sure. It doesn't happen for
 https://trac.torproject.org though, it happens for .onion sites. Maybe
 only for one specific .onion site. I will check it and leave a comment
 later (after 78 hours.)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32400 [- Select a component]: Cannot obtain GPG keys

[Tor Bug Tracker & Wiki]

#32400: Cannot obtain GPG keys
---+--
 Reporter:  amgems |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Immediate  |  Component:  - Select a component
  Version: |   Severity:  Blocker
 Keywords:  gpg|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
 % gpg2  --search 0x4E2C6E8793298290
 gpg: data source: https://keys.openpgp.org:443
 (1)   4096 bit RSA key 4E2C6E8793298290
 Keys 1-1 of 1 for "0x4E2C6E8793298290".  Enter number(s), N)ext, or Q)uit
 > 1
 gpg: key 4E2C6E8793298290: new key but contains no user ID - skipped
 gpg: Total number processed: 1
 gpg:   w/o user IDs: 1

 If I try using the link
 https://pgp.mit.edu/pks/lookup?search=0x4E2C6E8793298290=vindex=on

 I get a proxy error.

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

Re: [tor-bugs] #31335 [Core Tor/Tor]: make check-includes does not check out of tree builds correctly

[Tor Bug Tracker & Wiki]

#31335: make check-includes does not check out of tree builds correctly
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.5.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  043-should, 042-backport, network-   |  Actual Points:  0.1
  team-roadmap-september |
Parent ID:  #29217   | Points:  0.2
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by teor):

 * status:  assigned => merge_ready


Comment:

 See my PRs:
 * 0.4.2: https://github.com/torproject/tor/pull/1506

 Testing:
 * master: https://github.com/torproject/tor/pull/1507

 This is an obviously correct fix on already-reviewed code, anyone can
 merge after CI passes.

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

Re: [tor-bugs] #31335 [Core Tor/Tor]: make check-includes does not check out of tree builds correctly

[Tor Bug Tracker & Wiki]

#31335: make check-includes does not check out of tree builds correctly
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.5.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  043-should, 042-backport, network-   |  Actual Points:  0.1
  team-roadmap-september |
Parent ID:  #29217   | Points:  0.2
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by teor):

 * owner:  (none) => teor
 * keywords:  043-should, network-team-roadmap-september => 043-should,
 042-backport, network-team-roadmap-september
 * version:   => Tor: 0.3.5.1-alpha
 * status:  new => assigned
 * actualpoints:   => 0.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] #32399 [Core Tor/Tor]: Fix "make test-stem" after merging #32339 and #32344

[Tor Bug Tracker & Wiki]

#32399: Fix "make test-stem" after merging #32339 and #32344
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  043-regression, network-team-|  Actual Points:
  roadmap-november   |
Parent ID:  #29211   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor31-must
-+-

Comment (by nickm):

 (I can try to figure this out in my morning if you don't get to it today)

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

Re: [tor-bugs] #32399 [Core Tor/Tor]: Fix "make test-stem" after merging #32339 and #32344

[Tor Bug Tracker & Wiki]

#32399: Fix "make test-stem" after merging #32339 and #32344
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  043-regression, network-team-|  Actual Points:
  roadmap-november   |
Parent ID:  #29211   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor31-must
-+-

Comment (by nickm):

 My guess would be that this is related to the handling of
 OwningController*; those options have funny names and I might have handled
 one or both of them wrong.

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

Re: [tor-bugs] #32295 [Core Tor/Tor]: "Skipping obsolete configuration option." doesn't say which one

[Tor Bug Tracker & Wiki]

#32295: "Skipping obsolete configuration option." doesn't say which one
-+-
 Reporter:  arma |  Owner:  nickm
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.2.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-november,   |  Actual Points:
  042-backport   |
Parent ID:  #29211   | Points:  0.5
 Reviewer:   |Sponsor:
 |  Sponsor31-must
-+-

Comment (by nickm):

 My suggestion would be to change how OBSOLETE is implemented: it doesn't
 really make sense as a type. Instead, there should be an "empty" type for
 fields that can't be read or written, and a CFLG_OBSOLETE flag that causes
 these warnings.  The CFLG_OBSOLETE flag should be handled at the confvar
 layer, I think.

 This makes more sense for 0.4.3 than 0.4.2, though.  Personally I think it
 would almost be okay to leave this as-is in 0.4.2, since we haven't made
 any options obsolete that weren't obsolete before.  But if we think we
 really need a temporary fix there, we could pass the name down to the
 typedvar layer in any kludgey way we want.

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

Re: [tor-bugs] #32396 [Core Tor/Tor]: Add state file support to test_parseconf.sh

[Tor Bug Tracker & Wiki]

#32396: Add state file support to test_parseconf.sh
+
 Reporter:  teor|  Owner:  (none)
 Type:  enhancement | Status:  new
 Priority:  Medium  |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  network-team-roadmap-?  |  Actual Points:
Parent ID:  #29211  | Points:  1
 Reviewer:  |Sponsor:  Sponsor31-can
+

Comment (by nickm):

 test_parseconf relies on --validate-config and --dump-config, neither of
 which exists for state; we'd need to implement them, I suppose.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32399 [Core Tor/Tor]: Fix "make test-stem" after merging #32339 and #32344

[Tor Bug Tracker & Wiki]

#32399: Fix "make test-stem" after merging #32339 and #32344
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:  Tor: 0.4.3.x-final
Component:  Core |Version:
  Tor/Tor|   Keywords:  043-regression, network-team-
 Severity:  Normal   |  roadmap-november
Actual Points:   |  Parent ID:  #29211
   Points:   |   Reviewer:
  Sponsor:   |
  Sponsor31-must |
-+-
 In #32339 and #32344, we broke "make test-stem", but we didn't notice
 before merging, because "make test-stem" is allow_failure in Travis CI.

 It looks like we need to get stem to launch a new tor process for more
 tests. Or our immutability checks are too strict.

 Here is one of the errors:
 {{{
 ==
 FAIL: test_take_ownership_via_controller
 --
 Traceback (most recent call last):
   File "/home/dev/stem/stem/util/test_tools.py", line 152, in 
 self.method = lambda test: self.result(test)  # method that can be
 mixed into TestCases
   File "/home/dev/stem/stem/util/test_tools.py", line 227, in result
 test.fail(self._result.msg)
 AssertionError: Traceback (most recent call last):
   File "/home/dev/stem/stem/util/test_tools.py", line 169, in _wrapper
 runner(*args) if args else runner()
   File "/home/dev/stem/test/integ/process.py", line 641, in
 test_take_ownership_via_controller
 take_ownership = True,
   File "/home/dev/stem/stem/process.py", line 285, in
 launch_tor_with_config
 return launch_tor(tor_cmd, ['-f', '-'], None, completion_percent,
 init_msg_handler, timeout, take_ownership, close_output, stdin =
 config_str)
   File "/home/dev/stem/stem/process.py", line 158, in launch_tor
 raise OSError('Process terminated: %s' % last_problem)
 OSError: Process terminated: Failed to bind one of the listener ports.


 --
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32398 [Core Tor/Stem]: Stem str/bytes confusion on error

[Tor Bug Tracker & Wiki]

#32398: Stem str/bytes confusion on error
---+
 Reporter:  teor   |  Owner:  atagar
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 The test error is tor's problem, but the exception at the end should be
 fixed in stem:
 {{{
 ==
 FAIL: test_take_ownership_via_controller
 --
 Traceback (most recent call last):
   File "/home/dev/stem/stem/util/test_tools.py", line 152, in 
 self.method = lambda test: self.result(test)  # method that can be
 mixed into TestCases
   File "/home/dev/stem/stem/util/test_tools.py", line 227, in result
 test.fail(self._result.msg)
 AssertionError: Traceback (most recent call last):
   File "/home/dev/stem/stem/util/test_tools.py", line 169, in _wrapper
 runner(*args) if args else runner()
   File "/home/dev/stem/test/integ/process.py", line 641, in
 test_take_ownership_via_controller
 take_ownership = True,
   File "/home/dev/stem/stem/process.py", line 285, in
 launch_tor_with_config
 return launch_tor(tor_cmd, ['-f', '-'], None, completion_percent,
 init_msg_handler, timeout, take_ownership, close_output, stdin =
 config_str)
   File "/home/dev/stem/stem/process.py", line 158, in launch_tor
 raise OSError('Process terminated: %s' % last_problem)
 OSError: Process terminated: Failed to bind one of the listener ports.


 --
 Ran 22 tests in 10.048s

 FAILED (failures=1)

 Shutting down tor... done

 Traceback (most recent call last):
   File "/home/dev/stem/run_tests.py", line 468, in 
 main()
   File "/home/dev/stem/run_tests.py", line 304, in main
 if not integ_runner.assert_tor_is_running():
   File "/home/dev/stem/test/runner.py", line 507, in assert_tor_is_running
 process_output = (self._tor_process.stdout.read() + '\n\n' +
 self._tor_process.stderr.read()).strip()
 TypeError: can't concat str to bytes
 make: *** [Makefile:24019: test-stem] Error 1
 Exit 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] #30916 [Core Tor/Tor]: assert in dimap_add_entry()

[Tor Bug Tracker & Wiki]

#30916: assert in dimap_add_entry()
-+-
 Reporter:  dgoulet  |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.4.8-alpha
 Severity:  Normal   | Resolution:  fixed
 Keywords:  crash, 042-should consider-  |  Actual Points:  .1
  backport-after-0423 035-backport 040-backport  |
  041-backport BugSmashFund  |
Parent ID:   | Points:
 Reviewer:  teor |Sponsor:
-+-
Changes (by teor):

 * milestone:  Tor: 0.2.9.x-final => Tor: 0.3.5.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] #31837 [Core Tor/Tor]: Make test_rebind.py more robust

[Tor Bug Tracker & Wiki]

#31837: Make test_rebind.py more robust
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  consider-backport-after-0423,|  Actual Points:  0.1
  035-backport, 040-backport, 041-backport,  |
  BugSmashFund 042-can, asn-merge|
Parent ID:   | Points:  0.1
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by teor):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * milestone:  Tor: 0.4.1.x-final => Tor: 0.3.5.x-final


Comment:

 Merged to 0.3.5 and later.
 Merged #31107, #31466, #30916, #31408, #31837, and #31897 together.

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

Re: [tor-bugs] #31897 [Core Tor/Tor]: util/map_anon_nofork test fails on SunOS

[Tor Bug Tracker & Wiki]

#31897: util/map_anon_nofork test fails on SunOS
-+-
 Reporter:  svschmel |  Owner:  teor
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.1-alpha
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tor-test, 042-must, fast-fix,|  Actual Points:  0.1
  041-regression, BugSmashFund, 041-backport,|
  consider-backport-after-04233  |
Parent ID:   | Points:  0.1
 Reviewer:  ahf  |Sponsor:
-+-
Changes (by teor):

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


Comment:

 Merged to 0.4.1 and later.
 Merged #31107, #31466, #30916, #31408, #31837, and #31897 together.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: 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:  closed
 Priority:  Very High|  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.1-alpha
 Severity:  Normal   | Resolution:  fixed
 Keywords:  BugSmashFund tor-hs regression   |  Actual Points:  0.4
  042-must consider-backport-after-0423, |
  035-backport, 040-backport, 041-backport,  |
  042-backport   |
Parent ID:   | Points:  0.3
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * milestone:  Tor: 0.4.1.x-final => Tor: 0.3.5.x-final


Comment:

 Merged to 0.3.5 and later.
 Merged #31107, #31466, #30916, #31408, #31837, and #31897 together.

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

Re: [tor-bugs] #30916 [Core Tor/Tor]: assert in dimap_add_entry()

[Tor Bug Tracker & Wiki]

#30916: assert in dimap_add_entry()
-+-
 Reporter:  dgoulet  |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.4.8-alpha
 Severity:  Normal   | Resolution:  fixed
 Keywords:  crash, 042-should consider-  |  Actual Points:  .1
  backport-after-0423 035-backport 040-backport  |
  041-backport BugSmashFund  |
Parent ID:   | Points:
 Reviewer:  teor |Sponsor:
-+-
Changes (by teor):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * milestone:  Tor: 0.4.0.x-final => Tor: 0.2.9.x-final


Comment:

 Merged to 0.3.5 and later.
 Merged #31107, #31466, #30916, #31408, #31837, and #31897 together.

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

Re: [tor-bugs] #31466 [Core Tor/Tor]: Consider demoting ".exit is disabled" log message to info

[Tor Bug Tracker & Wiki]

#31466: Consider demoting ".exit is disabled" log message to info
-+-
 Reporter:  asn  |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  consider-backport-after-0423, bug-   |  Actual Points:  .1
  bounty, hackerone, tor-security?, 042-should   |
  029-backport? 035-backport 040-backport|
  041-backport BugSmashFund dgoulet-merge|
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:
-+-
Changes (by teor):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * milestone:  Tor: 0.4.0.x-final => Tor: 0.2.9.x-final


Comment:

 Merged to 0.2.9 and later.
 Merged #31107, #31466, #30916, #31408, #31837, and #31897 together.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: 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:  closed
 Priority:  High |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.4.4-alpha
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tor-relay, tor-channel 042-must  |  Actual Points:  .1
  consider-backport-after-0423 029-backport  |
  035-backport 040-backport 041-backport |
  BugSmashFund   |
Parent ID:   | Points:
 Reviewer:  teor |Sponsor:
-+-
Changes (by teor):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * milestone:  Tor: 0.4.0.x-final => Tor: 0.2.9.x-final


Comment:

 Merged to 0.2.9 and later.
 Merged #31107, #31466, #30916, #31408, #31837, and #31897 together.

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

Re: [tor-bugs] #32295 [Core Tor/Tor]: "Skipping obsolete configuration option." doesn't say which one

[Tor Bug Tracker & Wiki]

#32295: "Skipping obsolete configuration option." doesn't say which one
-+-
 Reporter:  arma |  Owner:  nickm
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.2.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-november,   |  Actual Points:
  042-backport   |
Parent ID:  #29211   | Points:  0.5
 Reviewer:   |Sponsor:
 |  Sponsor31-must
-+-
Changes (by teor):

 * owner:  teor => nickm


Comment:

 nickm, can you help me work out how to do this fix?
 (Or, if it's a quick one, feel free to do it.)

 If we want to warn about obsolete config options using their names (key),
 we need to pass config_line_t to parse(), or pass key and value to parse.

 Which design should we use for 0.4.2?
 Should we change it in 0.4.3?

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

Re: [tor-bugs] #30984 [Core Tor/Tor]: Make a key-value line abstraction to output control replies

[Tor Bug Tracker & Wiki]

#30984: Make a key-value line abstraction to output control replies
-+-
 Reporter:  catalyst |  Owner:
 |  catalyst
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  042-deferred-20190918, early-review  |  Actual Points:
Parent ID:  #29210   | Points:  5
 Reviewer:  teor |Sponsor:
 |  Sponsor31-can
-+-

Comment (by teor):

 Looks fine to me as a design, I suggested a few tweaks.
 Are there any specific things you would like me to look at?

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

Re: [tor-bugs] #30866 [Core Tor/Tor]: Teach config.c to work with options configured in other modules

[Tor Bug Tracker & Wiki]

#30866: Teach config.c to work with options configured in other modules
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  needs_revision
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #29211| Points:  2
 Reviewer:  teor  |Sponsor:  Sponsor31-can
--+
Changes (by teor):

 * status:  needs_review => needs_revision


Comment:

 (Please remember to add actual points!)

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

Re: [tor-bugs] #30866 [Core Tor/Tor]: Teach config.c to work with options configured in other modules

[Tor Bug Tracker & Wiki]

#30866: Teach config.c to work with options configured in other modules
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #29211| Points:  2
 Reviewer:  teor  |Sponsor:  Sponsor31-can
--+

Comment (by teor):

 This looks great, here's how we want to move forward:
 1. I'll do #32397
 2. nickm will add some tests for crypto NSS using test_parseconf.sh
 3. we can merge

 Optionally, if we want to do a lot of state refactoring:
 4. I'll do #32396
 5. Someone will add some tests for mainloop state using test_parseconf.sh
 But this is not a high priority at this time.

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

[tor-bugs] #32397 [Core Tor/Tor]: Add NSS and rust support to test_parseconf.sh

[Tor Bug Tracker & Wiki]

#32397: Add NSS and rust support to test_parseconf.sh
---+---
 Reporter:  teor   |  Owner:  teor
 Type:  enhancement| Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal |   Keywords:  network-team-roadmap-november
Actual Points: |  Parent ID:  #29211
   Points:  1  |   Reviewer:
  Sponsor:  Sponsor31-can  |
---+---
 We want to allow files like "expected_nss_rust_no_relay_dirauth", for
 cases where the outputs differ.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32396 [Core Tor/Tor]: Add state file support to test_parseconf.sh

[Tor Bug Tracker & Wiki]

#32396: Add state file support to test_parseconf.sh
---+
 Reporter:  teor   |  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal |   Keywords:  network-team-roadmap-?
Actual Points: |  Parent ID:  #29211
   Points:  1  |   Reviewer:
  Sponsor:  Sponsor31-can  |
---+
 Currently, test_parseconf.sh reads options from the cmdline file, default
 options file, and torrc.

 I'd also like to see state file support.

 This ticket is not a high priority, unless we refactor a lot of state
 code.

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

Re: [tor-bugs] #30866 [Core Tor/Tor]: Teach config.c to work with options configured in other modules

[Tor Bug Tracker & Wiki]

#30866: Teach config.c to work with options configured in other modules
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #29211| Points:  2
 Reviewer:  teor  |Sponsor:  Sponsor31-can
--+
Changes (by nickm):

 * status:  needs_revision => 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] #31509 [Core Tor/Tor]: config refactor: make test-stem should pass

[Tor Bug Tracker & Wiki]

#31509: config refactor: make test-stem should pass
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  not a
 Keywords:  network-team-roadmap-august, |  bug
  042-deferred-20190918  |  Actual Points:
Parent ID:  #29211   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor31-must
-+-
Changes (by teor):

 * status:  reopened => closed
 * resolution:   => not a bug


Comment:

 I will regularly run "make test-stem", as it doesn't work for other
 people.

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

Re: [tor-bugs] #32053 [Applications/Tor Browser]: Tor Browser bundles based on Firefox 68 ESR are not reproducible (LLVM optimization issue)

[Tor Bug Tracker & Wiki]

#32053: Tor Browser bundles based on Firefox 68 ESR are not reproducible (LLVM
optimization issue)
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Immediate|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201911, tbb-9.0-must,  |  Actual Points:
  tbb-9.0-issues, tbb-regression,|
  tbb-9.0.1-can, GeorgKoppen201911   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by alexcrichton):

 I just posted a comment on the bug report with a much more minimal test
 case (only a few hundred KB!), it only took many cpu hours to extract :)

 From here I'm still trying to reduce it further to increase the likelihood
 that someone from LLVM can help fix (I'm not so good at LLVM internals).
 This test case is small enough though that it may be pretty reasonable to
 bisect LLVM itself with. Dealing with a bitcode file across that many LLVM
 revisions may be pretty difficult though, so bisection likely won't be
 trivial.

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

Re: [tor-bugs] #32036 [Core Tor/Tor]: output debug logs to logcat as early as possible on Android

[Tor Bug Tracker & Wiki]

#32036: output debug logs to logcat as early as possible on Android
-+-
 Reporter:  eighthave|  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, Android, 043-should, |  Actual Points:
  BugSmashFund   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  tbb-mobile, Android, 043-should => tbb-mobile, Android,
 043-should, BugSmashFund
 * 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] #32191 [Core Tor/Tor]: when cross-compiling, lzma and zstd will be detected on build system

[Tor Bug Tracker & Wiki]

#32191: when cross-compiling, lzma and zstd will be detected on build system
-+-
 Reporter:  eighthave|  Owner:  teor
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  Android, 042-backport, BugSmashFund  |  Actual Points:  0.2
Parent ID:   | Points:  0.2
 Reviewer:  nickm|Sponsor:
-+-
Changes (by teor):

 * keywords:  Android, 042-backport => Android, 042-backport, BugSmashFund
 * points:   => 0.2
 * type:  enhancement => defect
 * actualpoints:   => 0.2


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

Re: [tor-bugs] #32191 [Core Tor/Tor]: when cross-compiling, lzma and zstd will be detected on build system

[Tor Bug Tracker & Wiki]

#32191: when cross-compiling, lzma and zstd will be detected on build system
---+
 Reporter:  eighthave  |  Owner:  teor
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  Android, 042-backport  |  Actual Points:
Parent ID: | Points:
 Reviewer:  nickm  |Sponsor:
---+
Changes (by teor):

 * status:  assigned => needs_review


Comment:

 Replying to [comment:30 nickm]:
 > >Nick, do you think we should backport this build fix to 0.4.2?
 >
 > Hm. Can we envision this breaking any reasonable build that would
 previously have succeeded?  If not, I think a backport is reasonable.

 It only sets PKG_CONFIG_PATH when it's unset. So it does override the
 default path compiled in to the pkg-config binary, but that path is wrong
 for cross-compiles. It never overrides user-configured paths.

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

Re: [tor-bugs] #32139 [Core Tor/Tor]: Disable all dirauth options when those modules are disabled (was: Disable all dirauth and relay options when those modules are disabled)

[Tor Bug Tracker & Wiki]

#32139: Disable all dirauth options when those modules are disabled
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-design, network-team-roadmap-|  Actual Points:
  november   |
Parent ID:  #31851   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by teor):

 * status:  new => assigned
 * keywords:  tor-design, network-team-roadmap-october => tor-design,
 network-team-roadmap-november
 * owner:  (none) => nickm


Comment:

 Now this ticket is only for dirauth.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32395 [Core Tor/Tor]: Disable all relay options when those modules are disabled

[Tor Bug Tracker & Wiki]

#32395: Disable all relay options when those modules are disabled
-+-
 Reporter:  teor |  Owner:  (none)
 Type:   | Status:  new
  enhancement|
 Priority:  Medium   |  Milestone:  Tor: 0.4.3.x-final
Component:  Core |Version:
  Tor/Tor|   Keywords:  tor-design, network-team-roadmap-
 Severity:  Normal   |  november
Actual Points:   |  Parent ID:  #31851
   Points:  2|   Reviewer:
  Sponsor:   |
  Sponsor31-can  |
-+-
 Here's what we want to change in this ticket:

 * --disable-module-relay
   * disable DirPort, DirCache, ORPort
   * set ClientOnly to 1
   * Disables all the other options under Directory Server Options
   * Disables all the other options under Server Options
   * Disables the --list-fingerprint, RelayBandwidth*,
 MaxAdvertisedBandwidth, PerConnBW*, and ServerTransportPlugin options
 * Maybe some of these options should move under Server Options in the
 man page

 These changes should be much easier after the config 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] #30984 [Core Tor/Tor]: Make a key-value line abstraction to output control replies

[Tor Bug Tracker & Wiki]

#30984: Make a key-value line abstraction to output control replies
-+-
 Reporter:  catalyst |  Owner:
 |  catalyst
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  042-deferred-20190918, early-review  |  Actual Points:
Parent ID:  #29210   | Points:  5
 Reviewer:  teor |Sponsor:
 |  Sponsor31-can
-+-

Comment (by catalyst):

 Pull request in https://github.com/torproject/tor/pull/1505

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32394 [Community/Translations]: Update Progress Bar doesn't use MK translations

[Tor Bug Tracker & Wiki]

#32394: Update Progress Bar doesn't use MK translations
--+
 Reporter:  Zarko_Gjurov  |  Owner:  emmapeel
 Type:  defect| Status:  new
 Priority:  Medium|  Component:  Community/Translations
  Version:|   Severity:  Normal
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
 While Tor Browser v9.0 (MK locale) is updating to v9.0.1 the **Update
 Progress Bar** doesn't use MK translation string(s).

 [[Image(https://i.ibb.co/Xxhx0Kd/Update-Progress-Bar-not-use-MK-
 translations.png)]]

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

Re: [tor-bugs] #32148 [Community/Translations]: "No Script" translations for MK locale are not updated.

[Tor Bug Tracker & Wiki]

#32148: "No Script" translations for MK locale are not updated.
+--
 Reporter:  Zarko_Gjurov|  Owner:  emmapeel
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Community/Translations  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by Zarko_Gjurov):

 The problem still exist in Tor Browser version 9.0.1.

 [[Image(https://i.ibb.co/Y38PBXj/No-Script-not-use-all-MK-
 translations.png)]]

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

[tor-bugs] [Tor Bug Tracker & Wiki] Batch modify: #31849, #31850, #31852, #31853, ...

[Tor Bug Tracker & Wiki]

Batch modification to #31849, #31850, #31852, #31853, #32067, #32099, #32100, 
#32101, #32110, #32113, #32306 by catalyst:


--
Tickets URL: 

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

Re: [tor-bugs] #29214 [Core Tor/Tor]: Update 'tor-guts' archictecture documentation to describe current (actual, as-built) architecture.

[Tor Bug Tracker & Wiki]

#29214: Update 'tor-guts' archictecture documentation to describe current 
(actual,
as-built) architecture.
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  task | Status:
 |  accepted
 Priority:  High |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-november,   |  Actual Points:
  s31-docs   |
Parent ID:   | Points:  5
 Reviewer:   |Sponsor:
 |  Sponsor31-must
-+-
Changes (by catalyst):

 * cc: catalyst (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] #30683 [Applications/Tor Browser]: Properties in dom/locales/$lang/chrome/ allow detecting user locale

[Tor Bug Tracker & Wiki]

#30683: Properties in dom/locales/$lang/chrome/ allow detecting user locale
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-fingerprinting-locale|  Actual Points:  1
  TorBrowserTeam201911R  |
Parent ID:   | Points:  0.25
 Reviewer:   |Sponsor:
-+-
Changes (by acat):

 * keywords:  tbb-fingerprinting-locale TorBrowserTeam201911 => tbb-
 fingerprinting-locale TorBrowserTeam201911R
 * status:  reopened => needs_review


Comment:

 Backported in https://github.com/acatarineu/tor-
 browser/commits/30683_backport.

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

[tor-bugs] #32393 [Applications/GetTor]: GetTor's GitHub links are broken

[Tor Bug Tracker & Wiki]

#32393: GetTor's GitHub links are broken
-+
 Reporter:  dcf  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/GetTor  |Version:
 Severity:  Normal   |   Keywords:  github
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+
 I just requested a !get...@torproject.org email. The github.com links in
 the response are broken:
 > Tor Browser 8.5.5 for windows-en-US-64 (github):
 https://github.com/TheTorProject/gettorbrowser/raw/torbrowser-releases
 /torbrowser-install-8.5.5_en-US.exe
 > Signature file: https://github.com/TheTorProject/gettorbrowser/raw
 /torbrowser-releases/torbrowser-install-8.5.5_en-US.exe.asc

 The current version of the branch that should hold the downloads is
 
https://github.com/TheTorProject/gettorbrowser/tree/d3b2871c6b92db792e169cfb146cae358729ee30.
 It doesn't seem to hold any download files at all, only .gitattributes and
 README.md.

 Looking at past commits, there were sometimes some files present, but
 never a complete set:
  *
 
[https://github.com/TheTorProject/gettorbrowser/tree/3b26d4f081391743f5edfcea6d2a8551aa99cb13
 3b26d4f081391743f5edfcea6d2a8551aa99cb13]
* tor-browser-linux32-8.5.5_ar.tar.xz
  *
 
[https://github.com/TheTorProject/gettorbrowser/tree/b98021238150818734c6ab72f843a81eb72c5dcc
 b98021238150818734c6ab72f843a81eb72c5dcc]
* tor-browser-linux32-8.5.5_ar.tar.xz
* tor-browser-linux32-8.5.5_ar.tar.xz.asc
  *
 
[https://github.com/TheTorProject/gettorbrowser/tree/1a579623316a189aab9334d33ee88014196e80e1
 1a579623316a189aab9334d33ee88014196e80e1]
* tor-browser-linux32-8.5.5_ar.tar.xz
* tor-browser-linux32-8.5.5_ar.tar.xz.asc
* tor-browser-linux32-8.5.5_ca.tar.xz
  *
 
[https://github.com/TheTorProject/gettorbrowser/tree/d284209de15ad6c7bf5f9a1e4c9684d3d1d89f5e
 d284209de15ad6c7bf5f9a1e4c9684d3d1d89f5e]
* tor-browser-linux32-8.5.5_ar.tar.xz
* tor-browser-linux32-8.5.5_ar.tar.xz.asc
* tor-browser-linux32-8.5.5_ca.tar.xz
* tor-browser-linux32-8.5.5_ca.tar.xz.asc
  *
 
[https://github.com/TheTorProject/gettorbrowser/commits/d3b2871c6b92db792e169cfb146cae358729ee30
 d3b2871c6b92db792e169cfb146cae358729ee30]
* ''none''

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

Re: [tor-bugs] #32295 [Core Tor/Tor]: "Skipping obsolete configuration option." doesn't say which one

[Tor Bug Tracker & Wiki]

#32295: "Skipping obsolete configuration option." doesn't say which one
-+-
 Reporter:  arma |  Owner:  teor
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.2.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-november,   |  Actual Points:
  042-backport   |
Parent ID:  #29211   | Points:  0.5
 Reviewer:   |Sponsor:
 |  Sponsor31-must
-+-
Changes (by teor):

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


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

Re: [tor-bugs] #32207 [Core Tor/Tor]: write description of pub-sub architecture

[Tor Bug Tracker & Wiki]

#32207: write description of pub-sub architecture
-+-
 Reporter:  catalyst |  Owner:  nickm
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-september,  |  Actual Points:
  s31-docs   |
Parent ID:  #29215   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor31-must
-+-
Changes (by gaba):

 * owner:  (none) => nickm
 * 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] #32209 [Core Tor/Tor]: write description of config subsystem architecture

[Tor Bug Tracker & Wiki]

#32209: write description of config subsystem architecture
-+-
 Reporter:  catalyst |  Owner:  nickm
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-september,  |  Actual Points:
  s31-docs   |
Parent ID:  #29215   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor31-must
-+-
Changes (by gaba):

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


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

Re: [tor-bugs] #32208 [Core Tor/Tor]: write description of control subsystem architecture

[Tor Bug Tracker & Wiki]

#32208: write description of control subsystem architecture
-+-
 Reporter:  catalyst |  Owner:
 |  catalyst
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-september,  |  Actual Points:
  s31-docs   |
Parent ID:  #29215   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor31-must
-+-
Changes (by catalyst):

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


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

Re: [tor-bugs] #32206 [Core Tor/Tor]: write high-level outline of target modular tor architecture

[Tor Bug Tracker & Wiki]

#32206: write high-level outline of target modular tor architecture
-+-
 Reporter:  catalyst |  Owner:
 |  catalyst
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-september,  |  Actual Points:
  s31-docs   |
Parent ID:  #29215   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor31-must
-+-
Changes (by catalyst):

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


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

Re: [tor-bugs] #32392 [Internal Services/Service - nextcloud]: Emails are sent from n...@riseup.net

[Tor Bug Tracker & Wiki]

#32392: Emails are sent from n...@riseup.net
-+-
 Reporter:  ln5  |  Owner:
 |  nextcloud-admin@…
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service -  |Version:
  nextcloud  |
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #32267   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gaba):

 * parent:   => #32267


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

Re: [tor-bugs] #32260 [Core Tor/Tor]: Backport "Travis: Use Ubuntu Bionic, but keep Trusty for chutney"

[Tor Bug Tracker & Wiki]

#32260: Backport "Travis: Use Ubuntu Bionic, but keep Trusty for chutney"
-+-
 Reporter:  teor |  Owner:  teor
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  consider-backport-immediately, tor-  |  Actual Points:  0.1
  ci, 029-backport, 035-backport, 040-backport,  |
  041-backport, 042-backport |
Parent ID:   | Points:  0.1
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * parent:  #31919 =>
 * milestone:  Tor: 0.4.3.x-final => Tor: 0.2.9.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

[tor-bugs] #32392 [Internal Services/Service - nextcloud]: Emails are sent from n...@riseup.net

[Tor Bug Tracker & Wiki]

#32392: Emails are sent from n...@riseup.net
-+-
 Reporter:  ln5  |  Owner:  nextcloud-
 |  admin@…
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service -  |Version:
  nextcloud  |
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 In emails from nc.tpn, both envelope sender and From: is "n...@riseup.net".
 This is confusing, especially since our evaluation instance uses that
 address.
 It would be good if we could have something @torproject.{org,net}. Not
 sure what's best.

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

Re: [tor-bugs] #32367 [Internal Services/Service - nextcloud]: ONLYOFFICE not working?

[Tor Bug Tracker & Wiki]

#32367: ONLYOFFICE not working?
-+-
 Reporter:  gaba |  Owner:
 |  nextcloud-admin@…
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service -  |Version:
  nextcloud  |
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:  #32267   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by micah):

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


Comment:

 This was due to the onlyoffice server being on a different domain than
 torproject.net, and browser plugins not letting you load things from other
 domains.

 We changed the onlyoffice document server address to be on the same
 domain, so this should no longer be an 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] #32239 [Internal Services/Tor Sysadmin Team]: setup a cache frontend for the blog

[Tor Bug Tracker & Wiki]

#32239: setup a cache frontend for the blog
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #32090   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * status:  accepted => merge_ready


Old description:

> design docs in https://help.torproject.org/tsa/howto/cache/
>
> launch checklist:
>
>  1. alternatives listing and comparison (done)
>  2. deploy a test virtual machine by hand, say `cache-01.tpo` (done)
>  3. benchmark the different alternatives (done, ATS and nginx comparable)
>  4. setup secondary node with Puppet, say `cache-02.tpo` (done)
>  4. validation benchmark against both nodes (done)
>  5. lower DNS to 10 minutes wait an hour (done)
>  6. open firewall (done)
>  7. lower DNS to 3 minutes (done, around 2019-11-05 16:00:00)
>  8. point DNS to caches (done)
>  11. raise DNS back to 1h if all goes well.
>
> Disaster recovery:
>
>  1. flip DNS back to backend

New description:

 design docs in https://help.torproject.org/tsa/howto/cache/

 launch checklist:

  1. alternatives listing and comparison (done)
  2. deploy a test virtual machine by hand, say `cache-01.tpo` (done)
  3. benchmark the different alternatives (done, ATS and nginx comparable)
  4. setup secondary node with Puppet, say `cache-02.tpo` (done)
  4. validation benchmark against both nodes (done)
  5. lower DNS to 10 minutes wait an hour (done)
  6. open firewall (done)
  7. lower DNS to 3 minutes (done, around 2019-11-05 16:00:00)
  8. point DNS to caches (done)
  11. raise DNS back to 1h if all goes well. (done!)

 Post launch tasks:

  1. update documentation to fill in information from template
  2. hit ratio stats in to Prometheus, separate ticket?
  3. convert existing varnish setups into Nginx (probably requires Puppet
 refactoring), separate ticket?

 Disaster recovery:

  1. flip DNS back to backend

--

Comment:

 added monitoring of https://blog.tpo in nagios, to make really sure *that*
 keeps working.

 last remaining step here is to make sure the hit ratio is correct, and
 update the documentation to fill in the "tutorial" and "howto" sections
 from the template.

 there is also longer-term work here to convert existing varnish instances,
 probably. updated the summary to cover for 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] #32239 [Internal Services/Tor Sysadmin Team]: setup a cache frontend for the blog

[Tor Bug Tracker & Wiki]

#32239: setup a cache frontend for the blog
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #32090   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 as predicted, we have between 2 and 4 mbit/s although that traffic is
 present on *both* nodes, so it remains to be seen what the actual traffic
 sum is. we might be a little above double the expected average, but it
 should still be within acceptable boundaries in terms of costs.

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

Re: [tor-bugs] #32239 [Internal Services/Tor Sysadmin Team]: setup a cache frontend for the blog

[Tor Bug Tracker & Wiki]

#32239: setup a cache frontend for the blog
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #32090   | Points:
 Reviewer:   |Sponsor:
-+-

Old description:

> design docs in https://help.torproject.org/tsa/howto/cache/
>
> launch checklist:
>
>  1. alternatives listing and comparison (done)
>  2. deploy a test virtual machine by hand, say `cache-01.tpo` (done)
>  3. benchmark the different alternatives (done, ATS and nginx comparable)
>  4. setup secondary node with Puppet, say `cache-02.tpo` (done)
>  4. validation benchmark against both nodes (done)
>  5. lower DNS to 10 minutes wait an hour (done)
>  6. open firewall (done)
>  7. lower DNS to 3 minutes (done, around 2019-11-05 16:00:00)
>  8. point DNS to caches
>  11. raise DNS back to 1h if all goes well.
>
> Disaster recovery:
>
>  1. flip DNS back to backend

New description:

 design docs in https://help.torproject.org/tsa/howto/cache/

 launch checklist:

  1. alternatives listing and comparison (done)
  2. deploy a test virtual machine by hand, say `cache-01.tpo` (done)
  3. benchmark the different alternatives (done, ATS and nginx comparable)
  4. setup secondary node with Puppet, say `cache-02.tpo` (done)
  4. validation benchmark against both nodes (done)
  5. lower DNS to 10 minutes wait an hour (done)
  6. open firewall (done)
  7. lower DNS to 3 minutes (done, around 2019-11-05 16:00:00)
  8. point DNS to caches (done)
  11. raise DNS back to 1h if all goes well.

 Disaster recovery:

  1. flip DNS back to backend

--

Comment (by anarcat):

 i've reverted to the originally planned procedure where we just flip the
 switch because it's a simpler procedure. i've also setup a `cache.tpo`
 alias to point to the cluster of machines so we can get other sites in and
 out of rotation with a single CNAME, instead of having to maintain
 possibly multiple entries under multiple entries.

 traffic now seems to be flowing into the nodes without noticeable
 problems. load is negligible:

 {{{
 Load average: 0.03 0.02 0.00
 }}}

 we have space for 12GB of cache on cache-02:

 {{{
 anarcat@cache-02:~$ df -h /var/cache/nginx/
 Filesystem Size  Used Avail Use% Mounted on
 /dev/mapper/croot   19G  3.0G   15G  18% /
 }}}

 and ~7GB on cache01:

 {{{
 root@cache01:~# df -h /var/cache/nginx/
 Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
 /dev/sda1  9,8G1,9G  7,4G  21% /
 }}}

 that's probably what we should pay closest attention to, actually, since
 it's not clear nginx will do the right thing with out of disk space
 conditions.

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

Re: [tor-bugs] #32239 [Internal Services/Tor Sysadmin Team]: setup a cache frontend for the blog

[Tor Bug Tracker & Wiki]

#32239: setup a cache frontend for the blog
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #32090   | Points:
 Reviewer:   |Sponsor:
-+-

Old description:

> design docs in https://help.torproject.org/tsa/howto/cache/
>
> launch checklist:
>
>  1. alternatives listing and comparison (done)
>  2. deploy a test virtual machine by hand, say `cache-01.tpo` (done)
>  3. benchmark the different alternatives (done, ATS and nginx comparable)
>  4. setup secondary node with Puppet, say `cache-02.tpo` (done)
>  4. validation benchmark against both nodes (done)
>  5. lower DNS to 10 minutes wait an hour (done)
>  6. open firewall (done)
>  7. lower DNS to 3 minutes (done, around 2019-11-05 16:00:00)
>  8. *add* one node to the DNS, check if traffic flows properly after 10
> minutes
>  9. add the other node to DNS, again checking traffic
>  10. if all is well, remove backend from DNS
>  11. raise DNS back to 1h if all goes well.
>
> Disaster recovery:
>
>  1. flip DNS back to backend

New description:

 design docs in https://help.torproject.org/tsa/howto/cache/

 launch checklist:

  1. alternatives listing and comparison (done)
  2. deploy a test virtual machine by hand, say `cache-01.tpo` (done)
  3. benchmark the different alternatives (done, ATS and nginx comparable)
  4. setup secondary node with Puppet, say `cache-02.tpo` (done)
  4. validation benchmark against both nodes (done)
  5. lower DNS to 10 minutes wait an hour (done)
  6. open firewall (done)
  7. lower DNS to 3 minutes (done, around 2019-11-05 16:00:00)
  8. point DNS to caches
  11. raise DNS back to 1h if all goes well.

 Disaster recovery:

  1. flip DNS back to backend

--

Comment (by anarcat):

 i've flipped DNS to the new nodes.

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

Re: [tor-bugs] #32239 [Internal Services/Tor Sysadmin Team]: setup a cache frontend for the blog

[Tor Bug Tracker & Wiki]

#32239: setup a cache frontend for the blog
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #32090   | Points:
 Reviewer:   |Sponsor:
-+-

Old description:

> design docs in https://help.torproject.org/tsa/howto/cache/
>
> launch checklist:
>
>  1. alternatives listing and comparison (done)
>  2. deploy a test virtual machine by hand, say `cache-01.tpo` (done)
>  3. benchmark the different alternatives (done, ATS and nginx comparable)
>  4. setup secondary node with Puppet, say `cache-02.tpo` (done)
>  4. validation benchmark against both nodes (done)
>  5. lower DNS to 10 minutes wait an hour (done)
>  6. open firewall
>  7. lower DNS to 3 minutes
>  8. *add* one node to the DNS, check if traffic flows properly after 10
> minutes
>  9. add the other node to DNS, again checking traffic
>  10. if all is well, remove backend from DNS
>  11. raise DNS back to 1h if all goes well.
>
> Disaster recovery:
>
>  1. flip DNS back to backend

New description:

 design docs in https://help.torproject.org/tsa/howto/cache/

 launch checklist:

  1. alternatives listing and comparison (done)
  2. deploy a test virtual machine by hand, say `cache-01.tpo` (done)
  3. benchmark the different alternatives (done, ATS and nginx comparable)
  4. setup secondary node with Puppet, say `cache-02.tpo` (done)
  4. validation benchmark against both nodes (done)
  5. lower DNS to 10 minutes wait an hour (done)
  6. open firewall (done)
  7. lower DNS to 3 minutes (done, around 2019-11-05 16:00:00)
  8. *add* one node to the DNS, check if traffic flows properly after 10
 minutes
  9. add the other node to DNS, again checking traffic
  10. if all is well, remove backend from DNS
  11. raise DNS back to 1h if all goes well.

 Disaster recovery:

  1. flip DNS back to backend

--

Comment (by anarcat):

 lowered TTL to 3 minutes, getting ready for launch

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

Re: [tor-bugs] #32053 [Applications/Tor Browser]: Tor Browser bundles based on Firefox 68 ESR are not reproducible (LLVM optimization issue)

[Tor Bug Tracker & Wiki]

#32053: Tor Browser bundles based on Firefox 68 ESR are not reproducible (LLVM
optimization issue)
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Immediate|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201911, tbb-9.0-must,  |  Actual Points:
  tbb-9.0-issues, tbb-regression,|
  tbb-9.0.1-can, GeorgKoppen201911   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 Replying to [comment:24 alexcrichton]:
 > I've opened up https://bugs.llvm.org/show_bug.cgi?id=43909 and will
 track that, I'm attempting to use LLVM's automatic test case reduction
 tools but it's likely going to take quite some time due to how large the
 module is.

 Thanks! Let me know whether/how I can help here. I don't know much about
 `opt` and its options/flags, so there is some learning curve for me but I
 could spend some cycles tomorrow and the coming days given how important
 that bug is for us. Maybe I should just start bisecting figuring out where
 this got introduced. Might help tracking the optimization issue down.
 Either way, let me know.

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

Re: [tor-bugs] #32391 [Internal Services/Service - nextcloud]: Purge test accounts and data from riseup in February 4, 2020

[Tor Bug Tracker & Wiki]

#32391: Purge test accounts and data from riseup in February 4, 2020
-+-
 Reporter:  gaba |  Owner:
 |  nextcloud-admin@…
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service -  |Version:
  nextcloud  |
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #32267   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gaba):

 * parent:   => #32267


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

Re: [tor-bugs] #32390 [Internal Services/Service - sandstorm]: decomission storm / bracteata on February 4, 2020

[Tor Bug Tracker & Wiki]

#32390: decomission storm / bracteata on February 4, 2020
---+--
 Reporter:  gaba   |  Owner:  hiro
 Type:  task   | Status:  new
 Priority:  Medium |  Milestone:
Component:  Internal Services/Service - sandstorm  |Version:
 Severity:  Normal | Resolution:
 Keywords:  gaba   |  Actual Points:
Parent ID:  #32267 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by gaba):

 * parent:   => #32267


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

Re: [tor-bugs] #32053 [Applications/Tor Browser]: Tor Browser bundles based on Firefox 68 ESR are not reproducible (LLVM optimization issue) (was: macOS bundles for Tor Browser 9.0a8 are not reproduci

[Tor Bug Tracker & Wiki]

#32053: Tor Browser bundles based on Firefox 68 ESR are not reproducible (LLVM
optimization issue)
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Immediate|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201911, tbb-9.0-must,  |  Actual Points:
  tbb-9.0-issues, tbb-regression,|
  tbb-9.0.1-can, GeorgKoppen201911   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Old description:

> For some reasons boklm and I got different macOS bundles when building
> our rc for 9.0a8.

New description:

 For some reasons boklm and I got different macOS bundles when building our
 rc for 9.0a8. Linux bundles are affected, too (seee #32052) and other
 platforms as well.

--

Comment (by gk):

 Closed #32052 as an actual duplicate after inspecting the intermediate
 compilation output of non-matching results.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32391 [Internal Services/Service - nextcloud]: Purge test accounts and data from riseup in February 4, 2020

[Tor Bug Tracker & Wiki]

#32391: Purge test accounts and data from riseup in February 4, 2020
-+-
 Reporter:  gaba |  Owner:  nextcloud-
 |  admin@…
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service -  |Version:
  nextcloud  |
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 We are migrating into nc.torproject.net. We are planning to remove any
 test account from nc.riseup.net in February 4, 2020. This is the ticket
 for us not to forget :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32390 [Internal Services/Service - sandstorm]: decomission storm / bracteata on February 4, 2020

[Tor Bug Tracker & Wiki]

#32390: decomission storm / bracteata on February 4, 2020
---+--
 Reporter:  gaba   |  Owner:  hiro
 Type:  task   | Status:  new
 Priority:  Medium |  Milestone:
Component:  Internal Services/Service - sandstorm  |Version:
 Severity:  Normal |   Keywords:  gaba
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+--
 Hi!

 We are migrating into nc.torproject.net. We are planning to shutdown storm
 in February. This is the ticket for us not to forget :)

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

Re: [tor-bugs] #32052 [Applications/Tor Browser]: Linux32 bundles for Tor Browser 9.0a8 are not reproducible

[Tor Bug Tracker & Wiki]

#32052: Linux32 bundles for Tor Browser 9.0a8 are not reproducible
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Immediate|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  tbb-9.0-must, tbb-9.0-issues, tbb-   |  duplicate
  regression, tbb-9.0.1-can, |  Actual Points:
  TorBrowserTeam201911   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

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


Comment:

 Okay, I looked at it closer by examining the intermediate output as done
 in #32053 and it seems both tickets are in fact duplicates: the linux
 builds have proper non-optimized bytecode but the optimization is not done
 deterministically either. Closing and having #32053 as the sole one for
 this issue.

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

Re: [tor-bugs] #32388 [Core Tor/Tor]: sched: When OR connection opens, always indicate the channel is ready for cells

[Tor Bug Tracker & Wiki]

#32388: sched: When OR connection opens, always indicate the channel is ready 
for
cells
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-sched |  Actual Points:
Parent ID:| Points:  0.1
 Reviewer:|Sponsor:
--+
Changes (by pastly):

 * cc: pastly (added)


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

[tor-bugs] #32389 [Applications/Tor Browser]: Sandbox Graphite using RLBox

[Tor Bug Tracker & Wiki]

#32389: Sandbox Graphite using RLBox
-+-
 Reporter:  gk   |  Owner:  tbb-team
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  tbb-security,
 Severity:  Normal   |  GeorgKoppen201911
Actual Points:   |  Parent ID:  #32379
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 We should try to sandbox Graphite using RLBox as a prototype gathering
 some performance and overhead data and helping to decide in which
 direction we want to go further on.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32388 [Core Tor/Tor]: sched: When OR connection opens, always indicate the channel is ready for cells

[Tor Bug Tracker & Wiki]

#32388: sched: When OR connection opens, always indicate the channel is ready 
for
cells
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  tor-sched
Actual Points:|  Parent ID:
   Points:  0.1   |   Reviewer:
  Sponsor:|
--+
 == Problem

 In `channel_tls_handle_state_change_on_orconn()`, when called when the OR
 connection becomes open, we have this snippet of code for when the new
 state is OPEN:

 {{{
 channel_change_state_open(base_chan);
 if (connection_or_num_cells_writeable(conn) > 0) {
   scheduler_channel_wants_writes(base_chan);
 }
 }}}

 So basically, the above means we only indicate the scheduler that the
 channel wants to write if we already have cells on the `outbuf`.

 It basically means that if the channel *scheduler* state is `IDLE`
 (initial opening state), it then ends up in state
 `SCHED_CHAN_WAITING_FOR_CELLS` which then means the scheduler will process
 the channel when a cell is queued on it. But ONLY if the channel had cells
 when it was opened.

 This on its own, as a design, is problematic because then what can make
 the channel transition into a state that allows the scheduler to recognize
 the channel as ready to be processed for cells?
 (`SCHED_CHAN_WAITING_FOR_CELLS`).

 Tor currently has 2 callsites that tells the scheduler that a channel
 "wants to write" data on the wire (`scheduler_channel_wants_writes()`,
 remember that function transition the scheduler state of the channel to
 "waiting for cells"):

 1. It is mentioned above that is when the channel becomes `OPEN`.

 2. The other one is when data is _flushed_ from the outbuf, in
 `connection_or_flushed_some()`.

 So once the channel is opened, we only become in the "wants to write"
 state if we previously had cells in the outbuf, which I can assure you is
 not always the case. And the other way is when we just wrote bytes on the
 network but then how can we do that in the first place?

 == What Is Saving Us

 One question is then: Maybe tor code flow makes it that we always have a
 cell in the outbuf when the channel opens?

 I conducted an experiment which made an Entry node of a client to only
 send 1 cell at a time per mainloop round. This made it that the
 `VERSIONs`, `CERTS` and `NETINFO` cell were sent in 3 different mainloop
 round and thus the client received them with a "delay".

 That was enough for the client's channel to have _nothing_ in the outbuf
 when the channel became `OPEN` that is when the `NETINFO` cell is received
 from the relay which skipped the scheduler state change and thus the
 client channel was stuck there in scheduler `IDLE` mode even though the
 channel was in `OPEN` state.

 What is saving us is because the very first thing we write on the wire,
 `VERSIONS` cell, calls the (2) callsite that tells the scheduler to go in
 "waiting for cells" state. And from there, the channel stays in that
 state.

 For now, this seems to be "fine" but any future changes like for instance
 where we wanted to have everything that writes on the `outbuf` to go
 through the scheduler so we can have proper KIST prioritization, will fail
 due to this design.

 == Short-Term Solution

 When the channel opens, we should simply put it in `wants to write` state
 all the time. So even bouncing from `MAINT` to `OPEN` state and vice versa
 will never make some cells stuck in the channel until something is
 explicitly written on the outbuf.

 Furthermore, it should be done in `channel_change_state_()` since this
 affects `channel_t`, it is NOT specific to `channeltls_t`. So in a world
 where we end up with multiple channel type, this whole situation explodes.

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

Re: [tor-bugs] #32367 [Internal Services/Service - nextcloud]: ONLYOFFICE not working?

[Tor Bug Tracker & Wiki]

#32367: ONLYOFFICE not working?
-+-
 Reporter:  gaba |  Owner:
 |  nextcloud-admin@…
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service -  |Version:
  nextcloud  |
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #32267   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gaba):

 * parent:   => #32267


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

Re: [tor-bugs] #32332 [Internal Services/Service - nextcloud]: Set up LDAP authn for nc.tpn

[Tor Bug Tracker & Wiki]

#32332: Set up LDAP authn for nc.tpn
-+-
 Reporter:  ln5  |  Owner:
 |  nextcloud-admin@…
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service -  |Version:
  nextcloud  |
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by anarcat):

 * parent:  #32267 =>


Comment:

 we decided not to block on this, so unlink from parent.

 the goal here is to make sure that accesses get created and revoked when
 we add and removed people from LDAP. but we're not comfortable enabling
 the current LDAP support system as it gives too much access to our LDAP
 server. we don't have time to evaluate all the implications of that and
 possible alternatives.

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

Re: [tor-bugs] #32267 [Internal Services/Service - nextcloud]: move to a private nextcloud instance

[Tor Bug Tracker & Wiki]

#32267: move to a private nextcloud instance
-+-
 Reporter:  anarcat  |  Owner:  ln5
 Type:  project  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service -  |Version:
  nextcloud  |
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Old description:

> in #31540, we agreed to delegate running a dedicated Nextcloud instance
> to riseup.
>
> this ticket tracks the next steps, so far:
>
>  1. create the private instance (riseup)
>  2. point DNS at the private instance (TPA)
>  3. make sure HTTPS works (riseup?)
>  4. #32332 set up LDAP integration, somehow (service admins + riseup)
>  5. move content and users over (gaba + pili + teams)

New description:

 in #31540, we agreed to delegate running a dedicated Nextcloud instance to
 riseup.

 this ticket tracks the next steps, so far:

  1. create the private instance (riseup)
  2. point DNS at the private instance (TPA)
  3. make sure HTTPS works (riseup?)
  4. ~~#32332 set up LDAP integration, somehow (service admins + riseup)~~
  5. move content and users over (gaba + pili + teams)

--

Comment (by anarcat):

 we agreed on postponing the LDAP requirement for now, as we're unsure how
 to proceed and don't want to block deployment. gaba will manage accounts
 by hand 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] #31130 [Applications/Tor Browser]: Use Debian 10 for our Android container images

[Tor Bug Tracker & Wiki]

#31130: Use Debian 10 for our Android container images
---+---
 Reporter:  gk |  Owner:  tbb-team
 Type:  defect | Status:
   |  needs_revision
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201911  |  Actual Points:
Parent ID:  #31127 | Points:  0.5
 Reviewer: |Sponsor:
---+---

Comment (by boklm):

 Replying to [comment:30 sisbell]:

 > It looks very close, I'm still investigating why I get the following
 error in tor-browser project when using apksigner.
 >
 > {{{
 >   inflating: tmp/removed-files
 > Error: Unable to access jarfile /usr/share/apksigner/apksigner.jar
 >
 > }}}

 The path to apksigner in buster is `/usr/lib/android-sdk/build-
 tools/debian/apksigner.jar`.

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

Re: [tor-bugs] #31130 [Applications/Tor Browser]: Use Debian 10 for our Android container images

[Tor Bug Tracker & Wiki]

#31130: Use Debian 10 for our Android container images
---+---
 Reporter:  gk |  Owner:  tbb-team
 Type:  defect | Status:
   |  needs_revision
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201911  |  Actual Points:
Parent ID:  #31127 | Points:  0.5
 Reviewer: |Sponsor:
---+---

Comment (by boklm):

 Replying to [comment:30 sisbell]:
 > I cleaned up the configs. I added an install_jdk flag to prevent openjdk
 install in https-everywhere project. Otherwise the build would break on
 installation.

 I think you don't need an install_jdk flag. You can just define
 `var/pre_pkginst` to empty in http-everywhere.

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

Re: [tor-bugs] #32387 [Core Tor/Tor]: Doxygen: enable source code browser

[Tor Bug Tracker & Wiki]

#32387: Doxygen: enable source code browser
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor31-can
--+
Changes (by nickm):

 * status:  assigned => needs_review


Comment:

 See branch `ticket32387` with PR at
 https://github.com/torproject/tor/pull/1504

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

Re: [tor-bugs] #32384 [Applications/Tor Browser]: trouble loading browser

[Tor Bug Tracker & Wiki]

#32384: trouble loading browser
--+--
 Reporter:  litjoh|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

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


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

[tor-bugs] #32387 [Core Tor/Tor]: Doxygen: enable source code browser

[Tor Bug Tracker & Wiki]

#32387: Doxygen: enable source code browser
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor:  Sponsor31-can  |
---+
 Doxygen has support for outputting an annotated cross-referenced version
 of our C source.  We should enable this to make it more useful.

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

Re: [tor-bugs] #32386 [Core Tor/Tor]: Doxygen: Make output more C-like

[Tor Bug Tracker & Wiki]

#32386: Doxygen: Make output more C-like
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:  0
Parent ID:| Points:  0
 Reviewer:|Sponsor:  Sponsor31-can
--+
Changes (by nickm):

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


Comment:

 Branch is `ticket32386` with PR at
 https://github.com/torproject/tor/pull/1503

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32386 [Core Tor/Tor]: Doxygen: Make output more C-like

[Tor Bug Tracker & Wiki]

#32386: Doxygen: Make output more C-like
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points:  0  |   Reviewer:
  Sponsor:  Sponsor31-can  |
---+
 There are a couple of options we should set to make our doxygen output
 more C-like and less C++-like.

 The TYPEDEF_HIDES_STRUCT option tells doxygen to handle `typedef struct
 foo_t foo_t` by making `foo_t` and `struct foo_t` synonymous.  This lets
 doxygen find documentation that it would otherwise miss: otherwise, if it
 sees documentation for "int func(foo_t *)" and a prototype for "int
 func(struct foo_t)", it will think that the prototype is undocumented.

 The HIDE_SCOPE_NAMES option tells doxygen to describe a member "member" of
 a struct "container" as "member", not "container::member".

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

Re: [tor-bugs] #31130 [Applications/Tor Browser]: Use Debian 10 for our Android container images

[Tor Bug Tracker & Wiki]

#31130: Use Debian 10 for our Android container images
---+---
 Reporter:  gk |  Owner:  tbb-team
 Type:  defect | Status:
   |  needs_revision
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201911  |  Actual Points:
Parent ID:  #31127 | Points:  0.5
 Reviewer: |Sponsor:
---+---
Changes (by gk):

 * keywords:  tbb-rbm, TorBrowserTeam201911R => tbb-rbm,
   TorBrowserTeam201911
 * status:  needs_review => needs_revision


Comment:

 Replying to [comment:30 sisbell]:
 > I cleaned up the configs. I added an install_jdk flag to prevent openjdk
 install in https-everywhere project. Otherwise the build would break on
 installation.
 >
 > https://github.com/sisbell/tor-browser-
 build/commit/1291e758e91784d739c9051873dc07073811df16
 >
 > It looks very close, I'm still investigating why I get the following
 error in tor-browser project when using apksigner.
 >
 > {{{
 >   inflating: tmp/removed-files
 > Error: Unable to access jarfile /usr/share/apksigner/apksigner.jar
 >
 > }}}

 Once you fixed that bit, please add the ticket back into `needs_review`.
 And please address *all* comments before putting a ticket into
 `needs_review` (That does not necessarily mean you need to fix all
 concerns as they might not be valid, but they should be addressed)

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

Re: [tor-bugs] #32385 [Core Tor/Tor]: doxygen: respect --enable-fatal-warnings

[Tor Bug Tracker & Wiki]

#32385: doxygen: respect --enable-fatal-warnings
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  doxygen   |  Actual Points:
Parent ID:| Points:  0
 Reviewer:|Sponsor:  Sponsor31-can
--+
Changes (by nickm):

 * status:  assigned => needs_review


Comment:

 See branch `ticket32385` with PR at
 https://github.com/torproject/tor/pull/1502

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32385 [Core Tor/Tor]: doxygen: respect --enable-fatal-warnings

[Tor Bug Tracker & Wiki]

#32385: doxygen: respect --enable-fatal-warnings
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal |   Keywords:  doxygen
Actual Points: |  Parent ID:
   Points:  0  |   Reviewer:
  Sponsor:  Sponsor31-can  |
---+
 Doxygen has an option to fail with an error if any warning message occurs.
 We can enable it, if we disable missing documentation warnings.  We should
 have another option to turn missing documentation warnings back on.

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

Re: [tor-bugs] #31130 [Applications/Tor Browser]: Use Debian 10 for our Android container images

[Tor Bug Tracker & Wiki]

#31130: Use Debian 10 for our Android container images
+--
 Reporter:  gk  |  Owner:  tbb-team
 Type:  defect  | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201911R  |  Actual Points:
Parent ID:  #31127  | Points:  0.5
 Reviewer:  |Sponsor:
+--
Changes (by sisbell):

 * keywords:  tbb-rbm, TorBrowserTeam201911 => tbb-rbm,
   TorBrowserTeam201911R
 * status:  needs_revision => needs_review


Comment:

 I cleaned up the configs. I added an install_jdk flag to prevent openjdk
 install in https-everywhere project. Otherwise the build would break on
 installation.

 https://github.com/sisbell/tor-browser-
 build/commit/1291e758e91784d739c9051873dc07073811df16

 It looks very close, I'm still investigating why I get the following error
 in tor-browser project when using apksigner.

 {{{
   inflating: tmp/removed-files
 Error: Unable to access jarfile /usr/share/apksigner/apksigner.jar

 }}}

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

Re: [tor-bugs] #32053 [Applications/Tor Browser]: macOS bundles for Tor Browser 9.0a8 are not reproducible

[Tor Bug Tracker & Wiki]

#32053: macOS bundles for Tor Browser 9.0a8 are not reproducible
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Immediate|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201911, tbb-9.0-must,  |  Actual Points:
  tbb-9.0-issues, tbb-regression,|
  tbb-9.0.1-can, GeorgKoppen201911   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by alexcrichton):

 I've opened up https://bugs.llvm.org/show_bug.cgi?id=43909 and will track
 that, I'm attempting to use LLVM's automatic test case reduction tools but
 it's likely going to take quite some time due to how large the module is.

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

Re: [tor-bugs] #32384 [- Select a component]: trouble loading browser

[Tor Bug Tracker & Wiki]

#32384: trouble loading browser
--+
 Reporter:  litjoh|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by litjoh):

 * Attachment "torfirst.PNG" added.

 what comes up first

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32384 [- Select a component]: trouble loading browser

[Tor Bug Tracker & Wiki]

#32384: trouble loading browser
+--
 Reporter:  litjoh  |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Component:  - Select a component
  Version:  |   Severity:  Normal
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
 when i first select the tor icon on my desktop it usually goes to a red
 screen and i get a message that tor isnt working in this browser (the tor
 browser)

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

Re: [tor-bugs] #32053 [Applications/Tor Browser]: macOS bundles for Tor Browser 9.0a8 are not reproducible

[Tor Bug Tracker & Wiki]

#32053: macOS bundles for Tor Browser 9.0a8 are not reproducible
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Immediate|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201911, tbb-9.0-must,  |  Actual Points:
  tbb-9.0-issues, tbb-regression,|
  tbb-9.0.1-can, GeorgKoppen201911   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 Replying to [comment:22 alexcrichton]:
 > Thanks for the files! Also wow those are huge.
 >
 > I've managed to reproduce this and it indeed looks like an LLVM issue!
 (yay?) I ran `opt -O3 style.no-opt.bc -o foo.bc && md5sum foo.bc` and I've
 gotten two different checksums after running a few times. I also just
 checked out the most recent LLVM trunk and I can see the same issue there.
 >
 > I don't think there's anything else needed from rustc here, with these
 bitcode files it should be enough to just run these through LLVM's `opt`
 tool to find a reduction that is smaller than 90MB to report :). That
 being said I suspect that an LLVM bug could go ahead and get opened for
 this and LLVM folks might be able to help with the reduction here.
 >
 > It's good to point out the cross-compile aspect, although I suspect that
 likely just happens to tickle the right portion of LLVM, and it's actually
 a bug for all platforms. We'll se though!
 >
 > Do you want me to file the LLVM bug, or would you like to do so?

 Awesome, thanks! Would you mind filing the bug mentioning all the
 necessary info for the llvm folks to look at (I am not sure in which
 components to put and whom to Cc etc.)? You can link to my files, I'll
 keep them there are least until the issue is resolved (Not sure if the
 llvm bug tracker allows such big files added). Please Cc me, if possible
 (gk [@] torproject [.] org).

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

Re: [tor-bugs] #30866 [Core Tor/Tor]: Teach config.c to work with options configured in other modules

[Tor Bug Tracker & Wiki]

#30866: Teach config.c to work with options configured in other modules
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  needs_revision
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #29211| Points:  2
 Reviewer:  teor  |Sponsor:  Sponsor31-can
--+

Comment (by nickm):

 I've rebased as `config_subsys_2` and started making the requested
 changes.  There's a PR at https://github.com/torproject/tor/pull/1501 so I
 can keep an eye on coverage and CI.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32383 [Internal Services/Tor Sysadmin Team]: retire build-arm-* raspi boxes

[Tor Bug Tracker & Wiki]

#32383: retire build-arm-* raspi boxes
-+-
 Reporter:  anarcat  |  Owner:  anarcat
 Type:  task | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin   |Version:
  Team   |
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 there are three boxes in our infra that are just too slow to provide the
 service they were designed for. they are the build-
 arm-0[123].torproject.org boxes and should be retired.

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

Re: [tor-bugs] #32053 [Applications/Tor Browser]: macOS bundles for Tor Browser 9.0a8 are not reproducible

[Tor Bug Tracker & Wiki]

#32053: macOS bundles for Tor Browser 9.0a8 are not reproducible
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Immediate|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201911, tbb-9.0-must,  |  Actual Points:
  tbb-9.0-issues, tbb-regression,|
  tbb-9.0.1-can, GeorgKoppen201911   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by alexcrichton):

 Thanks for the files! Also wow those are huge.

 I've managed to reproduce this and it indeed looks like an LLVM issue!
 (yay?) I ran `opt -O3 style.no-opt.bc -o foo.bc && md5sum foo.bc` and I've
 gotten two different checksums after running a few times. I also just
 checked out the most recent LLVM trunk and I can see the same issue there.

 I don't think there's anything else needed from rustc here, with these
 bitcode files it should be enough to just run these through LLVM's `opt`
 tool to find a reduction that is smaller than 90MB to report :). That
 being said I suspect that an LLVM bug could go ahead and get opened for
 this and LLVM folks might be able to help with the reduction here.

 It's good to point out the cross-compile aspect, although I suspect that
 likely just happens to tickle the right portion of LLVM, and it's actually
 a bug for all platforms. We'll se though!

 Do you want me to file the LLVM bug, or would you like to do so?

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

Re: [tor-bugs] #32231 [Metrics/CollecTor]: Lost some metrics due to broker host migration

[Tor Bug Tracker & Wiki]

#32231: Lost some metrics due to broker host migration
---+--
 Reporter:  cohosh |  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by karsten):

 Replying to [comment:6 cohosh]:
 > Yes, these files are okay to delete. Thanks karsten!

 Done!

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