public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jason Zaman" <perfinion@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-refpolicy:next commit in: policy/
Date: Tue, 24 Feb 2015 17:11:19 +0000 (UTC)	[thread overview]
Message-ID: <1424021785.5b8d41a56f311e6238010a2b2d42480f904eefb6.perfinion@gentoo> (raw)

commit:     5b8d41a56f311e6238010a2b2d42480f904eefb6
Author:     Chris PeBenito <cpebenito <AT> tresys <DOT> com>
AuthorDate: Tue Jan 27 22:25:36 2015 +0000
Commit:     Jason Zaman <perfinion <AT> gentoo <DOT> org>
CommitDate: Sun Feb 15 17:36:25 2015 +0000
URL:        http://sources.gentoo.org/gitweb/?p=proj/hardened-refpolicy.git;a=commit;h=5b8d41a5

Add always_check_network policy capability.

Disabled by default, as most systems don't want/need this.

---
 policy/policy_capabilities | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/policy/policy_capabilities b/policy/policy_capabilities
index db3cbca..70a4311 100644
--- a/policy/policy_capabilities
+++ b/policy/policy_capabilities
@@ -31,3 +31,13 @@ policycap network_peer_controls;
 # blk_file: open
 #
 policycap open_perms;
+
+# Always enforce network access controls, even
+# if labeling is not configured for them.
+# Available in kernel 3.13+
+#
+# Checks enabled:
+# packet: send recv
+# peer: recv
+#
+# policycap always_check_network;


             reply	other threads:[~2015-02-24 17:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 17:11 Jason Zaman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-03-04 17:16 [gentoo-commits] proj/hardened-refpolicy:next commit in: policy/ Sven Vermeulen
2017-02-17  8:50 Jason Zaman
2017-02-25 14:59 Jason Zaman
2017-02-25 16:58 Jason Zaman
2017-02-27 11:40 Jason Zaman
2017-03-30 17:09 Jason Zaman
2017-04-30  9:40 Jason Zaman
2017-05-07 17:47 Jason Zaman
2017-05-25 17:08 Jason Zaman
2017-09-10 14:03 Jason Zaman

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=1424021785.5b8d41a56f311e6238010a2b2d42480f904eefb6.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