From: "Sven Vermeulen" <swift@gentoo.org> To: gentoo-commits@lists.gentoo.org Subject: [gentoo-commits] proj/hardened-refpolicy:next commit in: policy/modules/kernel/ Date: Thu, 5 Mar 2015 13:15:32 +0000 (UTC) [thread overview] Message-ID: <1425497583.eda29c4a002eff58dcd3c7466f147920e530bf1b.swift@gentoo> (raw) commit: eda29c4a002eff58dcd3c7466f147920e530bf1b Author: Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be> AuthorDate: Wed Mar 4 19:33:03 2015 +0000 Commit: Sven Vermeulen <swift <AT> gentoo <DOT> org> CommitDate: Wed Mar 4 19:33:03 2015 +0000 URL: https://gitweb.gentoo.org/proj/hardened-refpolicy.git/commit/?id=eda29c4a Revert change to fix build Recently I introduced support for kdevtmpfs managing all device nodes but this triggers an issue. That method requires the storage module to be in the base, which pulls in an entire set of other issues, or that the attributes used by the storage module are moved towards the devices module (or another module inside base) which also has quite some work on it. Going to check with other team first. policy/modules/kernel/kernel.te | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/policy/modules/kernel/kernel.te b/policy/modules/kernel/kernel.te index a48cf63..3a045e0 100644 --- a/policy/modules/kernel/kernel.te +++ b/policy/modules/kernel/kernel.te @@ -439,5 +439,6 @@ ifdef(`distro_gentoo',` # To support kdevtmpfs properly (its purpose is to manage the /dev tmpfs so grant it these rights) # See also bug 535992 - dev_manage_all_dev_nodes(kernel_t) + #dev_manage_all_dev_nodes(kernel_t) + dev_setattr_generic_chr_files(kernel_t) ')
WARNING: multiple messages have this Message-ID (diff)
From: "Sven Vermeulen" <swift@gentoo.org> To: gentoo-commits@lists.gentoo.org Subject: [gentoo-commits] proj/hardened-refpolicy:master commit in: policy/modules/kernel/ Date: Wed, 4 Mar 2015 19:34:21 +0000 (UTC) [thread overview] Message-ID: <1425497583.eda29c4a002eff58dcd3c7466f147920e530bf1b.swift@gentoo> (raw) Message-ID: <20150304193421.qWlZU6fa3enukDaojp5A38SiBLJmqmLtfb2E1eipjuk@z> (raw) commit: eda29c4a002eff58dcd3c7466f147920e530bf1b Author: Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be> AuthorDate: Wed Mar 4 19:33:03 2015 +0000 Commit: Sven Vermeulen <swift <AT> gentoo <DOT> org> CommitDate: Wed Mar 4 19:33:03 2015 +0000 URL: http://sources.gentoo.org/gitweb/?p=proj/hardened-refpolicy.git;a=commit;h=eda29c4a Revert change to fix build Recently I introduced support for kdevtmpfs managing all device nodes but this triggers an issue. That method requires the storage module to be in the base, which pulls in an entire set of other issues, or that the attributes used by the storage module are moved towards the devices module (or another module inside base) which also has quite some work on it. Going to check with other team first. policy/modules/kernel/kernel.te | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/policy/modules/kernel/kernel.te b/policy/modules/kernel/kernel.te index a48cf63..3a045e0 100644 --- a/policy/modules/kernel/kernel.te +++ b/policy/modules/kernel/kernel.te @@ -439,5 +439,6 @@ ifdef(`distro_gentoo',` # To support kdevtmpfs properly (its purpose is to manage the /dev tmpfs so grant it these rights) # See also bug 535992 - dev_manage_all_dev_nodes(kernel_t) + #dev_manage_all_dev_nodes(kernel_t) + dev_setattr_generic_chr_files(kernel_t) ')
next reply other threads:[~2015-03-05 13:15 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-05 13:15 Sven Vermeulen [this message] 2015-03-04 19:34 ` [gentoo-commits] proj/hardened-refpolicy:master commit in: policy/modules/kernel/ Sven Vermeulen -- strict thread matches above, loose matches on Subject: below -- 2017-09-10 14:03 [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman 2017-03-30 17:06 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman 2017-03-30 17:09 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman 2017-02-27 11:40 Jason Zaman 2017-02-17 8:44 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman 2017-02-17 8:50 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman 2017-01-01 16:44 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman 2017-01-01 16:47 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman 2017-01-01 16:37 Jason Zaman 2017-01-01 16:36 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman 2017-01-01 16:37 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman 2017-01-01 16:36 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman 2017-01-01 16:37 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman 2016-12-08 4:47 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman 2016-12-08 5:03 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman 2016-12-08 4:47 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman 2016-12-08 5:03 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman 2016-08-13 18:35 Jason Zaman 2016-08-13 18:35 Jason Zaman 2015-12-17 18:49 Jason Zaman 2015-12-17 16:10 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman 2015-12-17 18:49 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman 2015-12-17 16:10 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman 2015-12-17 18:49 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman 2015-10-14 18:36 Jason Zaman 2015-10-11 10:48 Jason Zaman 2015-10-11 10:48 Jason Zaman 2015-09-20 7:00 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman 2015-10-11 10:48 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman 2015-08-27 19:11 Jason Zaman 2015-08-27 19:11 Jason Zaman 2015-08-27 18:58 [gentoo-commits] proj/hardened-refpolicy:master " Jason Zaman 2015-08-26 6:46 ` [gentoo-commits] proj/hardened-refpolicy:next " Jason Zaman 2015-07-13 21:45 Jason Zaman 2015-06-07 9:31 Sven Vermeulen 2015-03-04 15:35 [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen 2015-03-04 17:03 ` [gentoo-commits] proj/hardened-refpolicy:next " Sven Vermeulen 2015-03-04 15:20 [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen 2015-03-04 17:03 ` [gentoo-commits] proj/hardened-refpolicy:next " Sven Vermeulen 2015-02-24 17:11 Jason Zaman 2015-02-24 17:11 Jason Zaman 2015-01-25 13:46 Sven Vermeulen 2015-01-25 13:45 [gentoo-commits] proj/hardened-refpolicy:master " Sven Vermeulen 2015-01-25 13:46 ` [gentoo-commits] proj/hardened-refpolicy:next " Sven Vermeulen 2015-01-24 19:08 Sven Vermeulen 2015-01-24 17:12 Sven Vermeulen 2014-11-28 10:04 Sven Vermeulen 2014-11-22 18:24 [gentoo-commits] proj/hardened-refpolicy:master " 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-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-28 10:04 ` [gentoo-commits] proj/hardened-refpolicy:next " 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=1425497583.eda29c4a002eff58dcd3c7466f147920e530bf1b.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: linkBe 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