Stephen Smalley <[EMAIL PROTECTED]> wrote: > Right, the latter is reasonable. > Requires adding the class and permission definition to > policy/flask/security_classes and policy/flask/access_vectors and then > regenerating the kernel headers from those files, ala: > svn co http://oss.tresys.com/repos/refpolicy/trunk refpolicy > cd refpolicy/policy/flask > vi security_classes access_vectors > <add new class to end> > make > make LINUX_D=/path/to/linux-2.6 tokern
Does this require rebuilding and updating all the SELinux rpms to know about the new class? David -- 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/
