Re: [tor-bugs] #31775 [Webpages/Website]: Submenu on people page clobbers text

[Tor Bug Tracker & Wiki]

#31775: Submenu on people page clobbers text
--+--
 Reporter:  arma  |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by arma):

 * Attachment "screenshot-31775.png" added.


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

[tor-bugs] #31775 [Webpages/Website]: Submenu on people page clobbers text

[Tor Bug Tracker & Wiki]

#31775: Submenu on people page clobbers text
--+--
 Reporter:  arma  |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 On the people page:
 https://www.torproject.org/about/people/
 there is a submenu listing "History, People, Sponsors, Reports, Jobs,
 Trademark" and as I scroll down, these words overlap confusingly with the
 words in the biographies of 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

[tor-bugs] #31774 [Webpages/Website]: "#board" anchor on people page doesn't work

[Tor Bug Tracker & Wiki]

#31774: "#board" anchor on people page doesn't work
--+--
 Reporter:  arma  |  Owner:  hiro
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 https://www.torproject.org/about/people/#board
 doesn't send me to the 'board' section of the page.

 Whereas
 https://www.torproject.org/about/people/#core
 does send me to the core section.

 In the html, I see a
 {{{
 
 }}}
 but there is no corresponding {{{id="board"}}} anywhere.

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

Re: [tor-bugs] #31512 [Applications/Tor Browser]: Fingerprinting of Tor Browser

[Tor Bug Tracker & Wiki]

#31512: Fingerprinting of Tor Browser
--+--
 Reporter:  thelamper |  Owner:  tbb-team
 Type:  enhancement   | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  invalid
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by Thorin):

 Replying to [comment:8 thelamper]:
 > Does having javascript disabled make it harder to fingerprint individual
 Tor users

 Absolutely. Reducing the attack surface (by disabling JS) removes a
 **lot** of the FPing metrics possible.

 > Or is it generally viewed by the Tor Project as safe (ie non-
 fingerprintable) for Tor users to browse the web with javascript enabled?

 My view is that it's always a work in progress but the anti-FPing in Tor
 Browser is very mature at this stage. Instead, adapt to your threat model,
 and use the security slider.

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

Re: [tor-bugs] #31512 [Applications/Tor Browser]: Fingerprinting of Tor Browser

[Tor Bug Tracker & Wiki]

#31512: Fingerprinting of Tor Browser
--+--
 Reporter:  thelamper |  Owner:  tbb-team
 Type:  enhancement   | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  invalid
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by thelamper):

 Both of those fingerprinting tests (brax.me/geo/) and (tor.triop.se/) fail
 with javascript disabled ie they cannot generate a 'unique identifying
 number'.

 Does having javascript disabled make it harder to fingerprint individual
 Tor users ie it reduces the data leaked by the user's browser to the
 website in question? The panopticlick and amiunique tests suggest that
 disabling JS helps users blend in with the crowd by reducing their
 uniqueness.

 Or is it generally viewed by the Tor Project as safe (ie non-
 fingerprintable) for Tor users to browse the web with javascript enabled?

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

Re: [tor-bugs] #31772 [Core Tor/Tor]: MAPADDRESS control command

[Tor Bug Tracker & Wiki]

#31772: MAPADDRESS control command
-+-
 Reporter:  kowenki  |  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.5
 Severity:  Normal   | Resolution:
 Keywords:  041-backport 041-regression? |  Actual Points:  .2
  042-must   |
Parent ID:   | Points:  .2
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by teor):

 * status:  needs_review => merge_ready


Comment:

 Seems like a trivial fix.
 Let's merge to master, check CI is happy, then 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

Re: [tor-bugs] #31089 [Core Tor/Tor]: Consider using data-URI to embed how_tor_works_thumb.png image into tor-exit-notice.html

[Tor Bug Tracker & Wiki]

#31089: Consider using data-URI to embed how_tor_works_thumb.png image into tor-
exit-notice.html
-+-
 Reporter:  rl1987   |  Owner:  (none)
 Type:  enhancement  | Status:  closed
 Priority:  Low  |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Trivial  | Resolution:  fixed
 Keywords:  security-low, 029-backport,  |  Actual Points:  0.2
  035-backport, 040-backport, 041-backport,  |
  consider-backport-after-0421   |
Parent ID:   | Points:  0.2
 Reviewer:  teor |Sponsor:
-+-
Changes (by teor):

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


Comment:

 (And the most likely breakage is a missing image in some browsers, which
 is better than a low-severity privacy 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] #31772 [Core Tor/Tor]: MAPADDRESS control command

[Tor Bug Tracker & Wiki]

#31772: MAPADDRESS control command
-+-
 Reporter:  kowenki  |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.5
 Severity:  Normal   | Resolution:
 Keywords:  041-backport 041-regression? |  Actual Points:  .2
  042-must   |
Parent ID:   | Points:  .2
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by nickm):

 * status:  accepted => needs_review


Comment:

 CI has passed.

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

Re: [tor-bugs] #30743 [Core Tor/Tor]: Write a coccinelle script to catch increment/decrement calls inside log_debug().

[Tor Bug Tracker & Wiki]

#30743: Write a coccinelle script to catch increment/decrement calls inside
log_debug().
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  needs_information
 Priority:  Medium|  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:  catalyst  |Sponsor:
--+
Changes (by catalyst):

 * status:  needs_review => needs_information


Comment:

 Replying to [comment:3 nickm]:
 > See branch `ticket30743` with PR at
 https://github.com/torproject/tor/pull/1322 .  Running it over the source
 code with the apply.sh script in #31705 found no additional instances of
 bugs like #30628.
 Thanks! Mostly looks good. I manually verified that it detects the bug
 fixed in #30628.

 Do you think it needs a changes file? I think it would be useful it the
 changes file (and commit message) pointed at an example of a bug that this
 would catch.

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

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

[Tor Bug Tracker & Wiki]

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

Comment (by phw):

 Replying to [comment:27 karsten]:
 > I probably asked this before and forgot the answer: where would I find
 the spec for parsing the format? Thanks in advance!
 [[br]]
 The spec is still on my todo list. Here's a quick-and-dirty summary, so
 you don't need to block on me:
 * A metrics file starts with `bridgedb-stats-end -MM-DD HH:MM:SS (SECS
 s)`
 * The second line determines the version of the format. It currently is
 `bridgedb-stats-version 1.0`
 * From here on, we have multiple `bridgedb-metric-count` lines. They are
 structured as follows:
   * `bridgedb-metric-count DIST.PROTO.CC.[success|fail].none NUM`
   * `DIST` is BridgeDB's distribution mechanism, which currently is
 `http`, `email`, or `moat`.
   * `PROTO` is the obfuscation protocol, which currently is `obfs2`,
 `obfs3`, `obfs4`, `scramblesuit`, or `fte`.
   * `CC` is our two-letter country code.
   * The second-to-last field is either `success` or `fail` depending on if
 the BridgeDB request succeeded or not.
   * The last field is currently `none` but will eventually be a anomaly
 score, perhaps normalised to [0, 1]. I would suggest to ignore it for now.
   * `NUM` is the approximate number of requests, rounded to the next
 multiple of 10.

 I'll follow up with the spec once it's done. I hope this is good enough to
 make progress in the meanwhile.

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

Re: [tor-bugs] #31657 [Core Tor/Tor]: Rephrase "missing descriptors" notice log to be less confusing

[Tor Bug Tracker & Wiki]

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

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


Comment:

 Backporting to 0.3.5 and forward.

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

Re: [tor-bugs] #31089 [Core Tor/Tor]: Consider using data-URI to embed how_tor_works_thumb.png image into tor-exit-notice.html

[Tor Bug Tracker & Wiki]

#31089: Consider using data-URI to embed how_tor_works_thumb.png image into tor-
exit-notice.html
-+-
 Reporter:  rl1987   |  Owner:  (none)
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Low  |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Trivial  | Resolution:
 Keywords:  security-low, 029-backport,  |  Actual Points:  0.2
  035-backport, 040-backport, 041-backport,  |
  consider-backport-after-0421   |
Parent ID:   | Points:  0.2
 Reviewer:  teor |Sponsor:
-+-
Changes (by nickm):

 * milestone:  Tor: 0.4.1.x-final => Tor: 0.2.9.x-final


Comment:

 Merged to 0.2.9 and forward.  The risk is low; the severity is low; and
 this will be easy for people to work around if anything breaks.

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

