public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sven Vermeulen" <sven.vermeulen@siphos.be>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-refpolicy:master commit in: policy/modules/admin/
Date: Wed, 18 Sep 2013 14:08:21 +0000 (UTC)	[thread overview]
Message-ID: <1379513245.3b7bfcfd65b3892a0a8f5b07e5d4273c671f5ad6.SwifT@gentoo> (raw)

commit:     3b7bfcfd65b3892a0a8f5b07e5d4273c671f5ad6
Author:     Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be>
AuthorDate: Wed Sep 18 14:07:25 2013 +0000
Commit:     Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be>
CommitDate: Wed Sep 18 14:07:25 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-refpolicy.git;a=commit;h=3b7bfcfd

Fix bug #485304 - Allow capabilities for ping

When the ping binary is not setuid, but uses capabilities, then the ping_t
domain needs to be able to get and set capabilities.

---
 policy/modules/admin/netutils.te | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/policy/modules/admin/netutils.te b/policy/modules/admin/netutils.te
index 557da97..59933cd 100644
--- a/policy/modules/admin/netutils.te
+++ b/policy/modules/admin/netutils.te
@@ -212,3 +212,13 @@ userdom_use_user_terminals(traceroute_t)
 dev_read_rand(traceroute_t)
 dev_read_urand(traceroute_t)
 files_read_usr_files(traceroute_t)
