From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>,
Darrel Goeddel <dgoeddel@TrustedCS.com>,
SELinux <SELinux@tycho.nsa.gov>
Subject: MCS Policy.
Date: Tue, 30 Aug 2005 14:38:54 -0400 [thread overview]
Message-ID: <4314A7BE.20001@redhat.com> (raw)
I have now added the following range_transitions to mcs policy
+range_transition init_t getty_exec_t s0 - s0:c0.c127;
+range_transition getty_t login_exec_t s0 - s0:c0.c127;
+range_transition initrc_t cupsd_exec_t s0 - s0:c0.c127;
+range_transition initrc_t udev_exec_t s0 - s0:c0.c127;
Kernel is starting out with s0.
The only problem I am seeing now is initrc wants to read the processs
pid on a killall and gets denials for getty, login, udev and cups. Is
there an easy way to allow this without increasing initrc's range?
I am also having problems getting root to login with s0-s0:c0.127
Seems to always transiton to s0.
In targetd policy local login logs root in as
user_u:system_r:unconfined_t:s0
ssh and su logs in as
root:system_r:unconfined_t:s0
/etc/selinux/targeted/contexts/users/root looks like
system_r:unconfined_t:s0 system_r:unconfined_t:s0 - s0:c0.c127
system_r:initrc_t:s0 system_r:unconfined_t:s0 - s0:c0.c127
system_r:local_login_t:s0 system_r:unconfined_t:s0 - s0:c0.c127
system_r:remote_login_t:s0 system_r:unconfined_t:s0 - s0:c0.c127
system_r:rshd_t:s0 system_r:unconfined_t:s0 - s0:c0.c127
system_r:crond_t:s0 system_r:unconfined_t:s0 - s0:c0.c127
Dan
--
--
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 reply other threads:[~2005-08-30 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 18:38 Daniel J Walsh [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-25 0:06 mcs policy Justin Mattock
2008-01-25 18:36 ` 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=4314A7BE.20001@redhat.com \
--to=dwalsh@redhat.com \
--cc=SELinux@tycho.nsa.gov \
--cc=dgoeddel@TrustedCS.com \
--cc=sds@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.