From: Joshua Brindle <jbrindle@snu.edu>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: SELinux <SELinux@tycho.nsa.gov>
Subject: Re: X policy classes
Date: Fri, 14 May 2004 14:01:51 -0500 [thread overview]
Message-ID: <40A5179F.10508@snu.edu> (raw)
In-Reply-To: <1084556829.18592.5.camel@moss-spartans.epoch.ncsc.mil>
That is fine, we'll just need warning before those classes are put into
the mainline kernel so that our users can be sure to have upgraded
policies. Thanks again.
Joshua Brindle
Stephen Smalley wrote:
>On Fri, 2004-05-14 at 13:26, Joshua Brindle wrote:
>
>
>>--- security_classes.orig 2004-05-13 20:15:19.898433608 -0500
>>+++ security_classes 2004-05-13 12:37:47.489834072 -0500
>>@@ -47,6 +47,9 @@
>> # passwd/chfn/chsh
>> class passwd
>>
>>+# pax flags
>>+class pax
>>+
>> # SE-X Windows stuff
>> class drawable
>> class window
>>
>>
>>
>
>Hmmm...applying that diff now will perturb the values of the X window
>classes, requiring regeneration of the libselinux headers that went out
>in the release we just made and requiring a rebuild of any modified X
>servers upon a migration from libselinux-1.12 to any newer version. How
>much trouble is it for you to relocate the pax definition after the X
>classes and migrate your users?
>
>
>
--
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.
prev parent reply other threads:[~2004-05-14 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 6:19 X policy classes Joshua Brindle
2004-05-14 12:05 ` 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 [this message]
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=40A5179F.10508@snu.edu \
--to=jbrindle@snu.edu \
--cc=SELinux@tycho.nsa.gov \
--cc=sds@epoch.ncsc.mil \
/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.