diff for duplicates of <1509027463.5886.26.camel@linux.vnet.ibm.com> diff --git a/a/1.txt b/N1/1.txt index 7c95aa0..1634384 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -17,9 +17,9 @@ On Thu, 2017-10-26 at 15:42 +0800, joeyli wrote: > > leaves out testing to see if the integrity subsystem is enabled. > > > > Commit 503ceaef8e2e "ima: define a set of appraisal rules requiring -> > file signatures" was upstreamed. An additional patch could force +> > file signatures" was upstreamed. ?An additional patch could force > > these rules to be added to the custom policy, if lockdown is enabled. -> > This and other patches in this series could then check to see if +> > ?This and other patches in this series could then check to see if > > is_ima_appraise_enabled() is true. > > > > Mimi @@ -28,14 +28,14 @@ On Thu, 2017-10-26 at 15:42 +0800, joeyli wrote: > I have updated the patch title and description, and I also added > is_ima_appraise_enabled() as the following. Is it good to you? -Yes, that works. Thanks! Remember is_ima_appraise_enabled() is +Yes, that works. ?Thanks! ?Remember is_ima_appraise_enabled() is dependent on the "ima: require secure_boot rules in lockdown mode" -patch - http://kernsec.org/pipermail/linux-security-module-archive/201 +patch -?http://kernsec.org/pipermail/linux-security-module-archive/201 7-October/003910.html. The IMA "secure_boot" policy can be specified on the boot command line -as ima_policy="secure_boot". It requires kernel modules, firmware, -kexec kernel image and the IMA custom policy to be signed. In +as ima_policy="secure_boot". ?It requires kernel modules, firmware, +kexec kernel image and the IMA custom policy to be signed. ?In lockdown mode, these rules are enabled by default and added to the custom policy. @@ -49,3 +49,8 @@ security_kernel_post_read_file() hooks, which call ima_read_file() and ima_post_read_file() respectively. Mimi + +-- +To unsubscribe from this list: send the line "unsubscribe linux-security-module" in +the body of a message to majordomo at vger.kernel.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 3eeb6ae..9c9f4a3 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,18 +2,10 @@ "ref\0150842468754.7923.10037578333644594134.stgit@warthog.procyon.org.uk\0" "ref\01508774083.3639.124.camel@linux.vnet.ibm.com\0" "ref\020171026074243.GM8550@linux-l9pv.suse\0" - "From\0Mimi Zohar <zohar@linux.vnet.ibm.com>\0" - "Subject\0Re: [PATCH 07/27] kexec_file: Disable at runtime if securelevel has been set\0" + "From\0zohar@linux.vnet.ibm.com (Mimi Zohar)\0" + "Subject\0[PATCH 07/27] kexec_file: Disable at runtime if securelevel has been set\0" "Date\0Thu, 26 Oct 2017 10:17:43 -0400\0" - "To\0joeyli <jlee@suse.com>\0" - "Cc\0David Howells <dhowells@redhat.com>" - linux-security-module@vger.kernel.org - gnomes@lxorguk.ukuu.org.uk - linux-efi@vger.kernel.org - matthew.garrett@nebula.com - gregkh@linuxfoundation.org - linux-kernel@vger.kernel.org - " jforbes@redhat.com\0" + "To\0linux-security-module@vger.kernel.org\0" "\00:1\0" "b\0" "On Thu, 2017-10-26 at 15:42 +0800, joeyli wrote:\n" @@ -35,9 +27,9 @@ "> > leaves out testing to see if the integrity subsystem is enabled.\n" "> > \n" "> > Commit 503ceaef8e2e \"ima: define a set of appraisal rules requiring\n" - "> > file signatures\" was upstreamed. \302\240An additional patch could force\n" + "> > file signatures\" was upstreamed. ?An additional patch could force\n" "> > these rules to be added to the custom policy, if lockdown is enabled.\n" - "> > \302\240This and other patches in this series could then check to see if\n" + "> > ?This and other patches in this series could then check to see if\n" "> > is_ima_appraise_enabled() is true.\n" "> > \n" "> > Mimi\n" @@ -46,14 +38,14 @@ "> I have updated the patch title and description, and I also added\n" "> is_ima_appraise_enabled() as the following. Is it good to you?\n" "\n" - "Yes, that works. \302\240Thanks! \302\240Remember is_ima_appraise_enabled() is\n" + "Yes, that works. ?Thanks! ?Remember is_ima_appraise_enabled() is\n" "dependent on the \"ima: require secure_boot rules in lockdown mode\"\n" - "patch -\302\240http://kernsec.org/pipermail/linux-security-module-archive/201\n" + "patch -?http://kernsec.org/pipermail/linux-security-module-archive/201\n" "7-October/003910.html.\n" "\n" "The IMA \"secure_boot\" policy can be specified on the boot command line\n" - "as ima_policy=\"secure_boot\". \302\240It requires kernel modules, firmware,\n" - "kexec kernel image and the IMA custom policy to be signed. \302\240In\n" + "as ima_policy=\"secure_boot\". ?It requires kernel modules, firmware,\n" + "kexec kernel image and the IMA custom policy to be signed. ?In\n" "lockdown mode, these rules are enabled by default and added to the\n" "custom policy.\n" "\n" @@ -66,6 +58,11 @@ "security_kernel_post_read_file() hooks, which call ima_read_file() and\n" "ima_post_read_file() respectively.\n" "\n" - Mimi + "Mimi\n" + "\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe linux-security-module\" in\n" + "the body of a message to majordomo at vger.kernel.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -e5a2456c1210cd576922a3882ce548e20e9481915e555095757ce1361577655b +1f97c409235e3792c075e22568ca96d3b9c49e3382f5074a0c7d8262a82ec1aa
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.