mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #241] Start application with *firejail --seccomp* or not? #169
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#169
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 @Goderw on GitHub (Jan 20, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/241
Hello,
it isn`t an issue at all, but in the Arch-Linux-Wiki they say that firejail has to start with "firejail --seccomp firefox" for example. In your "wiki" I can read --seccomp isn't neccessary because there is a filter list for firefox anyway.
Well, which setting gives the most protection to start Firefox in this case -> With --seccomp or w/o?
Thanks for this great invention!!
@Goderw commented on GitHub (Jan 20, 2016):
Additionally:
I have testet both... and in both cases "grep Seccomp /proc//status" shows that seccomp 2 is enabled. So I think I can run "firejail firefox" w/o --seccomp in line!
@netblue30 commented on GitHub (Jan 20, 2016):
It is not necessary anymore. I've made it default.