On 2017/10/22 2:17, Casey Schaufler wrote: >> As one year elapsed since I proposed CaitSith for upstream, I'd like to >> hear the status again. I looked at >> http://schd.ws/hosted_files/lss2017/8b/201709-LinuxSecuritySummit-Stacking.pdf >> . >> How is ETA for Security Module Stacking? Is it a half year or so? > > Assuming that I can keep working on stacking at my current level, > and that we can work out a couple issues with audit and networking > there is a possibility we're looking at mid 2018 for stacking. The > increased interest in security module namespaces for containers is > helping make stacking seem important to more people. > >> If it is likely take longer, should I resume proposing CaitSith for now >> as one of "Minor modules" except security_module_enable() check added >> until Security Module Stacking work completes? Or should I wait for >> completion of stacking work? I want to know it, for recent proposals are >> rather staying silent. > > I wouldn't wait if it was my project, but I have been known > to be more aggressive than is good for me from time to time. >
It seems that stacking needs some more time. Manual with updated patch for current source code is available at https://caitsith.osdn.jp/index2.html . John, if you can resume reviewing, I'd like to propose CaitSith as one of "Minor modules" except security_module_enable() check. Regards.