From: Topi Miettinen <toiwoton@gmail.com>
To: SElinux list <selinux@vger.kernel.org>
Subject: Strange AVC denials without effect
Date: Fri, 3 Jul 2020 13:28:34 +0300 [thread overview]
Message-ID: <35be1a17-1b72-fca7-55b2-b3f32b4e13aa@gmail.com> (raw)
Hello,
I renamed SELinux packet types and also without using type attributes
(like packet_type etc), so that refpolicy TE rules for packets should
not apply. Then I added new rules for the new types one by one as they
were needed. But there are lots of audit entries which would seem to
indicate that kernel_t is prevented from sending packets:
type=AVC msg=audit(1593770235.180:3222): avc: denied { send } for
pid=408 comm="irq/30-iwlwifi" saddr=10.0.0.3 daddr=1.1.1.1 netif=wlan0
scontext=system_u:system_r:kernel_t:s0
tcontext=system_u:object_r:my_dns_client_packet_t:s0 tclass=packet
permissive=0
In reality, the packets are sent. But kernel_t is not permissive and
there should not be any rules which would allow the action, so shouldn't
this prevent packet transmission?
-Topi
next reply other threads:[~2020-07-03 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 10:28 Topi Miettinen [this message]
2020-07-03 13:49 ` Strange AVC denials without effect Paul Moore
2020-07-03 18:16 ` Topi Miettinen
2020-07-04 13:15 ` Topi Miettinen
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=35be1a17-1b72-fca7-55b2-b3f32b4e13aa@gmail.com \
--to=toiwoton@gmail.com \
--cc=selinux@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