Re: [tor-bugs] #25611 [Core Tor/Stem]: Integ test for MAPADDRESS

[Tor Bug Tracker & Wiki]

#25611: Integ test for MAPADDRESS
---+--
 Reporter:  atagar |  Owner:  atagar
 Type:  defect | Status:  needs_review
 Priority:  Low|  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Minor  | Resolution:
 Keywords:  testing|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by nickm):

 FYI, this test will fail with Tor 0.4.1 and 0.4.2, until #31772 is fixed.
 It should work fine with 0.4.0 and earlier.

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

Re: [tor-bugs] #31772 [Core Tor/Tor]: MAPADDRESS control command

[Tor Bug Tracker & Wiki]

#31772: MAPADDRESS control command
-+-
 Reporter:  kowenki  |  Owner:  nickm
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.5
 Severity:  Normal   | Resolution:
 Keywords:  041-backport 041-regression? |  Actual Points:  .2
  042-must   |
Parent ID:   | Points:  .2
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by nickm):

 * actualpoints:   => .2


Comment:

 I have a potential fix in branch `bug31772_041`.  I've made a PR at
 https://github.com/torproject/tor/pull/1336 .  kowenki, does this work for
 you?

 I've tested this by hand and it works well for me.  I've also written a
 stem integration test that we can use here: see #25611.  I have confirmed
 that my code passes this stem integration test, and that maint-0.4.1 does
 not pass without it.

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

Re: [tor-bugs] #25611 [Core Tor/Stem]: Integ test for MAPADDRESS

[Tor Bug Tracker & Wiki]

#25611: Integ test for MAPADDRESS
---+--
 Reporter:  atagar |  Owner:  atagar
 Type:  defect | Status:  needs_review
 Priority:  Low|  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Minor  | Resolution:
 Keywords:  testing|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by nickm):

 * status:  new => needs_review


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

Re: [tor-bugs] #25611 [Core Tor/Stem]: Integ test for MAPADDRESS

[Tor Bug Tracker & Wiki]

#25611: Integ test for MAPADDRESS
---+
 Reporter:  atagar |  Owner:  atagar
 Type:  defect | Status:  new
 Priority:  Low|  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Minor  | Resolution:
 Keywords:  testing|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by nickm):

 I have written an offline integration test for mapaddress; I don't know if
 it will do everything you want here, but it should be sufficient to
 prevent another occurrence of #31772.  The branch is called
 `test_mapaddress_offline` and the PR is at
 https://github.com/torproject/stem/pull/22 .

 Please let me know if you'd like me to open a separate ticket for this.

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

Re: [tor-bugs] #31711 [- Select a component]: Spread the word about the Digital Climate Strike on Tor's social media

[Tor Bug Tracker & Wiki]

#31711: Spread the word about the Digital Climate Strike on Tor's social media
--+
 Reporter:  teor  |  Owner:  steph
 Type:  task  | Status:  closed
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:  #31708| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

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


Comment:

 I think Steph has this covered.

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

Re: [tor-bugs] #31710 [Webpages/Blog]: Write blog post about the digital climate strike, and how Tor makes activists safer

[Tor Bug Tracker & Wiki]

#31710: Write blog post about the digital climate strike, and how Tor makes
activists safer
---+
 Reporter:  teor   |  Owner:  teor
 Type:  task   | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Webpages/Blog  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID:  #31708 | Points:
 Reviewer: |Sponsor:
---+
Changes (by teor):

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


Comment:

 It's up on the blog.

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

Re: [tor-bugs] #30917 [Core Tor/Tor]: Add instructions for making a new maint branch to EndOfLifeTor.md, and rename the file

[Tor Bug Tracker & Wiki]

#30917: Add instructions for making a new maint branch to EndOfLifeTor.md, and
rename the file
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  041-should, sponsor31-maybe, |  Actual Points:
  network-team-roadmap-september |
Parent ID:  #30839   | Points:  0.5
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  041-should, sponsor31-maybe => 041-should, sponsor31-maybe,
 network-team-roadmap-september


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

Re: [tor-bugs] #22893 [Core Tor/Tor]: prop224: Make intro point per-service and not per-descriptor

[Tor Bug Tracker & Wiki]

#22893: prop224: Make intro point per-service and not per-descriptor
-+-
 Reporter:  dgoulet  |  Owner:  teor
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Very High|  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  network-team-roadmap-september,  |  Actual Points:
  tor-hs, prop224-extra, 034-triage-20180328,|
  034-removed-20180328   |
Parent ID:  #29995   | Points:  7
 Reviewer:   |Sponsor:
 |  Sponsor27-must
-+-
Changes (by teor):

 * keywords:  tor-hs, prop224-extra, 034-triage-20180328,
 034-removed-20180328 =>
 network-team-roadmap-september, tor-hs, prop224-extra,
 034-triage-20180328, 034-removed-20180328


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

Re: [tor-bugs] #31570 [Core Tor/Tor]: INTERNAL ERROR: raw assertion failed (core dump) in termux

[Tor Bug Tracker & Wiki]

#31570: INTERNAL ERROR: raw assertion failed (core dump) in termux
-+-
 Reporter:  foremtehan   |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  042-should, regression?, mmap,   |  Actual Points:  .1
  android, crash BugSmashFund dgoulet-merge  |
  041-backport   |
Parent ID:   | Points:
 Reviewer:  ahf  |Sponsor:
-+-
Changes (by nickm):

 * keywords:
 042-should, regression?, mmap, android, crash BugSmashFund dgoulet-
 merge
 =>
 042-should, regression?, mmap, android, crash BugSmashFund dgoulet-
 merge 041-backport
 * milestone:  Tor: 0.4.2.x-final => Tor: 0.4.1.x-final


Comment:

 Backported to 0.4.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] #31673 [Core Tor/Tor]: Deprecated use of

[Tor Bug Tracker & Wiki]

#31673: Deprecated use of 
-+-
 Reporter:  dgoulet  |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  029-backport, 035-backport   |  Actual Points:
  040-backport 041-backport 042-must |
Parent ID:   | Points:  0.1
 Reviewer:  nickm|Sponsor:
-+-
Changes (by nickm):

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


Comment:

 Merged to 0.2.9 and forward.

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

Re: [tor-bugs] #31552 [Core Tor/Tor]: --disable-module-dirauth broken (missing symbols)

[Tor Bug Tracker & Wiki]

#31552: --disable-module-dirauth broken (missing symbols)
-+-
 Reporter:  LarryBitcoin |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.5
 Severity:  Normal   | Resolution:  fixed
 Keywords:  build, configure, features,  |  Actual Points:  .1
  modules, regression, 041-should, 041-backport  |
Parent ID:   | Points:
 Reviewer:  catalyst |Sponsor:
 |  Sponsor31-can
-+-
Changes (by nickm):

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


Comment:

 Merged to 0.4.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] #31687 [Core Tor/Tor]: FreeBSD compilation warns with Tor 0.4.1.5

[Tor Bug Tracker & Wiki]

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

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


Comment:

 Merged to 0.3.5, 0.4.0, and forward.

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

Re: [tor-bugs] #31696 [Core Tor/Tor]: Assertion failure in map-anon.c:218

[Tor Bug Tracker & Wiki]

#31696: Assertion failure in map-anon.c:218
-+-
 Reporter:  gk   |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.5
 Severity:  Normal   | Resolution:  fixed
 Keywords:  regression, crash, 041-regression,   |  Actual Points:  .1
  BugSmashFund, 042-must, 041-backport   |
Parent ID:   | Points:  .1
 Reviewer:  ahf  |Sponsor:
-+-
Changes (by nickm):

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


Comment:

 Merged to 0.4.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

[tor-bugs] #31773 [Applications/TorBirdy]: update torbirdy compatibility to work with Thunderbird 68.1.0

[Tor Bug Tracker & Wiki]

#31773: update torbirdy compatibility to work with Thunderbird 68.1.0
-+---
 Reporter:  cypherpunks  |  Owner:  sukhbir
 Type:  defect   | Status:  new
 Priority:  Medium   |  Component:  Applications/TorBirdy
  Version:   |   Severity:  Normal
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
 After upgrading Thunderbird to 68.1.0
 torbirdy no longer shows as compatible

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

Re: [tor-bugs] #30716 [Circumvention/Obfs4]: Improve the obfs4 obfuscation protocol

[Tor Bug Tracker & Wiki]

