Hello everyone! I've compiled a kernel with TOMOYO 1.8 support (TOMOYO is a mandatory access control system) by patching the kernel sources before running menuconfig (Woof-CE Kernel kit asks which configuration software to use, kernel sources can be patched at this time).
vmlinuz file: https://mega.nz/file/GbJzwQzB#tis0p1GO0 ... DUVA4_5884
SHA512: b4db99c3d9be33e9090d4bbf7225634c205da9902db6a0b44dac6f7d04421509a870f888788a1b9b6afbc41ae597a952544724796ee3fc02f85190d7e70bf437
Kernel modules SFS: https://mega.nz/file/CLRVQK5S#7FjkMbcdD ... 6ba3w74yCU
SHA512: 29d1a832bbe2d09e05f80b38ddc7c0c0661008e987a300b1c50bb246b531c971892cc60303abcf952405ea7f9109c03d90c27f4f8658b74c242f2b6dc135353f
Also, I haven't enabled the "do not modify task_struct" option, so patches may break KABI (kernel application binary interface), so modules may have to be recompiled for such a kernel
TOMOYO userspace tools:
TOMOYO web-site: https://tomoyo.osdn.jp/
I haven't created policies yet, I'm considering creating them soon. I'm also considering compiling 32-bit TOMOYO-supporting kernel and kernels with task_struct unmodified to prevent kABI breakage.
Would be nice to see mandatory access control in Puppy Linux.