Stephen Smalley <sds@xxxxxxxxxxxxx> wrote: > It is just a way of carving up the permission space, typically based on > object type, but it can essentially be arbitrary. The check in this > case seems specific to cachefiles since it is controlling an operation > on the /dev/cachefiles interface that only applies to cachefiles > internal operations, so making a cachefiles class seems reasonable. Can you specify what sort of permissions you're thinking of providing for tasks to operate on this class? Can an object of this class 'operate' on other objects, or can only process-class objects do that? How does an object of this class acquire a label? What is an object of this class? Is it a "cache"? Or were you thinking of a "module"? 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.
