[PR #3990] [MERGED] Follow-up fixes for torbrowser-launcher #4977

New issue

Closed

opened 2026-05-05 10:30:05 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 10:30:05 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/netblue30/firejail/pull/3990
Author: @ghost
Created: 2/15/2021
Status: ✅ Merged
Merged: 2/16/2021
Merged by: @undefined

Base: master ← Head: torbrowser

📝 Commits (7)

5789d97 Allow access to torbrowser-launcher under ${HOME}
b3fb4cb Avoid doubled include globals.local
970d679 Avoid doubled include globals.local
47e3e45 revert torbrowser-launcher rule
029a67a add note for torbrowser-launcher opt-in
307692f make apparmor opt-in
03f0dad adapt to apparmor being opt-in for torbrowser-launcher

📊 Changes

4 files changed (+10 additions, -6 deletions)

View changed files

📝 etc/apparmor/firejail-local (+3 -0)
📝 etc/profile-m-z/start-tor-browser.desktop.profile (+1 -4)
📝 etc/profile-m-z/start-tor-browser.profile (+2 -1)
📝 etc/profile-m-z/torbrowser-launcher.profile (+4 -1)

📄 Description

I retested enabling the apparmor option after legitimate questions posed by @rusty-snake and @Vincent43 in #3988 - thanks!. Apologies for the confusion, I forgot to add the AppArmor rule to allow access to the torbrowser-launcher executables installed under ${HOME}.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/netblue30/firejail/pull/3990 **Author:** [@ghost](https://github.com/ghost) **Created:** 2/15/2021 **Status:** ✅ Merged **Merged:** 2/16/2021 **Merged by:** [@undefined](undefined) **Base:** `master` ← **Head:** `torbrowser` --- ### 📝 Commits (7) - [`5789d97`](https://github.com/netblue30/firejail/commit/5789d97945e59dc6dd280bb9c0280b459a74146e) Allow access to torbrowser-launcher under ${HOME} - [`b3fb4cb`](https://github.com/netblue30/firejail/commit/b3fb4cbe5f6ecfeb739311e623010037887457d2) Avoid doubled include globals.local - [`970d679`](https://github.com/netblue30/firejail/commit/970d679d85a60792373f3b324497e91414d1b716) Avoid doubled include globals.local - [`47e3e45`](https://github.com/netblue30/firejail/commit/47e3e450bb12e77ac422c0b78c1724e7d6e657a7) revert torbrowser-launcher rule - [`029a67a`](https://github.com/netblue30/firejail/commit/029a67a08905f317df4246c118b6043788d4c81d) add note for torbrowser-launcher opt-in - [`307692f`](https://github.com/netblue30/firejail/commit/307692f1e2c0995ddfba25028924a202c988f392) make apparmor opt-in - [`03f0dad`](https://github.com/netblue30/firejail/commit/03f0dadc99b8d37795f0980366a64d1dec8ddc91) adapt to apparmor being opt-in for torbrowser-launcher ### 📊 Changes **4 files changed** (+10 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `etc/apparmor/firejail-local` (+3 -0) 📝 `etc/profile-m-z/start-tor-browser.desktop.profile` (+1 -4) 📝 `etc/profile-m-z/start-tor-browser.profile` (+2 -1) 📝 `etc/profile-m-z/torbrowser-launcher.profile` (+4 -1) </details> ### 📄 Description I retested enabling the apparmor option after legitimate questions posed by @rusty-snake and @Vincent43 in #3988 - thanks!. Apologies for the confusion, I forgot to add the AppArmor rule to allow access to the torbrowser-launcher executables installed under ${HOME}. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

gitea-mirror

2026-05-05 10:30:05 -06:00

closed this issue
added the
pull-request
label

gitea-mirror referenced this issue

2026-05-05 10:36:15 -06:00

[PR #4977] [MERGED] fix globals.local in mupdf & redirects #5317

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#4977

No description provided.

Rows
Columns