From: Paul Moore <paul.moore@hp.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SE Linux <selinux@tycho.nsa.gov>,
Daniel J Walsh <dwalsh@redhat.com>,
"Christopher J.PeBenito" <cpebenito@tresys.com>
Subject: Re: Running racoon from init_t?
Date: Fri, 9 Mar 2007 14:31:11 -0500 [thread overview]
Message-ID: <200703091431.12416.paul.moore@hp.com> (raw)
In-Reply-To: <1173462020.3241.131.camel@moss-spartans.epoch.ncsc.mil>
On Friday, March 9 2007 12:40:20 pm Stephen Smalley wrote:
> On Fri, 2007-03-09 at 12:36 -0500, Stephen Smalley wrote:
> > On Fri, 2007-03-09 at 12:09 -0500, Paul Moore wrote:
> > > I suspect this can fixed by adding the following to the policy,
> > > suggestions?
> > >
> > > init_use_fds(racoon_t)
> >
> > I'd have expected it to pick up the right rules from being an
> > init_daemon_domain().
>
> Actually, I'd tend to think that should be dontaudit'd - it doesn't have
> a legitimate need to access the console, right? Then SELinux will just
> close the descriptor silently and replace it with a ref to the null
> device.
That sounds reasonable as any configuration done in in this context will have
to be from a configuration file and not from stdin.
--
paul moore
linux security @ hp
--
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:[~2007-03-09 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 17:09 Running racoon from init_t? Paul Moore
2007-03-09 17:36 ` Stephen Smalley
2007-03-09 17:40 ` Stephen Smalley
2007-03-09 19:31 ` Paul Moore [this message]
2007-03-09 21:30 ` Christopher J. PeBenito
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=200703091431.12416.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--cc=sds@tycho.nsa.gov \
--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.