From: Russell Coker <russell@coker.com.au>
To: Dominick Grift <dac.override@gmail.com>
Cc: "selinux-refpolicy@vger.kernel.org" <selinux-refpolicy@vger.kernel.org>
Subject: Re: nnp_transition
Date: Tue, 22 Jan 2019 19:33:53 +1100 [thread overview]
Message-ID: <8870278.Oar1g5JlLj@liv> (raw)
In-Reply-To: <87fttlyuv7.fsf@gmail.com>
On Tuesday, 22 January 2019 7:11:40 PM AEDT Dominick Grift wrote:
> > Getting close to a Debian release so I have to sort out the nnp_transition
> > rules. How do I work out what's going on here? Do I just assume that as
> > dpkg_t has generally less access than unconfined_t it's ok? Is it worth
> > investigating why something in apt is setting NNP?
>
> Not worth looking into if you ask me (this is just the tip of the mountain).
> You no longer have to worry about type bounds if you enable the polcap
> (which i think is the default)
What do you mean by "enable the polcap"?
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2019-01-22 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 22:47 nnp_transition Russell Coker
2019-01-22 8:11 ` nnp_transition Dominick Grift
2019-01-22 8:33 ` Russell Coker [this message]
2019-01-22 8:35 ` nnp_transition Dominick Grift
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=8870278.Oar1g5JlLj@liv \
--to=russell@coker.com.au \
--cc=dac.override@gmail.com \
--cc=selinux-refpolicy@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).