From: "Kenton Groombridge" <concord@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-refpolicy:concord-dev commit in: policy/modules/system/
Date: Wed, 12 Oct 2022 13:35:00 +0000 (UTC) [thread overview]
Message-ID: <1665581543.985e8bcece6c3e6ab5d2cfc3326f2f44eaeb0bb3.concord@gentoo> (raw)
commit: 985e8bcece6c3e6ab5d2cfc3326f2f44eaeb0bb3
Author: Kenton Groombridge <concord <AT> gentoo <DOT> org>
AuthorDate: Wed Oct 12 13:32:23 2022 +0000
Commit: Kenton Groombridge <concord <AT> gentoo <DOT> org>
CommitDate: Wed Oct 12 13:32:23 2022 +0000
URL: https://gitweb.gentoo.org/proj/hardened-refpolicy.git/commit/?id=985e8bce
lvm: add file context for dmeventd in /usr/bin
Signed-off-by: Kenton Groombridge <concord <AT> gentoo.org>
policy/modules/system/lvm.fc | 1 +
1 file changed, 1 insertion(+)
diff --git a/policy/modules/system/lvm.fc b/policy/modules/system/lvm.fc
index 378970e5..602e810c 100644
--- a/policy/modules/system/lvm.fc
+++ b/policy/modules/system/lvm.fc
@@ -148,5 +148,6 @@
ifdef(`distro_gentoo',`
# Bug 529430 comment 8
+/usr/bin/dmeventd -- gen_context(system_u:object_r:lvm_exec_t,s0)
/usr/sbin/dmeventd -- gen_context(system_u:object_r:lvm_exec_t,s0)
')
next reply other threads:[~2022-10-12 13:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 13:35 Kenton Groombridge [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-12 13:34 [gentoo-commits] proj/hardened-refpolicy:concord-dev commit in: policy/modules/system/ Kenton Groombridge
2022-10-12 13:34 Kenton Groombridge
2022-10-12 13:34 Kenton Groombridge
2022-09-03 20:04 [gentoo-commits] proj/hardened-refpolicy:master " Kenton Groombridge
2022-10-12 13:35 ` [gentoo-commits] proj/hardened-refpolicy:concord-dev " Kenton Groombridge
2022-09-03 20:04 [gentoo-commits] proj/hardened-refpolicy:master " Kenton Groombridge
2022-10-12 13:34 ` [gentoo-commits] proj/hardened-refpolicy:concord-dev " Kenton Groombridge
2022-06-06 15:15 Kenton Groombridge
2022-06-06 15:15 Kenton Groombridge
2022-06-06 15:15 Kenton Groombridge
2022-06-06 15:13 [gentoo-commits] proj/hardened-refpolicy:various-20211111 " Kenton Groombridge
2022-06-06 15:13 ` [gentoo-commits] proj/hardened-refpolicy:concord-dev " Kenton Groombridge
2022-06-06 15:13 [gentoo-commits] proj/hardened-refpolicy:various-20211111 " Kenton Groombridge
2022-06-06 15:13 ` [gentoo-commits] proj/hardened-refpolicy:concord-dev " Kenton Groombridge
2022-06-06 15:13 [gentoo-commits] proj/hardened-refpolicy:various-20211111 " Kenton Groombridge
2022-06-06 15:13 ` [gentoo-commits] proj/hardened-refpolicy:concord-dev " Kenton Groombridge
2022-06-06 15:08 Kenton Groombridge
2022-06-06 15:08 Kenton Groombridge
2022-06-06 15:08 Kenton Groombridge
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=1665581543.985e8bcece6c3e6ab5d2cfc3326f2f44eaeb0bb3.concord@gentoo \
--to=concord@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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