All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominick Grift <dac.override@gmail.com>
To: Russell Coker <russell@coker.com.au>
Cc: "selinux-refpolicy\@vger.kernel.org" 
	<selinux-refpolicy@vger.kernel.org>
Subject: Re: nnp_transition
Date: Tue, 22 Jan 2019 09:35:16 +0100	[thread overview]
Message-ID: <87bm49ytrv.fsf@gmail.com> (raw)
In-Reply-To: <8870278.Oar1g5JlLj@liv> (Russell Coker's message of "Tue, 22 Jan 2019 19:33:53 +1100")

Russell Coker <russell@coker.com.au> writes:

> 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"?

[root@brutus ~]# seinfo --polcap | grep nnp
   nnp_nosuid_transition

-- 
Key fingerprint = 5F4D 3CDB D3F8 3652 FBD8 02D5 3B6C 5F1D 2C7B 6B02
https://sks-keyservers.net/pks/lookup?op=get&search=0x3B6C5F1D2C7B6B02
Dominick Grift

      reply	other threads:[~2019-01-22  8:35 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   ` nnp_transition Russell Coker
2019-01-22  8:35     ` Dominick Grift [this message]

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=87bm49ytrv.fsf@gmail.com \
    --to=dac.override@gmail.com \
    --cc=russell@coker.com.au \
    --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 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.