From: "Sven Vermeulen" <swift@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-refpolicy:testing commit in: policy/modules/kernel/
Date: Thu, 7 Aug 2014 12:30:44 +0000 (UTC) [thread overview]
Message-ID: <1407414491.5fd609058ca8eec44bac6baf0a510511a79c6bce.swift@gentoo> (raw)
commit: 5fd609058ca8eec44bac6baf0a510511a79c6bce
Author: Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be>
AuthorDate: Thu Aug 7 12:28:11 2014 +0000
Commit: Sven Vermeulen <swift <AT> gentoo <DOT> org>
CommitDate: Thu Aug 7 12:28:11 2014 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-refpolicy.git;a=commit;h=5fd60905
Introduce files_relabel_all_pids
The files_relabel_all_pids allows for relabelfrom/relabelto privileges
on files, symbolic links and directories (for now) of the types
associated with the pidfile attribute, which basically is *_var_run_t
and var_run_t.
---
policy/modules/kernel/files.if | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/policy/modules/kernel/files.if b/policy/modules/kernel/files.if
index 5d53aa4..609de1f 100644
--- a/policy/modules/kernel/files.if
+++ b/policy/modules/kernel/files.if
@@ -6752,3 +6752,24 @@ interface(`files_manage_non_security_file_type',`
manage_sock_files_pattern($1, non_security_file_type, non_security_file_type)
')
+########################################
+## <summary>
+## Relabel all pidfile resources.
+## </summary>
+## <param name="domain">
+## <summary>
+## Domain allowed access.
+## </summary>
+## </param>
+## <rolecap/>
+#
+interface(`files_relabel_all_pids',`
+ gen_require(`
+ attribute pidfile;
+ ')
+
+ allow $1 pidfile:dir list_dir_perms;
+ relabel_dirs_pattern($1, pidfile, pidfile)
+ relabel_files_pattern($1, pidfile, pidfile)
+ relabel_lnk_files_pattern($1, pidfile, pidfile)
+')
next reply other threads:[~2014-08-07 12:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 12:30 Sven Vermeulen [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-08 8:50 [gentoo-commits] proj/hardened-refpolicy:testing commit in: policy/modules/kernel/ Sven Vermeulen
2014-08-08 8:50 Sven Vermeulen
2014-08-08 8:48 [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen
2014-08-08 8:50 ` [gentoo-commits] proj/hardened-refpolicy:testing " Sven Vermeulen
2014-08-07 12:41 Sven Vermeulen
2014-08-07 12:41 Sven Vermeulen
2014-08-07 9:41 [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen
2014-08-08 8:50 ` [gentoo-commits] proj/hardened-refpolicy:testing " Sven Vermeulen
2014-08-06 18:13 Sven Vermeulen
2014-08-06 18:13 Sven Vermeulen
2014-08-06 9:06 Sven Vermeulen
2014-08-06 8:59 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=1407414491.5fd609058ca8eec44bac6baf0a510511a79c6bce.swift@gentoo \
--to=swift@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