mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #5639] qutebrowser: cannot run userscripts #3052
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#3052
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kjk11 on GitHub (Feb 5, 2023).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5639
As described here , one of the recent changes to the Qutebrowser profile, most likely this pull request https://github.com/netblue30/firejail/pull/5389, breaks the invocation of qutebrowser userscripts. I have been able to circumvent this problem by setting
in qutebrowser.local . I believe userscripts should work by default. Perhaps there is a more fine-grained way of getting the functionality back?
@ghost commented on GitHub (Feb 6, 2023):
Thank you for reporting this. I agree.
There are several profiles that have
ignore noexec ${HOME}. In general that loosens the sandbox obviously, but it still is dependend on what you have installed under ${HOME} that potentially could pose a threat. Not really a fine-grained tool though theignore noexecoption, but we'll need to add it to the profile regardless.You could try to compensate for this
lossvia additional AppArmor rules, only allowing the owner of files under ${HOME}/.config/qutebrowser/userscripts to execute those and nothing else. Check your/etc/apparmor.d/local/firejail-default, there are interesting comments inside that can help achieve this.OTOH, something like the below should limit what's allowed to be executed:
Just remember to clear AA's rules cache (if you use that option) after editing the file and usually a reboot is also required for AA to enforce the changes. If you need help with that, feel free to ask.
@ghost commented on GitHub (Feb 15, 2023):
@kjk11 Usual deal. Merging the PR auto-closes this. Feel free to reopen.