From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Latest Ref Policy Diffs
Date: Fri, 09 Dec 2005 09:47:56 -0500 [thread overview]
Message-ID: <1134139676.8185.40.camel@sgc> (raw)
In-Reply-To: <43999777.1020509@redhat.com>
On Fri, 2005-12-09 at 09:40 -0500, Daniel J Walsh wrote:
> Christopher J. PeBenito wrote:
> > On Thu, 2005-12-08 at 16:14 -0500, Daniel J Walsh wrote:
> >
> >> Major change in targeted policy is about to hit. Basically we are going
> >> to turn off allow_execmod, allow_execmem, and allow_execstack by default
> >> for unconfined_t programs.
> >>
> > I just have a question about this hunk:
> >
> >> @@ -79,6 +75,8 @@
> >>
> >> ifdef(`targeted_policy',`
> >> unconfined_domain_template(xdm_t)
> >> + allow xdm_t self:process execmem;
> >> + unconfined_domtrans(xdm_t)
> >> ',`
> >> allow xdm_t xdm_lock_t:file create_file_perms;
> >> files_create_lock(xdm_t,xdm_lock_t)
> >>
> >
> > Shouldn't the execmem be outside of the ifdef, since if it needs this,
> > it will need it regardless of the policy type?
> >
> I think in a strict policy machine, the xserver will need this not xdm?
>
> Since we are not using xserver policy, The xserver is running as xdm.
Ok, that makes sense.
--
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150
--
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.
next prev parent reply other threads:[~2005-12-09 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 21:14 Latest Ref Policy Diffs Daniel J Walsh
2005-12-09 14:21 ` Christopher J. PeBenito
2005-12-09 14:40 ` Daniel J Walsh
2005-12-09 14:47 ` Christopher J. PeBenito [this message]
2005-12-09 21:24 ` Christopher J. PeBenito
2005-12-12 14:54 ` Stephen Smalley
2005-12-12 16:41 ` Christopher J. PeBenito
2005-12-12 18:31 ` Eric Paris
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=1134139676.8185.40.camel@sgc \
--to=cpebenito@tresys.com \
--cc=dwalsh@redhat.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.