#30716: Improve the obfs4 obfuscation protocol
-+-
 Reporter:  phw  |  Owner:  phw
 Type:  task | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Obfs4  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  sponsor28, anti-censorship-roadmap-  |  Actual Points:
  august |
Parent ID:   | Points:  20
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-

Comment (by phw):

 We briefly discussed the interaction between Tor's WF defences and obfs4's
 flow obfuscation in #tor-dev. Here's a summary:
 * We want a clear separation of responsibilities: Tor's circuit padding
 defends against WF attacks while obfs4 defends against traffic
 classification.
 * We want defence in depth. If an adversary breaks obfs4, she should not
 be able to fingerprint the encapsulated Tor stream, to learn what website
 the user is visiting.
 * That said, the defence in depth should come with as little overhead as
 possible. Every padding byte (be it from obfs4 or the application) is a
 byte that is no longer goodput. If performance suffers too much, users
 will turn to other circumvention tools.

 Here are some additional research questions:

 * Both obfs4 and Tor add padding to defend against traffic classifiers and
 WF attacks, respectively. Can we combine these two systems in a smart way
 that minimises overhead while retaining our security properties? (Keep in
 mind that obfs4 is only present between client and bridge while Tor's WF
 defences may be present between client and middle relay.)

 * Can obfs4's padding negatively affect Tor's padding and vice versa?

 * How does the application data that goes into obfs4 affect our resistance
 to traffic classifiers? In other words: Is obfs4-transporting-tor more
 resistant to classifiers than obfs4-transporting-vpn?

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

Re: [tor-bugs] #29206 [Circumvention/Snowflake]: New design for client -- server protocol for Snowflake

[Tor Bug Tracker & Wiki]

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

Comment (by cohosh):

 Thanks for the feedback! I added a bunch of new commits onto the
 [https://github.com/cohosh/snowflake/compare/sequencing sequencing branch]

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

Re: [tor-bugs] #31772 [Core Tor/Tor]: MAPADDRESS control command

[Tor Bug Tracker & Wiki]

#31772: MAPADDRESS control command
-+-
 Reporter:  kowenki  |  Owner:  nickm
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.5
 Severity:  Normal   | Resolution:
 Keywords:  041-backport 041-regression? |  Actual Points:
  042-must   |
Parent ID:   | Points:  .2
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by nickm):

 * owner:  (none) => nickm
 * status:  new => accepted
 * points:   => .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] #31772 [Core Tor/Tor]: MAPADDRESS control command

[Tor Bug Tracker & Wiki]

#31772: MAPADDRESS control command
-+-
 Reporter:  kowenki  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.1.5
 Severity:  Normal   | Resolution:
 Keywords:  041-backport 041-regression? |  Actual Points:
  042-must   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by nickm):

 * keywords:   => 041-backport 041-regression? 042-must
 * sponsor:   => Sponsor31-can
 * milestone:   => Tor: 0.4.2.x-final


Comment:

 This looks like a parsing bug to me; I'll investigate.  The likeliest
 cause is the controller refactoring in 0.4.1.x.

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

 * status:  needs_revision => needs_review


Comment:

 (practracker failure 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

[tor-bugs] #31772 [Core Tor/Tor]: MAPADDRESS control command

[Tor Bug Tracker & Wiki]

#31772: MAPADDRESS control command
--+--
 Reporter:  kowenki   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Component:  Core Tor/Tor
  Version:  Tor: 0.4.1.5  |   Severity:  Normal
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
 I'm using the control socket to execute MAPADDRESS commands.
 Since TorBrowser 8.5.5 (Linux64) with Tor 0.4.1.5 the behavior changed.

 On TorBrowser 8.5.4 (Linux64) with Tor 0.4.0.5 the following command
 worked:

 MAPADDRESS *.torproject.org=127.0.0.1
 250 *.torproject.org=127.0.0.1

 On TorBrowser 8.5.5 (Linux64) with Tor 0.4.1.5 the following happens:

 MAPADDRESS *.torproject.org=127.0.0.1
 512 syntax error: not enough arguments to mapaddress.

 However, I found out that the following works:

 MAPADDRESS foo *.torproject.org=127.0.0.1
 250 *.torproject.org=127.0.0.1


 I could not find any information about a change in the MAPADDRESS command
 specification.

 Did the MAPADDRESS command change or may this be a bug in the command
 parsing?

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

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

[Tor Bug Tracker & Wiki]

#31718: Update DNS records for .ooni.torproject.org domains
-+-
 Reporter:  hellais  |  Owner:  anarcat
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 i have disabled certificate pinning on ooni.torproject.org around 15
 minutes ago. it should therefore expire in 60 days exactly, which is about
 on saturday november 16th at 19:30UTC. assuming we don't want to do this
 transition on a saturday, we should probably look into this again on
 november 18th.

 i documented a bit how HPKP works in:

 https://help.torproject.org/tsa/howto/letsencrypt/#index3h1

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

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

[Tor Bug Tracker & Wiki]

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

Comment (by karsten):

 Gah, I misspelled the directory name in one place. Fixed, files are coming
 in as they should. Thanks!

 I probably asked this before and forgot the answer: where would I find the
 spec for parsing the format? Thanks in advance!

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

Re: [tor-bugs] #31771 [Internal Services/Service - trac]: bugs.torproject.org has some issue with the certificate

[Tor Bug Tracker & Wiki]

#31771: bugs.torproject.org has some issue with the certificate
--+
 Reporter:  antonela  |  Owner:  qbi
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by weasel):

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


Comment:

 the spec.tpo service and the vanity vhosts (bugs, wiki, safetyboard, etc;
 i.e. all the things that are only an apache config but no data) were not
 previously included in the static_mirror_web role.

 This has now been fixed, thanks for the report.

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

Re: [tor-bugs] #31771 [Internal Services/Service - trac]: bugs.torproject.org has some issue with the certificate

[Tor Bug Tracker & Wiki]

#31771: bugs.torproject.org has some issue with the certificate
--+--
 Reporter:  antonela  |  Owner:  qbi
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by weasel):

 sounds about right
 curl  --resolve 'bugs.torproject.org:443:116.202.120.165'  -I
 https://bugs.torproject.org/
 curl: (60) SSL certificate problem: unable to get local issuer certificate

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

Re: [tor-bugs] #30716 [Circumvention/Obfs4]: Improve the obfs4 obfuscation protocol

[Tor Bug Tracker & Wiki]

#30716: Improve the obfs4 obfuscation protocol
-+-
 Reporter:  phw  |  Owner:  phw
 Type:  task | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Circumvention/Obfs4  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  sponsor28, anti-censorship-roadmap-  |  Actual Points:
  august |
Parent ID:   | Points:  20
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-

Comment (by phw):

 Here's a brief overview of where we're at.  We should improve both obfs4's
 payload ''and'' flow obfuscation. My
 [https://trac.torproject.org/projects/tor/ticket/30716#comment:10 above
 comment] gave an overview of how we can improve flow obfuscation. To
 clarify: blindly incorporating WF defences is unlikely to succeed. We
 should instead extend obfs4's flow obfuscation and build an evaluation
 framework (which can be inspired by WF work).

 The main issue with obfs4's payload obfuscation is that it consists
 entirely of uniformly distributed bytes for which Wang et al. built a
 reliable classifier in their CCS'15 paper.  We should find a way to reduce
 obfs4's per-packet entropy – at least for the first ''n'' packets,
 assuming that our adversary classifies a flow in the first ''n'' packets.
 Keeping flow state is costly, after all.

 We identified two approaches for reducing obfs4's per-packet entropy:

 1. Adopting LibFTE. We could derive regular expressions from obfs4's
 shared secret that we then feed into LibFTE. These regular expressions
 should make obfs4 look like "a protocol with structure."

 2. Building an entropy "modifier". A silly implementation of this idea
 could insert a 0-byte after every second obfs4 byte, which would reduce
 the stream's entropy.  Again, the way this entropy modifier works should
 be derived from obfs4's shared secret.  We should parameterise the
 modifier with an inflation factor ''i'', which we can gradually scale back
 to 0, to improve goodput once our adversary classified the flow.

 As cohosh pointed out, the challenge lies in making these improvements
 without having us stand out.

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

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

[Tor Bug Tracker & Wiki]

