Skip to content
Snippets Groups Projects

Backport security fixes from ESR 102.4 to ESR 91.13-based Tor Browser

Merged morgan requested to merge morgan/tor-browser:bug_41359 into tor-browser-91.13.0esr-11.5-1

Resolves #41359 (closed)

Backported all of the patches for the CVEs listed in the issue.

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • assigned to @richard

  • 🤖 Triage Bot 🤖 requested review from @boklm

    requested review from @boklm

  • This looks good to me.

    I created a new branch and cherry-picked the patches, and got the same result as this MR. The only conflict was with 6d5378a6.

    However I saw the patch for https://bugzilla.mozilla.org/show_bug.cgi?id=1791598 in the master branch of gecko-dev, but I don't see it in the esr102 branch. Any idea why Mozilla apparently did not backport this patch?

  • Author Owner

    From what I can read from the issue, it seems like they think the issue cannot be hit due to how Firefox uses it, and mitigations from RLBox sandboxing in general mean it's low risk and didn't need ot be backported.

    But it's an easy fix and it applies so why not?

  • morgan changed title from Backport security fixes from ESR 102.4 to ERR 91.13-based Tor Browser to Backport security fixes from ESR 102.4 to ESR 91.13-based Tor Browser

    changed title from Backport security fixes from ESR 102.4 to ERR 91.13-based Tor Browser to Backport security fixes from ESR 102.4 to ESR 91.13-based Tor Browser

  • Author Owner

    From what I can read from the issue, it seems like they think the issue cannot be hit due to how Firefox uses it, and mitigations from RLBox sandboxing in general.

Please register or sign in to reply
Loading