mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1490] Better way to investigate syscalls #999
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#999
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 @chiraag-nataraj on GitHub (Aug 23, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1490
I set up a customized seccomp list for mutt (I know, they break pretty easily) and the new version of Mutt broke it. But when I run it, there is no relevant output in the audit logs (I used
sudo ausearch --rawsince I'm using Debian). I don't understand how that could be happening though...shouldn't any failed syscalls register in the system log?[Edit] This is even weirder. It seems mutt hasn't been updated, which means firejail's syscall list spontaneously broke with Mutt, for no apparent reason. I'm going to try with the latest commit. Yup, I have this issue with the latest commit as well.
@netblue30 commented on GitHub (Aug 23, 2017):
Seccomp whitelist got broken a few days ago, thanks for the bug!