+
+ifdef(`distro_gentoo',`
+	#########################################
+	#
+	# ping_t policy
+	#
+
+	# When not using setuid ping but capabilities
+	allow ping_t self:process { getcap setcap };
+')


             reply	other threads:[~2013-09-18 14:08 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 14:08 Sven Vermeulen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-08 23:55 [gentoo-commits] proj/hardened-refpolicy:master commit in: policy/modules/admin/ Jason Zaman
2024-12-15  0:30 Jason Zaman
2024-10-21 15:19 Kenton Groombridge
2024-05-14 19:42 Kenton Groombridge
2023-02-13 15:35 Kenton Groombridge
2023-02-13 15:35 Kenton Groombridge
2023-02-13 15:35 Kenton Groombridge
2023-02-13 15:35 Kenton Groombridge
2023-02-13 15:35 Kenton Groombridge
2022-12-13 20:55 Kenton Groombridge
2022-11-02 14:42 Kenton Groombridge
2022-11-02 14:42 Kenton Groombridge
2022-11-02 14:42 Kenton Groombridge
2022-09-03 20:04 Kenton Groombridge
2022-09-03 19:54 Jason Zaman
2022-03-31  3:31 Jason Zaman
2022-02-27  2:52 Jason Zaman
2022-02-27  2:52 Jason Zaman
2022-01-31 19:31 Jason Zaman
2022-01-31 19:31 Jason Zaman
2021-11-21 23:20 Jason Zaman
2021-11-21 19:33 Jason Zaman
2021-11-21 19:33 Jason Zaman
2021-11-21  3:00 Jason Zaman
2021-11-21  3:00 Jason Zaman
2021-11-21  3:00 Jason Zaman
2021-11-12  2:00 Jason Zaman
2021-11-11 21:27 Jason Zaman
2021-11-11 21:27 Jason Zaman
2021-09-05 16:00 Jason Zaman
2021-02-07  3:20 Jason Zaman
2021-02-01  2:10 Jason Zaman
2020-11-29  9:14 Jason Zaman
2020-11-28 23:09 Jason Zaman
2020-02-15  7:33 Jason Zaman
2019-12-16 17:48 Jason Zaman
2019-12-16 17:48 Jason Zaman
2019-07-13  7:01 Jason Zaman
2019-07-13  7:01 Jason Zaman
2019-07-13  7:01 Jason Zaman
2019-07-13  7:01 Jason Zaman
2019-07-13  7:01 Jason Zaman
2019-07-13  7:01 Jason Zaman
2019-07-13  7:01 Jason Zaman
2019-07-13  7:01 Jason Zaman
2019-07-13  7:01 Jason Zaman
2019-03-26 10:17 Jason Zaman
2019-03-26 10:17 Jason Zaman
2019-03-26 10:17 Jason Zaman
2019-03-26 10:17 Jason Zaman
2018-12-09 11:48 Jason Zaman
2018-11-11 23:29 Jason Zaman
2018-11-11 23:29 Jason Zaman
2018-11-11 23:29 Jason Zaman
2018-07-12 14:37 Jason Zaman
2017-10-29 20:42 Jason Zaman
2017-06-13  8:25 Jason Zaman
2017-02-17  8:44 Jason Zaman
2017-02-05  9:53 Jason Zaman
2017-01-01 16:36 Jason Zaman
2016-05-13  5:37 Jason Zaman
2015-07-15 13:47 Sven Vermeulen
2015-06-09 10:45 [gentoo-commits] proj/hardened-refpolicy:next " Sven Vermeulen
2015-06-09 10:52 ` [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen
2015-06-07  9:31 [gentoo-commits] proj/hardened-refpolicy:next " Sven Vermeulen
2015-06-09 10:52 ` [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen
2015-05-16 11:31 Sven Vermeulen
2015-01-25 14:04 Sven Vermeulen
2014-11-28 10:04 [gentoo-commits] proj/hardened-refpolicy:next " Sven Vermeulen
2014-11-22 17:43 ` [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen
2014-11-27 22:23 Sven Vermeulen
2014-10-12  8:59 [gentoo-commits] proj/hardened-refpolicy:next " Sven Vermeulen
2014-10-12  9:13 ` [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen
2014-10-12  8:44 [gentoo-commits] proj/hardened-refpolicy:next " Sven Vermeulen
2014-10-12  9:13 ` [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen
2014-10-12  8:27 Sven Vermeulen
2014-10-12  8:27 Sven Vermeulen
2014-10-12  8:27 Sven Vermeulen
2014-08-31 18:14 Sven Vermeulen
2014-08-19 20:07 Sven Vermeulen
2014-08-19 20:07 Sven Vermeulen
2014-04-08 16:02 Sven Vermeulen
2014-03-25 19:47 Sven Vermeulen
2014-03-04 15:30 Sven Vermeulen
2014-03-04 15:30 Sven Vermeulen
2014-03-04 15:30 Sven Vermeulen
2014-02-15  9:45 Sven Vermeulen
2014-02-02 12:18 Sven Vermeulen
2013-12-06 17:33 Sven Vermeulen
2013-12-06 17:33 Sven Vermeulen
2013-09-27 13:27 Sven Vermeulen
2013-09-27 13:27 Sven Vermeulen
2013-09-24 17:10 Sven Vermeulen
2013-08-17 18:12 Sven Vermeulen
2013-08-15 12:18 Sven Vermeulen
2013-08-15 12:10 Sven Vermeulen
2013-08-15 12:07 Sven Vermeulen
2013-08-15 11:44 Sven Vermeulen
2013-08-15 11:44 Sven Vermeulen
2013-08-15 11:44 Sven Vermeulen
2013-08-15 11:44 Sven Vermeulen
2013-04-11  7:19 Sven Vermeulen
2013-04-11  7:19 Sven Vermeulen
2013-03-29 12:04 Sven Vermeulen
2013-01-27 13:15 Sven Vermeulen
2013-01-03 16:49 Sven Vermeulen
2012-12-17  9:33 Sven Vermeulen
2012-12-04 20:44 Sven Vermeulen
2012-11-27 19:14 Sven Vermeulen
2012-11-17 20:18 Sven Vermeulen
2012-10-30 20:24 Sven Vermeulen
2012-10-30 20:24 Sven Vermeulen
2012-10-10 19:52 Sven Vermeulen
2012-05-28  8:41 Sven Vermeulen
2012-04-22 12:41 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=1379513245.3b7bfcfd65b3892a0a8f5b07e5d4273c671f5ad6.SwifT@gentoo \
    --to=sven.vermeulen@siphos.be \
    --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