#31718: Update DNS records for .ooni.torproject.org domains
-+-
 Reporter:  hellais  |  Owner:  anarcat
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by hellais):

 So we looked into this with @anarcat and encountered the following issues:

 - The current setup has both HSTS and certificate pinning enabled for the
 ooni.torproject.org website
 - It is not straightforward to do custom HTTPS changes on the current ooni
 hosting service (netlify)

 Since the maxage for the certificate pinning is set to 60 days we will
 need to wait for that amount of time before we are able to migrate over.

 In the meantime @anarcat is going to see how to disable the certificate
 pinning headers from the ooni.torproject.org host config, so that we can
 begin waiting the 60 days after which we can proceed with the CNAME plan
 as mentioned above.

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

Re: [tor-bugs] #31285 [Circumvention/Snowflake]: Browsers accumulate permanently open UDP sockets over time

[Tor Bug Tracker & Wiki]

#31285: Browsers accumulate permanently open UDP sockets over time
-+
 Reporter:  cypherpunks  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  snowflake-webextension   |  Actual Points:
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+

Comment (by cypherpunks):

 I checked, and none of them show up in that list. I assume they're not
 being opened by Firefox itself so it didn't log them, but were instead
 opened at a lower level inside some code that Firefox calls. Would Firefox
 be aware of what happens inside the ICE code or the addon? The persistent
 TCP connection to the Snowflake agent is listed though.

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

Re: [tor-bugs] #18935 [Applications/Tor Browser]: MS bugs - Danger! Windows updates break everything on their way!

[Tor Bug Tracker & Wiki]

#18935: MS bugs - Danger! Windows updates break everything on their way!
--+--
 Reporter:  bugzilla  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:  fixed
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 Hah, works flawlessly for years. It's not a bug in Firefox. Read this
 ticket carefully.

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

Re: [tor-bugs] #31771 [Internal Services/Service - trac]: bugs.torproject.org has some issue with the certificate

[Tor Bug Tracker & Wiki]

#31771: bugs.torproject.org has some issue with the certificate
--+--
 Reporter:  antonela  |  Owner:  qbi
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by arma):

 Theory: the new web-fsn-01.tpo rotation webserver is busted.

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

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

[Tor Bug Tracker & Wiki]

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

Comment (by phw):

 Here's our latest rsync attempt:
 {{{
 1568738247:metrics:<36>Sep 17 16:37:27 collector-ssh-wrap[29644]: The
 SSH_ORIGINAL_COMMAND ('rsync --server -logDtpre.iLsfxC .
 /srv/collector.torproject.org/collector/in/bridgedb-stats/') is not on the
 whitelist
 1568738247:metrics:rsync: connection unexpectedly closed (0 bytes received
 so far) [sender]
 1568738247:metrics:rsync error: error in rsync protocol data stream (code
 12) at io.c(235) [sender=3.1.2]
 }}}

 It looks like the same issue as the one we recently solved in #31515.

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

Re: [tor-bugs] #29206 [Circumvention/Snowflake]: New design for client -- server protocol for Snowflake

[Tor Bug Tracker & Wiki]

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

 * status:  needs_review => needs_revision


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

Re: [tor-bugs] #31771 [Internal Services/Service - trac]: bugs.torproject.org has some issue with the certificate

[Tor Bug Tracker & Wiki]

#31771: bugs.torproject.org has some issue with the certificate
--+--
 Reporter:  antonela  |  Owner:  qbi
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by antonela):

 * Attachment "web-fsn-01_torproject_org.crt" 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] #31771 [Internal Services/Service - trac]: bugs.torproject.org has some issue with the certificate

[Tor Bug Tracker & Wiki]

#31771: bugs.torproject.org has some issue with the certificate
--+--
 Reporter:  antonela  |  Owner:  qbi
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 When I want to visit https://bugs.torproject.org/ Firefox says:

 "Error code: SEC_ERROR_UNKNOWN_ISSUER"

 OS: MacOS Mojave 10.14
 Chrome https://share.riseup.net/#CYonUWZTp0NFD7xUGnqKwg
 Firefox https://share.riseup.net/#oGJLGO3dncEzfaqZfrEhFg

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

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

[Tor Bug Tracker & Wiki]

#31763: relay-search lists flakey as down for an hour or two, when it's never 
been
reachable
--+--
 Reporter:  arma  |  Owner:  metrics-team
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by cohosh):

 * cc: cohosh, phw (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] #21952 [Applications/Tor Browser]: Onion-location: increasing the use of onion services through automatic redirects and aliasing (was: .Onion everywhere?: increasing the use of onion se

[Tor Bug Tracker & Wiki]

#21952: Onion-location: increasing the use of onion services through automatic
redirects and aliasing
-+-
 Reporter:  linda|  Owner:  tbb-
 |  team
 Type:  project  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, tor-hs, network-team-   |  Actual Points:
  roadmap-november   |
Parent ID:  #30024   | Points:  6
 Reviewer:   |Sponsor:
 |  Sponsor27-must
-+-

Comment (by asn):

 This ticket now represents work on Onion-location

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

Re: [tor-bugs] #22893 [Core Tor/Tor]: prop224: Make intro point per-service and not per-descriptor

[Tor Bug Tracker & Wiki]

#22893: prop224: Make intro point per-service and not per-descriptor
-+-
 Reporter:  dgoulet  |  Owner:  teor
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Very High|  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224-extra,   |  Actual Points:
  034-triage-20180328, 034-removed-20180328  |
Parent ID:  #29995   | Points:  7
 Reviewer:   |Sponsor:
 |  Sponsor27-must
-+-
Changes (by asn):

 * parent:   => #29995
 * actualpoints:  #29995 =>


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31770 [Core Tor/Tor]: Divide connection_edge.c into separate files.

[Tor Bug Tracker & Wiki]

#31770: Divide connection_edge.c into separate files.
---+
 Reporter:  nickm  |  Owner:  nickm
 Type:  task   | Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.4.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal |   Keywords:  032-should
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor:  Sponsor31-can  |
---+
 The connection_edge.c file was already above our threshold for file size,
 and in 0.4.2.x it has gotten bigger.  Practracker is warning about it;
 let's split it up.

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

Re: [tor-bugs] #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:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, tor-channel 042-must  |  Actual Points:  .1
  029-backport? 035-backport 040-backport|
  041-backport BugSmashFund  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  needs_review => needs_revision


Comment:

 (oops. There is a practracker failure on 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] #31769 [Core Tor/Tor]: -Wextra-semi causes build failure on debian bullseye

[Tor Bug Tracker & Wiki]

#31769: -Wextra-semi causes build failure on debian bullseye
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  029-backport 035-backport|  Actual Points:  .1
  040-backport 041-backport 042-should?  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 The plot grows thicker.  On both debian and fedora, this command line
 gives a warning but returns success:
 {{{
 gcc -Wextra-semi -Werror -c example.c && echo ok
 }}}
 but this one fails:
 {{{
 gcc -Werror -Wextra-semi -c example.c && echo ok
 }}}

 Note that the only difference is the ordering of the `-Werror` and
 `-Wextra-semi` options.

 Let's look at our config.log file. On debian the command line that passes
 is:
 > gcc -c -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-
 all -Wstack-protector --param ssp-buffer-size=1 -fPIE -fasynchronous-
 unwind-tables -Wall -fno-strict-aliasing -Waddress -Warray-bounds -Wdate-
 time -Wdouble-promotion -Wduplicate-decl-specifier -Wduplicated-cond
 -Wextra -pedantic -Werror -Wextra-semi  conftest.c >&5

 And on Fedora the one that fails is:
 > gcc -c -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-
 all -Wstack-protector --param ssp-buffer-size=1 -fPIE -fasynchronous-
 unwind-tables -Wall -fno-strict-aliasing -Waddress -Warray-bounds -Wdate-
 time -Wdouble-promotion -Wduplicate-decl-specifier -Wduplicated-cond
 -Wextra -pedantic -Werror -Wextra-semi  conftest.c >&5

 Those look identical to me.

 Moreover, when I run them on a fedora desktop and on a debian bullseye
 schroot, I (correctly) get a failing exit code from both.

 At this point, I am flummoxed.

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

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

[Tor Bug Tracker & Wiki]

