mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2343] Dropping 'mincore' syscall breaks several apps #1564
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#1564
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 @Vincent43 on GitHub (Jan 16, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2343
Originally assigned to: @netblue30 on GitHub.
Recent commit that added
mincoreto defaultseccompblacklist causeskodifail to start. Perhaps we have to move toseccomp.dropfilter in kodi profile and omitmincoresyscall.SECCOMP subj==firejail-default (enforce) pid=4792 comm="kodi.bin" exe="/usr/lib/kodi/kodi.bin" sig=31 arch=c000003e syscall=27 compat=0 ip=0x6bf06868d89b code=0x0@Vincent43 commented on GitHub (Jan 21, 2019):
Fixed by
05bbec3375@Vincent43 commented on GitHub (Jan 22, 2019):
Bad news,
mpvhave the same issue:SECCOMP ses=1 subj==firejail-default (enforce) pid=23615 comm="mpv/vo" exe="/usr/bin/mpv" sig=31 arch=c000003e syscall=27 compat=0 ip=0x6db290aea89b code=0x0I wonder if
mincoreisn't too widely used to be in default filter.@SkewedZeppelin commented on GitHub (Jan 22, 2019):
totem seems broken too
@SkewedZeppelin commented on GitHub (Jan 22, 2019):
We should probably revert it before release to not cause too many issues.
The kernel patch to reduce leakage from the mincore syscall was already backported to all supported kernels anyway.take that back, it wasn't, only in 4.20 for now?@Vincent43 commented on GitHub (Jan 22, 2019):
I think it's only in 5.0 for now. Perhaps isn't considered much urgent.
@netblue30 commented on GitHub (Jan 23, 2019):
I have removed it, thanks!
@Vincent43 commented on GitHub (Jan 24, 2019):
@SkewedZeppelin actually the kernel commit was reverted.