From: Russell Coker <russell@coker.com.au>
To: Colin Walters <walters@verbum.org>, selinux@tycho.nsa.gov
Subject: Re: [patch] a few small new macros for global_macros.te
Date: Wed, 16 Jul 2003 09:31:01 +1000 [thread overview]
Message-ID: <200307160931.01645.russell@coker.com.au> (raw)
In-Reply-To: <1058301863.14211.3.camel@columbia>
On Wed, 16 Jul 2003 06:44, Colin Walters wrote:
> I noticed a lot of .te files were repeatedly specifying access to etc_t
> and etc_runtime_t. So I created
> a macro normal_config_file_access for that. Also while the domain_trans
> macro is useful, it doesn't allow for #! scripts, since the file has to
> be read. So there's a new macro domain_trans_read.
In my tree domain_trans() does what your domain_trans_read() does.
Does it make sense to have a rule involveing ld_so_cache_t apart from
uses_shlib()? When would you want to grant access to ld_so_cache_t but not
use uses_shlib()?
What do you need extended_config_file_read_access() for?
--
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:[~2003-07-15 23:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 20:44 [patch] a few small new macros for global_macros.te Colin Walters
2003-07-15 23:31 ` Russell Coker [this message]
2003-07-16 4:27 ` Colin Walters
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=200307160931.01645.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
--cc=walters@verbum.org \
/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.