#31718: Update DNS records for .ooni.torproject.org domains
-+-
 Reporter:  hellais  |  Owner:  anarcat
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by anarcat):

 seems to me that just adding the CNAME will not be enough, as there are
 many other things to cleanup. the main procedure should be:

  1. remove `ooni.torproject.org` from `tor-puppet/modules/roles/misc
 /static-components.yaml`
  2. ??? make it go away from auto-services somehow?
  3. add the CNAME

 Other things to cleanup include:

 {{{
 letsencrypt-domains/domains:46:ooni.torproject.org
 tor-nagios/config/nagios-master.cfg:1330:name: mirror static sync -
 ooni
 tor-nagios/config/nagios-master.cfg:1331:check:
 "dsa_check_staticsync!ooni.torproject.org"
 tor-puppet/modules/sudo/files/sudoers:63:%ooni
 STATICMASTER=(ooni) ALL
 tor-puppet/modules/sudo/files/sudoers:95:%ooni
 STATICMASTER=(mirroradm)NOPASSWD: /usr/local/bin/static-master-
 update-component ooni.torproject.org, /usr/local/bin/static-update-
 component ooni.torproject.org
 tor-puppet/modules/roles/manifests/static_mirror_web.pp:74:  ssl::service
 { 'ooni.torproject.org': ensure => 'ifstatic', notify  => Exec['service
 apache2 reload'], key => true, }
 tor-puppet/modules/roles/manifests/static_mirror_onion.pp:37:
 'ooni.torproject.org',
 tor-puppet/onions/onionbalance-services.yaml:17: [...]
 }}}

 I'm particularly concerned about let's encrypt - wouldn't adding the cname
 break the X509 cert, as we would now point to another server?

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

Re: [tor-bugs] #31769 [Core Tor/Tor]: -Wextra-semi causes build failure on debian bullseye

[Tor Bug Tracker & Wiki]

#31769: -Wextra-semi causes build failure on debian bullseye
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  029-backport 035-backport|  Actual Points:  .1
  040-backport 041-backport 042-should?  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 This may be a debian-only issue: I have just noticed that apparently my
 fedora desktop also claims to have GCC 9.2.1, but compilation is passing.
 Apparently this happens because -Wextra-semi is detected as unsupported in
 the autoconf script:
 {{{
 configure:18768: checking whether the compiler accepts -Wextra-semi
 configure:18787: gcc -c -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2
 -fstack-protector-all -Wstack-protector --param ssp-buffer-size=1 -fPIE
 -fasynchronous-unwind-tables -Wall -fno-strict-aliasing -Waddress -Warray-
 bounds -Wdate-time -Wdouble-promotion -Wduplicate-decl-specifier
 -Wduplicated-cond -Wextra -pedantic -Werror -Wextra-semi  conftest.c >&5
 cc1: error: command line option '-Wextra-semi' is valid for C++/ObjC++ but
 not for C [-Werror]
 cc1: all warnings being treated as errors
 }}}

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

Re: [tor-bugs] #22893 [Core Tor/Tor]: prop224: Make intro point per-service and not per-descriptor

[Tor Bug Tracker & Wiki]

#22893: prop224: Make intro point per-service and not per-descriptor
-+-
 Reporter:  dgoulet  |  Owner:  teor
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Very High|  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224-extra,   |  Actual Points:  #29995
  034-triage-20180328, 034-removed-20180328  |
Parent ID:   | Points:  7
 Reviewer:   |Sponsor:
 |  Sponsor27-must
-+-
Changes (by asn):

 * actualpoints:   => #29995


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

Re: [tor-bugs] #18935 [Applications/Tor Browser]: MS bugs - Danger! Windows updates break everything on their way!

[Tor Bug Tracker & Wiki]

#18935: MS bugs - Danger! Windows updates break everything on their way!
--+--
 Reporter:  bugzilla  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:  fixed
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by tom):

 Firefox doesn't support EAF:
 https://bugzilla.mozilla.org/show_bug.cgi?id=1509748

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

Re: [tor-bugs] #25483 [Circumvention/Snowflake]: Windows reproducible build of snowflake

[Tor Bug Tracker & Wiki]

#25483: Windows reproducible build of snowflake
-+-
 Reporter:  arlolra  |  Owner:  cohosh
 Type:  project  | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  TorBrowserTeam201805, anti-  |  Actual Points:
  censorship-roadmap-august  |
Parent ID:  #19001   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-

Comment (by cypherpunks):

 Go 1.13:
 > The Windows version specified by internally-linked Windows binaries is
 now Windows 7 rather than NT 4.0.

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

 * status:  accepted => needs_review


Comment:

 CI has passed

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

Re: [tor-bugs] #31575 [Applications/Tor Browser]: Firefox is phoning home during start-up in Tor Browser based on ESR 68

[Tor Bug Tracker & Wiki]

#31575: Firefox is phoning home during start-up in Tor Browser based on ESR 68
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff68-esr, tbb-9.0-must-alpha,|  Actual Points:
  TorBrowserTeam201909R  |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by acat):

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


Comment:

 >Note that the English title of the about:tor page is About Tor. I think
 we should use that in the preferences UI rather than Tor Browser Home but
 of course other people may have different opinions. For me, Tor Browser
 Home introduces a new term without much benefit.

 Thanks! I think it makes a lot of sense, going that route for now. Patch
 for review: https://github.com/acatarineu/tor-browser/commits/31575+2.

 I also changed [https://github.com/acatarineu/tor-browser/commit/31575+2
 #diff-a400b1ceb12ef6e65579411ba4a8867aR20 this] so that the default
 `about:tor` does not appear as `Custom URL` in `about:preferences`, but as
 `About Tor` (`about:home` also redirects to `about:tor`, but that's not
 the default value for `browser.startup.homepage`).

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

Re: [tor-bugs] #25483 [Circumvention/Snowflake]: Windows reproducible build of snowflake

[Tor Bug Tracker & Wiki]

#25483: Windows reproducible build of snowflake
-+-
 Reporter:  arlolra  |  Owner:  cohosh
 Type:  project  | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Circumvention/Snowflake  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  TorBrowserTeam201805, anti-  |  Actual Points:
  censorship-roadmap-august  |
Parent ID:  #19001   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor28-must
-+-
Changes (by cohosh):

 * status:  accepted => needs_review


Comment:

 This build is now working as of
 https://trac.torproject.org/projects/tor/ticket/28942#comment:59

 I just added an extra commit on top of dcf's branch to bump the version of
 webrtc so we have the upstream fixes: https://github.com/cohosh/tor-
 browser-build/compare/pion2

 I haven't gotten it built on android yet due to #31293 but here are the
 sha256 sums for the rest of it:
 {{{
 f3fadbac79c94e22eacb5902582bec5dbd303862768fc07c8d4f1bba469a8c5c  tor-
 browser-9.0a4-windows-x86_64-264573/mar-tools-win64.zip
 ed2a538d8e4b1aecc555e6b1683a93f4096184015549ed9992526b43759f0c9c  tor-
 browser-9.0a4-windows-x86_64-264573/torbrowser-install-win64-9.0a4_en-
 US.exe

 7d5a8353bde39d0bafb40d9c03eb4f2b28cddd8306bf429e811f1caa9435189c  tor-
 browser-9.0a4-windows-i686-a3fd1d/mar-tools-win32.zip
 27bee134cf8f4c700729c6d4662bee2c23db3ddf27164e878592091e9c5d6fc8  tor-
 browser-9.0a4-windows-i686-a3fd1d/torbrowser-install-9.0a4_en-US.exe

 659e4e31ac2875ff24f667040f13a93caaddf2be73a742229bc64c6552af55dd  tor-
 browser-9.0a4-osx-x86_64-e53cb5/mar-tools-mac64.zip
 aaf162ecc77e214c04ce78c4eb68ed2f7d239efbc6ad61daeb8af9f9e8d41018  tor-
 browser-9.0a4-osx-x86_64-e53cb5/TorBrowser-9.0a4-osx64_en-US.dmg

 a95656c0a1d220f51ebb7c02264ca14a6dfcaf1f49f9c1eb2b100b8912202fbb  tor-
 browser-9.0a4-linux-x86_64-377cf5/mar-tools-linux64.zip
 313467567d9f85b11f9fc075f2a450d0fa5daa575a17635a0852fbdecbe7163f  tor-
 browser-9.0a4-linux-x86_64-377cf5/tor-browser-linux64-9.0a4_en-US.tar.xz
 f2e28bd473b7fc21dc3a4ce0b1c4931de1cc2bbba643cb790a94cd23b5f8a44f  tor-
 browser-9.0a4-linux-x86_64-377cf5/tor-browser-linux64-debug.tar.xz
 05be2469134ab700ff06a464eaef4c5ae95252810158c6490ab1830d65c1e5df  tor-
 browser-9.0a4-linux-x86_64-377cf5/tor-linux64-debug.tar.xz

 3c44f8039334230540ca09eeea7b478eb6d2b94186b4f15f65b39d5b5afa8654  tor-
 browser-9.0a4-linux-i686-4e5c2e/mar-tools-linux32.zip
 b154ec37b41f515a4618a4f2602c5fca082e7cbeb8c14ef6cc85788c156cd200  tor-
 browser-9.0a4-linux-i686-4e5c2e/tor-browser-linux32-9.0a4_en-US.tar.xz
 08d05d0573f41f55d95bcca4c61374491469ddde220ddd51d9f32e754c395a16  tor-
 browser-9.0a4-linux-i686-4e5c2e/tor-browser-linux32-debug.tar.xz
 0261e8109dc380f197a24e3e4799182916a060065a97bf66926f7e3f01a0523b  tor-
 browser-9.0a4-linux-i686-4e5c2e/tor-linux32-debug.tar.xz
 }}}

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

Re: [tor-bugs] #31769 [Core Tor/Tor]: -Wextra-semi causes build failure on debian bullseye

[Tor Bug Tracker & Wiki]

#31769: -Wextra-semi causes build failure on debian bullseye
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  029-backport 035-backport|  Actual Points:  .1
  040-backport 041-backport 042-should?  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  assigned => needs_review


Comment:

 See branch `bug31769_029`; https://github.com/torproject/tor/pull/1335 is
 a PR that merges it to master.

 I don't think we should merge this unless it becomes apparent that GCC
 will not fix their bug.

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

Re: [tor-bugs] #31769 [Core Tor/Tor]: -Wextra-semi causes build failure on debian bullseye

[Tor Bug Tracker & Wiki]

#31769: -Wextra-semi causes build failure on debian bullseye
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  029-backport 035-backport|  Actual Points:  .1
  040-backport 041-backport 042-should?  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  029-backport 035-backport 040-backport 041-backport =>
 029-backport 035-backport 040-backport 041-backport 042-should?
 * actualpoints:   => .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] #31769 [Core Tor/Tor]: -Wextra-semi causes build failure on debian bullseye

