From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: list of permissions created by allow2audit: what do i do now?
Date: Tue, 18 May 2004 13:02:44 +0000 [thread overview]
Message-ID: <20040518130244.GB24917@lkcl.net> (raw)
In-Reply-To: <1084884047.28966.59.camel@moss-spartans.epoch.ncsc.mil>
On Tue, May 18, 2004 at 08:40:47AM -0400, Stephen Smalley wrote:
> On Tue, 2004-05-18 at 06:40, Luke Kenneth Casson Leighton wrote:
> > from the list, below, i've removed me editing syslog as root without
> > doing newrole -r system_r :)
>
> sysadm_r, not system_r.
hey, given that i haven't allowed my useraccount to do newrole
to _either_ of those...
> > allow initrc_t xdm_rw_etc_t:dir { add_name remove_name write };
> > allow initrc_t xdm_rw_etc_t:file { create ioctl rename unlink write };
> >
> > i mean, i see in domains/programs/xdm.te that there _are_
> > allow initrc_t xdm_rw_etc_t permissions for create (create_file_perms)
> > and also a comment that init scripts want to check for update
> > windowmanagerlist so they get getattr and read allowed.
> >
> > ... so what's going on?? why am i getting these messages?
>
> In the upstream policy, I see:
> $ grep 'allow initrc_t xdm_rw_etc_t' policy.conf
> allow initrc_t xdm_rw_etc_t:file { getattr read };
>
> So initrc_t is presently only allowed to stat and read those files.
> Now, there are other rules for xdm_t:
> $ grep 'allow xdm_t xdm_rw_etc_t' policy.conf
> allow xdm_t xdm_rw_etc_t:dir { read getattr lock search ioctl add_name remove_name write };
> allow xdm_t xdm_rw_etc_t:file { create ioctl read getattr lock write setattr append link unlink rename };
>
> And the xdm.te source file does have a comment prior to the
> corresponding source statements that says that this is for wdm.
> But perhaps someone erred and submitted the wrong rules for wdm (we
> don't use it ourselves).
okay, maybe this is a silly question.
given the number of errors i am seeing, and given that they won't
go away, perhaps there is some breakdown in communication between
the rules being in the policy.conf file and their application to
packages.
for example, should i be doing a make relabel every time i add
some new rules?
should i force setfiles usage just like there is in
/etc/dpkg/postinst.d/selinux?
am i on the right track, here?
> > if i am using wdm (the patched version) is there anything i need to
> > do to get it to work / be accepted?
>
> Don't know, as I've never used it.
ah. then i will try.... xdm, and see what happens.
(wdm is the patched one from daniel walsh).
--
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:[~2004-05-18 13:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 10:40 list of permissions created by allow2audit: what do i do now? Luke Kenneth Casson Leighton
2004-05-18 12:40 ` Stephen Smalley
2004-05-18 13:02 ` Luke Kenneth Casson Leighton [this message]
2004-05-18 13:20 ` Stephen Smalley
2004-05-18 13:30 ` Stephen Smalley
2004-05-18 13:44 ` Stephen Smalley
2004-05-18 14:08 ` Luke Kenneth Casson Leighton
2004-05-18 15:11 ` Luke Kenneth Casson Leighton
2004-05-18 17:18 ` Stephen Smalley
2004-05-18 18:51 ` Luke Kenneth Casson Leighton
2004-05-18 19:54 ` Stephen Smalley
2004-05-18 20:18 ` Luke Kenneth Casson Leighton
2004-05-18 20:48 ` Russell Coker
2004-05-18 20:56 ` Luke Kenneth Casson Leighton
2004-05-18 19:51 ` Luke Kenneth Casson Leighton
2004-05-18 18:02 ` Russell Coker
2004-05-18 16:25 ` Valdis.Kletnieks
2004-05-18 19:12 ` Luke Kenneth Casson Leighton
2004-05-18 12:56 ` Luke Kenneth Casson Leighton
2004-05-18 13:14 ` Stephen Smalley
2004-05-18 15:19 ` Luke Kenneth Casson Leighton
2004-05-18 14:29 ` Russell Coker
2004-05-18 15:30 ` Luke Kenneth Casson Leighton
2004-05-18 14:01 ` Russell Coker
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=20040518130244.GB24917@lkcl.net \
--to=lkcl@lkcl.net \
--cc=sds@epoch.ncsc.mil \
--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.