mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3423] seccomp is breaking wire-desktop #2149
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#2149
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 @CodeArtisan00 on GitHub (May 19, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3423
specs- Manjaro (KDE), Kernel: 5.6.x, Firejail ver: 0.9.62 wire: 3.17.2924
output of firejail --debug : https://gist.github.com/Neo00001/a77cc18994863c41327e7e0fa45e3554
@ghost commented on GitHub (May 19, 2020):
Hi, looking at your debug log doesn't indicate conclusively this is a seccomp issue. It might be #2946 (which is fixed in git). There's an easy way to determine seccomp issues in firejail though, so if you can run the below after starting wire-desktop that would be helpful.
$ sudo journalctl | grep syscallIf you get output like ... syscall=123 ... you can determine which syscall is used although it was forbidden by the profile:
$ firejail --debug-syscalls | grep 123If you don't get any output and you want to check if it's #2946, add the below in your wire-desktop.local:
BTW, can you post what's in your wire-desktop.local currently?
@CodeArtisan00 commented on GitHub (May 19, 2020):
output of firejail --debug-syscalls shows personality
it doesn't launch wire.
seccomp !chrootfixes the problem. usingseccomp !chrootonly fixes it.ignore netwhitelist ~/Downloads/Wire/@ghost commented on GitHub (May 19, 2020):
I forgot that the '!' syntax is actually supported in 0.9.62. As for your wire-desktop.local, I just wanted to make sure there wasn't anything there that might be interfering. The system-wide wire-desktop.profile already whitelists ${HOME}/Downloads, so the subdir reference shouldn't be strictly necessary. I'll fix the profile in git, so make a note that you can remove 'seccomp !chroot' from the .local on a future firejail upgrade. Thanks for reporting!
@CodeArtisan00 commented on GitHub (May 20, 2020):
I have commented out that in profile. & I use different directory for different apps.
@rusty-snake commented on GitHub (May 21, 2020):
I do the same (for firefox) you can add
nowhitelist ${HOME}/Downloadsto wire-desktop.local so you don't need to comment this after every update of firejail. Also you can addblacklist ${HOME}/Downloads/Wiretodisable-xdg.localor so to block some blacklisting profiles from accessing it (if you want).