[Tor Bug Tracker & Wiki]

#31769: -Wextra-semi causes build failure on debian bullseye
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  029-backport 035-backport|  Actual Points:
  040-backport 041-backport  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 Debian bullseye apparently has GCC 9.2.1:
 https://packages.debian.org/testing/gcc

 But 9.2.1 is not apparently released yet: https://gcc.gnu.org/ml/gcc-
 announce/2019/

 I think we should prepare a fix, but I think this is not a release
 blocker.

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

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

[Tor Bug Tracker & Wiki]

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

 * status:  accepted => needs_review


Comment:

 I'll put this into needs_review now. Here's a commit that bumps the
 version of webrtc and removes the need for the patch:
 https://github.com/cohosh/tor-browser-
 build/commit/873685ba2a4756176bf2a680563f09d297cd3a50

 And the rebased pion branch of snowflake:
 https://github.com/cohosh/snowflake/compare/pion

 While being able to
 
[https://github.com/cohosh/snowflake/commit/ef59d09f7cef7970e34efa18da0612e38f8f5002
 being able to use the pion logs] would be nice, we need Go 1.13 to do it
 nicely, and we haven't yet bumped the version for Tor Browser builds. I
 would like to cherry-pick
 
[https://github.com/cohosh/snowflake/commit/f370a4f296de432c392c6fc2f204fd3877a60429
 adding locks to safelog] though.

 Note also that starting with
 [https://github.com/pion/webrtc/releases/tag/v2.1.4 v2.1.4], pion/webrtc
 is moving to Go 1.13. I'm not sure yet if it can still be built with Go
 1.12.

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

Re: [tor-bugs] #31769 [Core Tor/Tor]: -Wextra-semi causes build failure on debian bullseye

[Tor Bug Tracker & Wiki]

#31769: -Wextra-semi causes build failure on debian bullseye
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  029-backport 035-backport|  Actual Points:
  040-backport 041-backport  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 Except that the flag apparently does something different on clang:
 80f1a2cbbdd0abd509711a5069f31855df5bcd79 .

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31769 [Core Tor/Tor]: -Wextra-semi causes build failure on debian bullseye

[Tor Bug Tracker & Wiki]

#31769: -Wextra-semi causes build failure on debian bullseye
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:  Tor: 0.4.2.x-final
Component:  Core |Version:
  Tor/Tor|   Keywords:  029-backport 035-backport
 Severity:  Normal   |  040-backport 041-backport
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 From jenkins: https://jenkins.torproject.org/job/tor-ci-linux-
 master/ARCHITECTURE=amd64,SUITE=bullseye/4153/consoleFull

 {{{
 09:00:39 cc1: warning: command line option '-Wextra-semi' is valid for
 C++/ObjC++ but not for C
 }}}

 The logical solution here is to remove the flag.

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

Re: [tor-bugs] #31286 [Applications/Tor Browser]: Include bridge configuration into about:preferences

[Tor Bug Tracker & Wiki]

#31286: Include bridge configuration into about:preferences
-+-
 Reporter:  gk   |  Owner:
 |  pospeselr
 Type:  task | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-9.0-must-alpha,  |  Actual Points:
  TorBrowserTeam201909, ff68-esr |
Parent ID:  #10760   | Points:  15
 Reviewer:   |Sponsor:
 |  Sponsor44-can
-+-

Comment (by antonela):

 > We need an onboarding card for explaining this change. Do we want to do
 it during this release? If yes, I'll file that child ticket.

 Done > https://trac.torproject.org/projects/tor/ticket/31768

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31768 [Applications/Tor Browser]: Introduce Tor network settings in TB9 onboarding

[Tor Bug Tracker & Wiki]

#31768: Introduce Tor network settings in TB9 onboarding
--+--
 Reporter:  antonela  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  ux-team
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 We need to explain users that Tor Network Settings were moved from the Tor
 button to `about:preferences#tor`

 New UI relevant ticket
 https://trac.torproject.org/projects/tor/ticket/31286

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

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

[Tor Bug Tracker & Wiki]

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

Comment (by karsten):

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

 Hmm, I changed something on colchicifolium's side to accept the rsync, but
 it doesn't seem to work. Is there anything in the log on your side?

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

Re: [tor-bugs] #30029 [Applications/Tor Browser]: Objective 2, Activity 5: POC for Human-memorable addresses for .onion services

[Tor Bug Tracker & Wiki]

#30029: Objective 2, Activity 5: POC for Human-memorable addresses for .onion
services
---+---
 Reporter:  pili   |  Owner:  tbb-team
 Type:  project| Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  network-team-roadmap-november  |  Actual Points:
Parent ID:  #30281 | Points:  50
 Reviewer: |Sponsor:
   |  Sponsor27-must
---+---
Changes (by pili):

 * points:   => 50


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

Re: [tor-bugs] #30090 [UX]: Make a list of potential .onion errors

[Tor Bug Tracker & Wiki]

#30090: Make a list of potential .onion errors
+
 Reporter:  pili|  Owner:  antonela
 Type:  task| Status:  new
 Priority:  Medium  |  Milestone:
Component:  UX  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  #19251  | Points:
 Reviewer:  |Sponsor:  Sponsor27-must
+
Changes (by pili):

 * parent:  #30025 => #19251


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

Re: [tor-bugs] #30025 [Applications/Tor Browser]: Objective 2, Activity 4: Better client-side errors

[Tor Bug Tracker & Wiki]

#30025: Objective 2, Activity 4: Better client-side errors
--+
 Reporter:  pili  |  Owner:  tbb-team
 Type:  project   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #30281| Points:  21
 Reviewer:|Sponsor:  Sponsor27-must
--+
Changes (by pili):

 * points:   => 21


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

Re: [tor-bugs] #30024 [Applications/Tor Browser]: Objective 2, Activity 3: Notify users if a current website they are visiting on Tor Browser has an onion service version

[Tor Bug Tracker & Wiki]

#30024: Objective 2, Activity 3: Notify users if a current website they are
visiting on Tor Browser has an onion service version
--+
 Reporter:  pili  |  Owner:  tbb-team
 Type:  project   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #30281| Points:  21
 Reviewer:|Sponsor:  Sponsor27-must
--+
Changes (by pili):

 * points:   => 21


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

Re: [tor-bugs] #30022 [Applications/Tor Browser]: Objective 2, Activity 2: Notify users about typo errors when entering .onion addresses

[Tor Bug Tracker & Wiki]

#30022: Objective 2, Activity 2: Notify users about typo errors when entering
.onion addresses
--+
 Reporter:  pili  |  Owner:  tbb-team
 Type:  project   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #30281| Points:  5
 Reviewer:|Sponsor:  Sponsor27-must
--+
Changes (by pili):

 * points:   => 5


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

Re: [tor-bugs] #24129 [Webpages/Website]: support.torproject.org work

[Tor Bug Tracker & Wiki]

#24129: support.torproject.org work
--+--
 Reporter:  isabela   |  Owner:  isabela
 Type:  task  | Status:  closed
 Priority:  Medium|  Milestone:  website redesign
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  implemented
 Keywords:  ux-team,  |  Actual Points:
Parent ID:  #21222| Points:
 Reviewer:|Sponsor:
--+--
Changes (by antonela):

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


Comment:

 https://support.torproject.org/ is live.

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

Re: [tor-bugs] #27562 [Webpages/Support]: Detect the locale and automatically serve the language specific support portal

[Tor Bug Tracker & Wiki]

#27562: Detect the locale and automatically serve the language specific support
portal
--+--
 Reporter:  sukhbir   |  Owner:  hiro
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Support  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by antonela):

 * parent:  #24129 =>


