Stephen Smalley <sds@xxxxxxxxxxxxx> 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 -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
