From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] modules_object_t vs. modules_dep_t labeling
Date: Mon, 5 Oct 2015 08:14:25 -0400 [thread overview]
Message-ID: <561269A1.7040202@tresys.com> (raw)
In-Reply-To: <560D03C1.9060102@redhat.com>
On 10/1/2015 5:58 AM, Miroslav Grepl wrote:
> We have more and more bugs with mislabeled /lib/modules/*/modules.dep*
> files. There is a default label for them - modules_dep_t but we get them
> labeled as modules_object_t. Yes, we can add filename transition rules
> and also find a reason why they get wrong labeling (in progress).
>
> But is there a big advantage to have these two labels. At least I don't
> see it from the policy point of view (sesearch).
I'm open to merging them, but would first have to do some further analysis.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2015-10-05 12:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 9:58 [refpolicy] modules_object_t vs. modules_dep_t labeling Miroslav Grepl
2015-10-05 12:14 ` Christopher J. PeBenito [this message]
2015-10-05 12:48 ` Dominick Grift
2015-10-06 18:13 ` Dominick Grift
2015-10-05 16:34 ` Dominick Grift
2015-10-05 19:17 ` Christopher J. PeBenito
2015-10-06 11:29 ` Dominick Grift
2015-10-06 11:46 ` Dominick Grift
2015-10-08 5:13 ` Miroslav Grepl
2015-10-08 13:15 ` Christopher J. PeBenito
2015-10-09 7:17 ` Miroslav Grepl
2015-10-10 7:17 ` Sven Vermeulen
2015-10-10 12:46 ` Daniel J Walsh
2015-10-10 13:40 ` Dominick Grift
2015-10-12 7:23 ` Miroslav Grepl
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=561269A1.7040202@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.com \
/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.