Comment:

 We want to close #24129. We are keeping this ticket open to make sure that
 this is happening.

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

Re: [tor-bugs] #29963 [Webpages/Support]: Allow browser Find (Ctrl+F) on support.torproject.org

[Tor Bug Tracker & Wiki]

#29963: Allow browser Find (Ctrl+F) on support.torproject.org
--+
 Reporter:  cypherpunks   |  Owner:  hiro
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Webpages/Support  |Version:
 Severity:  Normal| Resolution:  worksforme
 Keywords:|  Actual Points:
Parent ID:  #24129| Points:
 Reviewer:|Sponsor:
--+
Changes (by antonela):

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


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

Re: [tor-bugs] #31107 [Core Tor/Tor]: channel: channel_tls_handle_cell() CELL_VERSIONS code reached

[Tor Bug Tracker & Wiki]

#31107: channel: channel_tls_handle_cell() CELL_VERSIONS code reached
-+-
 Reporter:  dgoulet  |  Owner:  nickm
 Type:  defect   | Status:
 |  accepted
 Priority:  High |  Milestone:  Tor:
 |  0.4.2.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, tor-channel 042-must  |  Actual Points:  .1
  029-backport? 035-backport 040-backport|
  041-backport BugSmashFund  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 The right solution here is to make this `tor_fragile_assert()` into a
 protocol warning, since it happens when somebody else is violating the
 protocol.  It is not a security issue or a crash after all. (Hooray!)

 0.2.9 fix: bug31107_029. PR at https://github.com/torproject/tor/pull/1330

 The merge forward is clean; these branches are for CI.

 0.3.5 fix: bug31107_035. PR at https://github.com/torproject/tor/pull/1331
 0.4.0 fix: bug31107_040. PR at https://github.com/torproject/tor/pull/1332
 0.4.1 fix: bug31107_041. PR at https://github.com/torproject/tor/pull/1333
 0.4.2 fix: bug31107_master. PR at
 https://github.com/torproject/tor/pull/1334

 I'll put this in needs_review once CI is passing.

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

Re: [tor-bugs] #30429 [Applications/Tor Browser]: Rebase Tor Browser patches for Firefox ESR 68

[Tor Bug Tracker & Wiki]

#30429: Rebase Tor Browser patches for Firefox ESR 68
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_revision
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff68-esr, tbb-9.0-must-alpha,|  Actual Points:
  TorBrowserTeam201909   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor44-can
-+-

Comment (by gk):

 I took a look at commit 14df73ecfdd88db89f196cecfb934dab7e552969 (aka the
 rebased patch for #4234):

 Do we really want to disable staged updates for macOS? I feel if we don't
 have good reasons like we do for Windows and Linux we should a) not
 degrade the user experience here and b) not deviate from the update code
 path Mozilla is using (assuming that the alternative path is less tested).

 We need an updated logo for `aboutdebugging-firefox-release.svg` at least,
 right? Do we have a bug for that on file? (one can see the issue after
 flipping `devtools.aboutdebugging.new-enabled` and then opening
 `about:debugging`)

 Why do we suddenly need the `#ifdef XP_WIN` blocks around `closeHandle()`
 and friends? Just to make it abundantly clear that this is only used for
 Windows as is the ctypes inclusion? I wonder if we could that somehow
 upstream or make it clear upstream in a way  that we don't have to carry
 that part of the patch around every time.

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

Re: [tor-bugs] #31107 [Core Tor/Tor]: channel: channel_tls_handle_cell() CELL_VERSIONS code reached

[Tor Bug Tracker & Wiki]

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

 * actualpoints:   => .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] #31575 [Applications/Tor Browser]: Firefox is phoning home during start-up in Tor Browser based on ESR 68

[Tor Bug Tracker & Wiki]

#31575: Firefox is phoning home during start-up in Tor Browser based on ESR 68
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff68-esr, tbb-9.0-must-alpha,|  Actual Points:
  TorBrowserTeam201909   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by mcs):

 * cc: antonela, pili (added)


Comment:

 Replying to [comment:8 acat]:
 > Sorry, it still remains to change `Firefox Home` string to `Tor Browser
 Home` and localize it. I was not sure whether to do that separately later,
 but I think it's worth it doing it here, so setting it as revision_needed
 and will do that change too.

 Note that the English title of the about:tor page is `About Tor`. I think
 we should use that in the preferences UI rather than `Tor Browser Home`
 but of course other people may have different opinions. For me, `Tor
 Browser Home` introduces a new term without much benefit.

 Cc: Antonela and Pili in case they have smart things to say ;)

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

Re: [tor-bugs] #31107 [Core Tor/Tor]: channel: channel_tls_handle_cell() CELL_VERSIONS code reached

[Tor Bug Tracker & Wiki]

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

Comment (by nickm):

 Okay, here is a better diagnosis.

 The problem is that cell_command_is_var_length() looks at the link
 protocol version when deciding whether a cell is variable-length.  That's
 cool, but it does mean that CELL_VERSIONS is not necessarily a variable-
 length cell.  So if somebody sends a VERSIONS cell on a v1 connection,
 we'll hit this warning.

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

Re: [tor-bugs] #31107 [Core Tor/Tor]: channel: channel_tls_handle_cell() CELL_VERSIONS code reached

[Tor Bug Tracker & Wiki]

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

Comment (by nickm):

 Ohhh, wait.  It doesn't actually work that way.  I need to reconsider.

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

Re: [tor-bugs] #31575 [Applications/Tor Browser]: Firefox is phoning home during start-up in Tor Browser based on ESR 68

[Tor Bug Tracker & Wiki]

#31575: Firefox is phoning home during start-up in Tor Browser based on ESR 68
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff68-esr, tbb-9.0-must-alpha,|  Actual Points:
  TorBrowserTeam201909   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by acat):

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


Comment:

 Sorry, it still remains to change `Firefox Home` string to `Tor Browser
 Home` and localize it. I was not sure whether to do that separately later,
 but I think it's worth it doing it here, so setting it as revision_needed
 and will do that change too.

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

Re: [tor-bugs] #31107 [Core Tor/Tor]: channel: channel_tls_handle_cell() CELL_VERSIONS code reached

[Tor Bug Tracker & Wiki]

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

 * keywords:  tor-relay, tor-channel security 042-must =>
 tor-relay, tor-channel 042-must 029-backport? 035-backport
 040-backport 041-backport BugSmashFund
 * priority:  Very High => High


Comment:

 Okay, this is a bug, and an old one.  It looks like our logic in
 connection_or_process_cells_from_inbuf() is wrong in the way that it
 handles variable-length cells.

 Basically, what it is doing right now it this:
 {{{
 try to fetch var_cell_t from buffer.
 if (we got a var_cell_t) {
give it to the channel layer.
return
 }
 see whether we have more than 512/514 bytes on the buffer
 if (we do) {
package it as a cell_t
give it to the channel layer
return;
 }
 wait for more data
 }}}

 See the problem?  If we have a pending incomplete variable-length cell of
 more than 512/514 bytes, it will get mis-packaged as a regular fixed-
 length cell.

 What fun!

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

Re: [tor-bugs] #31107 [Core Tor/Tor]: channel: channel_tls_handle_cell() CELL_VERSIONS code reached

