From: Russell Coker <russell@coker.com.au>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: list of permissions created by allow2audit: what do i do now?
Date: Wed, 19 May 2004 04:02:16 +1000 [thread overview]
Message-ID: <200405190402.16586.russell@coker.com.au> (raw)
In-Reply-To: <20040518151112.GF24917@lkcl.net>
On Wed, 19 May 2004 01:11, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> /usr/bin/[xgkw]dm -- system_u:object_r:xdm_exec_t
>
> therefore, the programs gdm, xdm, kdm and wdm all have type xdm_exec_t
> therefore, according to line 24 of domains/programs/xdm.te, gdm,
> xdm, kdm and wdm are all allowed to automatically transition from
> the initialisation context into a new context named xdm_t.
Yes, and they can also transition from initrc_t by line 21. This is important
because in Debian xdm is not started directly from init.
> therefore, the programs gdm, xdm, kdm and wdm are all allowed to do
> the things that are mentioned as allow xdm_t etc.
Yes.
> okay, just a guess: when you declare an allow, are the relevant
> permissions added or replaced if there already exists, say,
> allow xdm_xserver_t var_lib_t:file { read };
Added.
> and i then add, in a following line to policy.conf :
> allow xdm_xserver_t var_lib_t:file { getattr };
>
> do i end up with _only_ getattr permissions or do i end up
> with both read _and_ getattr?
Both.
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
--
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 18:03 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
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 [this message]
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=200405190402.16586.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=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.