mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3417] seccomp.block-secondary #2148
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#2148
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 @rusty-snake on GitHub (May 15, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3417
Are there any reasons why we don't use
seccomp.block-secondary? It should work for almost all profiles (except wine and steam).@ghost commented on GitHub (May 15, 2020):
I have been running with
seccomp.block-secondaryin globals.local for as long as it exists without issues. But I don't use wine nor steam. The only other exception I encountered is when firejailing an appimage (which generally I try to avoid). We would need to determine how appimages in general react to the seccomp.block-secondary option, which I for one am not particularly looking forward to.@rusty-snake commented on GitHub (May 15, 2020):
I too
Just this one? or also other appimages?
@ghost commented on GitHub (May 15, 2020):
This is the only appimage I use because I couldn't create a reasonable profile for its non-appimage counterpart. It's not something I'm happy with, in general I avoid using snap/flatpak/appimage technology. So I cannot determine if it is something specific to this application or something in general with appimages. I'll try to test a few others, but to be conclusive we might ask @ AppImageKit I suppose.
@rusty-snake commented on GitHub (Sep 1, 2020):
Tested KeePassXC and Cool-Retro-Term AI, both worked with sbs. We can go and add sbs to the most profiles.