From: Andy Warner <warner@rubix.com>
To: selinux@tycho.nsa.gov
Subject: adding objects classes and permissions to policy
Date: Thu, 16 Oct 2008 21:40:43 +0200 [thread overview]
Message-ID: <48F798BB.6070602@rubix.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 300 bytes --]
When adding new object classes and permissions to SELinux policy is it
necessary to re-create flask.h and av_permissions.h header files so that
a user-space object manager can access the associated defines? If so,
would someone give me some pointers as to how these are generated?
Thanks,
Andy
[-- Attachment #2: Type: text/html, Size: 491 bytes --]
next reply other threads:[~2008-10-16 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 19:40 Andy Warner [this message]
2008-10-16 19:53 ` adding objects classes and permissions to policy Stephen Smalley
2008-10-16 19:55 ` Stephen Smalley
2008-10-17 9:45 ` Andy Warner
2008-10-17 12:13 ` Stephen Smalley
2008-10-17 14:18 ` Andy Warner
2008-10-17 14:23 ` Stephen Smalley
2008-10-17 15:14 ` Andy Warner
2008-10-17 15:15 ` Stephen Smalley
2008-10-17 15:55 ` Protecting against inadvertent file copy Sanjai Narain
2008-10-17 17:14 ` Stephen Smalley
2008-10-17 19:13 ` Sanjai Narain
2008-10-16 20:02 ` adding objects classes and permissions to policy Xavier Toth
2008-10-16 20:06 ` Stephen Smalley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48F798BB.6070602@rubix.com \
--to=warner@rubix.com \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.