All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <jbrindle@snu.edu>
To: SELinux <SELinux@tycho.nsa.gov>
Subject: X policy classes
Date: Fri, 14 May 2004 01:19:23 -0500	[thread overview]
Message-ID: <40A464EB.5030008@snu.edu> (raw)

We noticed today that the SE-X policy classes have been merged into the 
sf.net cvs policy. Is there an ETA on when those will be merged into the 
kernel headers?

The reason I ask is because we added the pax class in Gentoo policy and 
kernels, now the ordering becomes an issue because with our current 
kernels (with pax support included) the policy flask/access_vectors 
ordering would have to have pax and then X classes but that would 
prevent a user from using a vanilla kernel which has the X classes in 
the headers.

We'll probably go ahead and add the X classes to our kernel headers and 
pax below them so that both vanilla and gentoo kernels would be able to 
load the same policy but we'll need to make changes to our policy and 
would like to know when we can expect the headers to be changed.

Another idea might be to add the pax class to the standard access_vector 
  file but I'm not sure how receptive that would be since afaik we are 
the only ones using it.

Joshua Brindle


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

             reply	other threads:[~2004-05-14  6:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14  6:19 Joshua Brindle [this message]
2004-05-14 12:05 ` X policy classes Stephen Smalley
2004-05-14 17:26   ` Joshua Brindle
2004-05-14 17:47     ` Stephen Smalley
2004-05-14 19:00       ` Chris PeBenito
2004-05-14 19:08         ` Stephen Smalley
2004-05-26 15:35           ` Stephen Smalley
2004-05-26 15:50             ` Stephen Smalley
2004-05-14 19:01       ` Joshua Brindle

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=40A464EB.5030008@snu.edu \
    --to=jbrindle@snu.edu \
    --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.