Hello. Since Linux 5.1 was released, I refreshed the tarballs. There is no change except supporting the latest kernels. ccs-patch-1.8.5-20190506.tar.gz MD5:aaaaadd5a737105ff3a47acec5881ba6 caitsith-patch-0.2-20190506.tar.gz MD5:88882d87bd2d2bc12ec1fc687db317ea In Linux 5.1, TOMOYO 2.x became TOMOYO 2.6 ( https://tomoyo.osdn.jp/2.6/ ). In Linux 5.2, TOMOYO 2.6 will get the following changes. (1) To solve a problem that it is inconvenient for policy development that filesystems which do not support rename operation (e.g. squashfs) do not generate absolute pathnames ( http://lists.osdn.me/mailman/archives/tomoyo-users-en/2017-July/000685.html ), the pathname calculation logic is modified to generate absolute pathnames on filesystems which do not support rename operation but require a block device upon mount operation. Since majority of users are using filesystems which support rename operation, this change would bother nobody. Also, I'm thinking to backport to TOMOYO 1.8 / AKARI / CaitSith after confirming that this change has no problem with TOMOYO 2.6. (2) To be able to cover more code by fuzzing tests by syzbot, a kernel config option CONFIG_SECURITY_TOMOYO_INSECURE_BUILTIN_SETTING which should be enabled only when building kernels for fuzzing tests is added. Please be careful not to enable by error when building normal kernels. Please let me know if you found any problems.
TOMOYO
Fork