Replies: 3 comments
-
|
Thanks @osevan, I'll definitely integrate it into firejail. It is a more elegant solution than what we have now. By May 2026 kernel 6.19 will be at least in Arch and Ubuntu. Currently we have: |
Beta Was this translation helpful? Give feedback.
-
|
Not to forget: this should be as additional layer of defense . Like landlock and apparmor lsm it should work as additional layer of defense . Thanks and Best regards |
Beta Was this translation helpful? Give feedback.
-
|
By default we try not to replace it, and just layer it on top of what we have. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
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
Beta Was this translation helpful? Give feedback.
All reactions