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:41:50 +0000 (UTC) [thread overview]
Message-ID: <1407404865.9c22729b7ff8064c52b59c5dbe78dfd632a1bf87.swift@gentoo> (raw)
commit: 9c22729b7ff8064c52b59c5dbe78dfd632a1bf87
Author: Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be>
AuthorDate: Thu Aug 7 09:39:37 2014 +0000
Commit: Sven Vermeulen <swift <AT> gentoo <DOT> org>
CommitDate: Thu Aug 7 09:47:45 2014 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-refpolicy.git;a=commit;h=9c22729b
Add files_relabel_non_security_file_type
This interface allows for relabel operations against all resources with
a type associated with the non_security_file_type attribute.
---
policy/modules/kernel/files.if | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
diff --git a/policy/modules/kernel/files.if b/policy/modules/kernel/files.if
index 5d53aa4..105c7c2 100644
--- a/policy/modules/kernel/files.if
+++ b/policy/modules/kernel/files.if
@@ -6731,6 +6731,35 @@ interface(`files_read_etc_runtime',`
########################################
## <summary>
+## Relabel all non-security related
+## files.
+## </summary>
+## <param name="domain">
+## <summary>
+## Domain allowed access.
+## </summary>
+## </param>
+## <rolecap/>
+#
+interface(`files_relabel_non_security_file_type',`
+ gen_require(`
+ attribute non_security_file_type;
+ ')
+
+ allow $1 non_security_file_type:dir list_dir_perms;
+ relabel_dirs_pattern($1, non_security_file_type, non_security_file_type)
+ relabel_files_pattern($1, non_security_file_type, non_security_file_type)
+ relabel_lnk_files_pattern($1, non_security_file_type, non_security_file_type)
+ relabel_fifo_files_pattern($1, non_security_file_type, non_security_file_type)
+ relabel_sock_files_pattern($1, non_security_file_type, non_security_file_type)
+ # this is only relabelfrom since there should be no
+ # device nodes with file types.
+ relabelfrom_blk_files_pattern($1, non_security_file_type, non_security_file_type)
+ relabelfrom_chr_files_pattern($1, non_security_file_type, non_security_file_type)
+')
+
+########################################
+## <summary>
## Manage non-security related resources.
## </summary>
## <param name="domain">
next reply other threads:[~2014-08-07 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 12:41 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:30 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=1407404865.9c22729b7ff8064c52b59c5dbe78dfd632a1bf87.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