--- Jan Engelhardt <[EMAIL PROTECTED]> wrote: > > On Nov 28 2007 18:22, [EMAIL PROTECTED] wrote: > > > >Talpa is modular itself being composed of a set of kernel modules of which > >not all are loaded simultaneously. Where possible LSM can be used and _no_ > >messing with syscall table will take place. Unfortunately where another > >LSM user is present that won't work > > SELinux supports chaining, so if talpa is loaded as a secondary to selinux, > where is the problem? For those LSMs which do not support chaining (*cough* > apparmor *cough* be one, mtadm another), fix them.
Um, cough cough (I ready do have a nasty cold) SELinux supports a very limited bit of chaining. I don't think you're going to be chaining security_secid_to_secctx() or security_secctx_to_secid() with the current SELinux code, but you could prove me wrong there. Chaining is a red herring. If you want talpa it seems that you have a use case that isn't going to require the presence of another LSM. You may have other issues, but at this point I say throw caution to the wind, clean it up based on the suggestions you've seen here, and put the patch up as an RFC on the LSM list. What's the worst that could happen? Casey Schaufler [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
