[GH-ISSUE #3417] seccomp.block-secondary #2148

Closed
opened 2026-05-05 08:49:19 -06:00 by gitea-mirror · 4 comments
Owner

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).

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).
Author
Owner

@ghost commented on GitHub (May 15, 2020):

I have been running with seccomp.block-secondary in 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.

<!-- gh-comment-id:629216996 --> @ghost commented on GitHub (May 15, 2020): I have been running with `seccomp.block-secondary` in 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](https://github.com/loki-project/session-desktop/releases/download/v1.0.8/session-messenger-desktop-linux-x86_64-1.0.8.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.
Author
Owner

@rusty-snake commented on GitHub (May 15, 2020):

I have been running with seccomp.block-secondary in globals.local

I too

The only other exception I encountered is when firejailing an appimage

Just this one? or also other appimages?

<!-- gh-comment-id:629221054 --> @rusty-snake commented on GitHub (May 15, 2020): > I have been running with seccomp.block-secondary in globals.local I too > The only other exception I encountered is when firejailing an appimage Just this one? or also other appimages?
Author
Owner

@ghost commented on GitHub (May 15, 2020):

Just this one? or also other appimages?

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.

<!-- gh-comment-id:629232646 --> @ghost commented on GitHub (May 15, 2020): > Just this one? or also other appimages? 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](https://github.com/AppImage/AppImageKit) I suppose.
Author
Owner

@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.

<!-- gh-comment-id:684921438 --> @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.
Sign in to join this conversation.
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#2148
No description provided.