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:11:40 +0100 [thread overview]
Message-ID: <87fttlyuv7.fsf@gmail.com> (raw)
In-Reply-To: <6525171.sqPiMeOL83@liv> (Russell Coker's message of "Tue, 22 Jan 2019 09:47:04 +1100")
Russell Coker <russell@coker.com.au> writes:
> 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)
>
> type=PROCTITLE msg=audit(22/01/19 07:08:31.692:1104) : proctitle=/usr/bin/dpkg
> --print-foreign-architectures
> type=SYSCALL msg=audit(22/01/19 07:08:31.692:1104) : arch=x86_64
> syscall=execve success=yes exit=0 a0=0x5611b27bd0e0 a1=0x5611b27c1590
> a2=0x7fff0e8f51f0 a3=0x1 items=0 ppid=18604 pid=18605 auid=root uid=_apt
> gid=nogroup euid=_apt suid=_apt fsuid=_apt egid=nogroup sgid=nogroup
> fsgid=nogroup tty=pts2 ses=9 comm=dpkg exe=/usr/bin/dpkg
> subj=unconfined_u:unconfined_r:dpkg_t:s0-s0:c0.c1023 key=(null)
> type=AVC msg=audit(22/01/19 07:08:31.692:1104) : avc: granted {
> nnp_transition } for pid=18605 comm=apt-config
> scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
> tcontext=unconfined_u:unconfined_r:dpkg_t:s0-s0:c0.c1023 tclass=process2
--
Key fingerprint = 5F4D 3CDB D3F8 3652 FBD8 02D5 3B6C 5F1D 2C7B 6B02
https://sks-keyservers.net/pks/lookup?op=get&search=0x3B6C5F1D2C7B6B02
Dominick Grift
next prev parent reply other threads:[~2019-01-22 8:11 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 ` Dominick Grift [this message]
2019-01-22 8:33 ` nnp_transition Russell Coker
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=87fttlyuv7.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 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).