[Tor Bug Tracker & Wiki]

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

 * keywords:  tor-relay, tor-channel security crash 042-must => tor-relay,
 tor-channel security 042-must


Comment:

 Okay.  Fortunately, this isn't a crash: tor_fragile_assert() just logs a
 stack trace like this.

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

Re: [tor-bugs] #31575 [Applications/Tor Browser]: Firefox is phoning home during start-up in Tor Browser based on ESR 68

[Tor Bug Tracker & Wiki]

#31575: Firefox is phoning home during start-up in Tor Browser based on ESR 68
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff68-esr, tbb-9.0-must-alpha,|  Actual Points:
  TorBrowserTeam201909R  |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by acat):

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


Comment:

 Patch for review in https://github.com/acatarineu/tor-
 browser/commits/31575+1 (two commits).

 Now choosing "Firefox Home" for newtab or home in `about:preferences` will
 load `about:tor` instead of Firefox newtab. For newtab the default will be
 `about:blank`.

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

Re: [tor-bugs] #31518 [Core Tor/Tor]: HAProxy implementation in TCPProxy option.

[Tor Bug Tracker & Wiki]

#31518: HAProxy implementation in TCPProxy option.
--+
 Reporter:  haxxpop   |  Owner:  haxxpop
 Type:  enhancement   | Status:  needs_revision
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  proxy tcp |  Actual Points:
Parent ID:| Points:
 Reviewer:  nickm |Sponsor:
--+
Changes (by nickm):

 * status:  needs_review => needs_revision


Comment:

 Okay, this is looking better and better!  I think it will be ready for
 inclusion in 0.4.3.x.

 I added a suggestion to rename the "WANT_ACK" state.

 The other request I have is to see if you can write tests for more
 functions.  Right now, only around 1/4 of the new lines in your patch have
 test coverage.  Coveralls didn't add its report to the ticket for some
 reason, but you can see the coverage report at
 https://coveralls.io/builds/25644803

 If there's something you can't test, or think a test isn't necessary for,
 please let me know and we can talk about it.

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

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

[Tor Bug Tracker & Wiki]

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

 * keywords:
 warning compiler 042-should 041-backport 040-backport 035-backport
 BugSmashFund
 =>
 consider-backport-immediately warning compiler 042-should 041-backport
 040-backport 035-backport BugSmashFund


Comment:

 This is a compiler warning fix, which should be fine to backport after it
 passes CI.

 Here are the PRs:
 * 0.3.5: https://github.com/torproject/tor/pull/1314
 * 0.4.0: https://github.com/torproject/tor/pull/1323

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

Re: [tor-bugs] #28745 [Applications/Tor Browser]: THE Torbutton clean-up

[Tor Bug Tracker & Wiki]

#28745: THE Torbutton clean-up
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-torbutton,   |  Actual Points:
  TorBrowserTeam201909R  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 #19256

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

Re: [tor-bugs] #31709 [Webpages/Website]: Add the Digital Climate Strike code to the Tor Website

[Tor Bug Tracker & Wiki]

#31709: Add the Digital Climate Strike code to the Tor Website
--+
 Reporter:  teor  |  Owner:  hiro
 Type:  task  | Status:  needs_revision
 Priority:  High  |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #31708| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * Attachment "Tor_Browser_macOS.png" added.

 Tor Browser macOS Tor Climate Strike Banner and Scroll Bar

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

Re: [tor-bugs] #31709 [Webpages/Website]: Add the Digital Climate Strike code to the Tor Website

[Tor Bug Tracker & Wiki]

#31709: Add the Digital Climate Strike code to the Tor Website
--+
 Reporter:  teor  |  Owner:  hiro
 Type:  task  | Status:  needs_revision
 Priority:  High  |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #31708| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * Attachment "Safari_macOS.png" added.

 Safari macOS Tor Climate Strike Banner

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

Re: [tor-bugs] #31709 [Webpages/Website]: Add the Digital Climate Strike code to the Tor Website

[Tor Bug Tracker & Wiki]

#31709: Add the Digital Climate Strike code to the Tor Website
--+
 Reporter:  teor  |  Owner:  hiro
 Type:  task  | Status:  needs_revision
 Priority:  High  |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #31708| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * Attachment "Chrome_macOS.png" added.

 Chrome macOS Tor Climate Strike Banner

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

Re: [tor-bugs] #31709 [Webpages/Website]: Add the Digital Climate Strike code to the Tor Website

[Tor Bug Tracker & Wiki]

#31709: Add the Digital Climate Strike code to the Tor Website
--+
 Reporter:  teor  |  Owner:  hiro
 Type:  task  | Status:  needs_revision
 Priority:  High  |  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #31708| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * status:  new => needs_revision


Comment:

 Replying to [comment:2 pili]:
 > This is currently available on staging: https://lektor-
 staging.torproject.org/tpo/develop/
 >
 > Can we get a review that it works as expected before promoting to
 production?

 The banner appears with and without JavaScript, on:
 * MobileSafari on iPad
 * Tor Browser on macOS
 * Google Chrome on macOS
 * Safari on macOS

 There are 3 interactive UI elements:
 * the global climate strike image link works on all platforms
 * the "Yes, I'm In" button works on all platforms, but looks bad on:
   * Google Chrome on macOS
   * Safari on macOS
   * (I'll attach some screenshots)
 * the close button "x" works on all platforms, except:
   * Tor Browser on macOS, where it is obscured by the scroll bar
 * solution: move the close button another 1-1.5x of its width to the
 left

 These issues are not blockers, but we should fix them.

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

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

[Tor Bug Tracker & Wiki]

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

 * milestone:  Tor: 0.4.2.x-final => Tor: 0.4.1.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] #31687 [Core Tor/Tor]: FreeBSD compilation warns with Tor 0.4.1.5

[Tor Bug Tracker & Wiki]

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

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


Comment:

 Merged. Leaving ticket open for bakcport.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31767 [Applications/Tor Browser]: Avoid using intl.locale.requested pref directly

[Tor Bug Tracker & Wiki]

#31767: Avoid using intl.locale.requested pref directly
--+--
 Reporter:  acat  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  ff68-esr
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 We wrongly assume that `intl.locale.requested` contains just a single
 locale, but it's actually a list of locales if more than one language pack
 is installed (which we are allowing for now).

 We should probably use JS API `Services.locale.requestedLocale` and the
 appropriate C++ API (need to check) instead of using
 `intl.locale.requested` value. This affects "torbutton" code and patch for
 #14631.

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

Re: [tor-bugs] #31766 [Core Tor]: INTERNAL_ERROR in map_anon.c

[Tor Bug Tracker & Wiki]

#31766: INTERNAL_ERROR in map_anon.c
-+--
 Reporter:  tmpname0901  |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:
Component:  Core Tor |Version:  Tor: 0.4.1.5
 Severity:  Major| Resolution:  duplicate
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by tmpname0901):

 * Attachment "Tor-0.4.1.5-build-log.txt.gz" added.

 How the faulting Tor was built.

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

Re: [tor-bugs] #31766 [Core Tor]: INTERNAL_ERROR in map_anon.c

[Tor Bug Tracker & Wiki]

#31766: INTERNAL_ERROR in map_anon.c
-+--
 Reporter:  tmpname0901  |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:
Component:  Core Tor |Version:  Tor: 0.4.1.5
 Severity:  Major| Resolution:  duplicate
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by tmpname0901):

 * Attachment "tor-0.4.1.5-fault-output.txt" added.

 Output of INTERNAL_ERROR on start-up

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

Re: [tor-bugs] #31584 [Applications/Tor Browser]: Clean up mingw-w64 project

[Tor Bug Tracker & Wiki]

#31584: Clean up mingw-w64 project
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-rbm, ff68-esr, tbb-9.0-must- |  Actual Points:
  alpha, TorBrowserTeam201909R,  |
  GeorgKoppen201909  |
Parent ID:  #30322   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 o_0 isn't it for switching to clang? If you also want gcc, do it for
 nightlies only, please.

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

Re: [tor-bugs] #31766 [Core Tor]: INTERNAL_ERROR in map_anon.c

[Tor Bug Tracker & Wiki]

#31766: INTERNAL_ERROR in map_anon.c
-+--
 Reporter:  tmpname0901  |  Owner:  (none)
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:
Component:  Core Tor |Version:  Tor: 0.4.1.5
 Severity:  Major| Resolution:  duplicate
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by nickm):

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


Comment:

 Thanks for the bug report!  This looks like a duplicate of #31570.

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