mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #6982] Kernel 6.19 merged ipe check good for every container #3444
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#3444
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 @osevan on GitHub (Dec 4, 2025).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6982
Dear devs,
I hope i can give here as always newest security features for kernel - like I did with landlock .
New feature is ipe
Every container runtime can plant
execveat( ) and AT_EXECVE_CHECK for checking if ipe policy is active or not
https://docs.kernel.org/admin-guide/LSM/ipe.html
https://www.phoronix.com/news/Linux-6.19-IPE-AT_EXECVE_CHECK
Kernel ipe activating :
sudo tee /sys/kernel/security/ipe/policy > /dev/null < /tmp/ipe-policy.conf
Simple c app example
Every elf binary or bash script or python script can go through
execveat( ) and AT_EXECVE_CHECK
And we have additional layer of defense .
Output in dmesg looks like this :
IPE: denied execution: path=/tmp/testscript.sh reason=integrity
Removing policy :
echo "" | sudo tee /sys/kernel/security/ipe/policy > /dev/null
I hope you can patch firejail with these feature or make configure option --with-ipe for testing .
3 minimum checks :
If kernel 6.19 running
If ipe policy set already
If profile file or argv got content "ipe-check" or --ipe-check when firejail started
Thanks and
Best regards