From: "Jason Zaman" <perfinion@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-refpolicy:master commit in: policy/flask/
Date: Sat, 28 Nov 2020 23:09:30 +0000 (UTC) [thread overview]
Message-ID: <1605517423.dadb27bdd553c2e64101dc9992a1df4f6e5975d0.perfinion@gentoo> (raw)
commit: dadb27bdd553c2e64101dc9992a1df4f6e5975d0
Author: Dannick Pomerleau <dannickp <AT> hotmail <DOT> com>
AuthorDate: Fri Oct 16 00:49:49 2020 +0000
Commit: Jason Zaman <perfinion <AT> gentoo <DOT> org>
CommitDate: Mon Nov 16 09:03:43 2020 +0000
URL: https://gitweb.gentoo.org/proj/hardened-refpolicy.git/commit/?id=dadb27bd
access_vectors: Add new capabilities to cap2
Updated location of capability definitions to point to current location within kernel source code.
CAP_BPF and CAP_PERFMON mainlined in: cb8e59cc87201af93dfbb6c3dccc8fcad72a09c2, original commit: a17b53c4a4b55ec322c132b6670743612229ee9c
CAP_CHECKPOINT_RESTORE mainlined in: 74858abbb1032222f922487fd1a24513bbed80f9, original commit: 124ea650d3072b005457faed69909221c2905a1f
The missing capabilities were noticed on archlinux with kernel 5.8.14-arch1-1.
Signed-off-by: Dannick Pomerleau <dannickp <AT> hotmail.com>
Signed-off-by: Jason Zaman <perfinion <AT> gentoo.org>
policy/flask/access_vectors | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/policy/flask/access_vectors b/policy/flask/access_vectors
index a9aceb46..d464a3de 100644
--- a/policy/flask/access_vectors
+++ b/policy/flask/access_vectors
@@ -132,7 +132,7 @@ common x_device
#
common cap
{
- # The capabilities are defined in include/linux/capability.h
+ # The capabilities are defined in include/uapi/linux/capability.h
# Capabilities >= 32 are defined in the cap2 common.
# Care should be taken to ensure that these are consistent with
# those definitions. (Order matters)
@@ -179,6 +179,9 @@ common cap2
wake_alarm
block_suspend
audit_read
+ perfmon
+ bpf
+ checkpoint_restore
}
#
next reply other threads:[~2020-11-28 23:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 23:09 Jason Zaman [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-01 19:56 [gentoo-commits] proj/hardened-refpolicy:master commit in: policy/flask/ Kenton Groombridge
2022-03-31 3:31 Jason Zaman
2020-02-15 7:33 Jason Zaman
2019-12-16 17:48 Jason Zaman
2019-03-26 10:17 Jason Zaman
2018-11-11 23:29 Jason Zaman
2018-06-08 10:07 Jason Zaman
2017-05-18 17:02 [gentoo-commits] proj/hardened-refpolicy:swift " Sven Vermeulen
2017-05-18 17:03 ` [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen
2016-08-13 18:35 [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman
2016-08-13 18:32 ` [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman
2016-05-13 5:37 Jason Zaman
2016-05-13 5:37 Jason Zaman
2015-10-26 5:48 Jason Zaman
2015-05-22 19:32 Jason Zaman
2014-11-23 14:06 [gentoo-commits] proj/hardened-refpolicy:bitcoin " Sven Vermeulen
2014-11-22 16:25 ` [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen
2014-06-25 19:06 Sven Vermeulen
2014-06-25 19:06 Sven Vermeulen
2014-06-25 19:06 Sven Vermeulen
2013-02-04 19:17 Sven Vermeulen
2012-07-26 19:23 Sven Vermeulen
2012-06-24 7:40 Sven Vermeulen
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=1605517423.dadb27bdd553c2e64101dc9992a1df4f6e5975d0.perfinion@gentoo \
--to=perfinion@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