diff for duplicates of <20171028083446.GG20348@linux-l9pv.suse> diff --git a/a/1.txt b/N1/1.txt index 008c876..f3a7475 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -19,9 +19,9 @@ On Fri, Oct 27, 2017 at 03:32:26PM -0400, Mimi Zohar 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 @@ -30,14 +30,14 @@ On Fri, Oct 27, 2017 at 03:32:26PM -0400, Mimi Zohar 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. > > @@ -51,7 +51,7 @@ On Fri, Oct 27, 2017 at 03:32:26PM -0400, Mimi Zohar wrote: > > ima_post_read_file() respectively. > > Hm, with "lockdown" enabled on the boot command line, I'm now able to -> do the kexec load, but not the unload. :/ After the kexec load with +> do the kexec load, but not the unload. :/ ? After the kexec load with I have tried on Qemu with OVMF, I can load and unload second kernel by kexec tool (on openSUSE is in kexec-tools RPM): @@ -77,4 +77,8 @@ The kernel source is from David's linux-fs git with lockdown-20171026 tag. The kernel is also signed by pesign. Regards -Joey Lee +Joey Lee +-- +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 3462388..6eedd74 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,18 +4,10 @@ "ref\020171026074243.GM8550@linux-l9pv.suse\0" "ref\01509027463.5886.26.camel@linux.vnet.ibm.com\0" "ref\01509132746.3729.9.camel@linux.vnet.ibm.com\0" - "From\0joeyli <jlee@suse.com>\0" - "Subject\0Re: [PATCH 07/27] kexec_file: Disable at runtime if securelevel has been set\0" + "From\0jlee@suse.com (joeyli)\0" + "Subject\0[PATCH 07/27] kexec_file: Disable at runtime if securelevel has been set\0" "Date\0Sat, 28 Oct 2017 16:34:46 +0800\0" - "To\0Mimi Zohar <zohar@linux.vnet.ibm.com>\0" - "Cc\0David Howells <dhowells@redhat.com>" - linux-security-module@vger.kernel.org - gnomes@lxorguk.ukuu.org.uk - linux-efi@vger.kernel.org - gregkh@linuxfoundation.org - linux-kernel@vger.kernel.org - jforbes@redhat.com - " Matthew Garrett <mjg59@google.com>\0" + "To\0linux-security-module@vger.kernel.org\0" "\00:1\0" "b\0" "On Fri, Oct 27, 2017 at 03:32:26PM -0400, Mimi Zohar wrote:\n" @@ -39,9 +31,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" @@ -50,14 +42,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" @@ -71,7 +63,7 @@ "> > ima_post_read_file() respectively.\n" "> \n" "> Hm, with \"lockdown\" enabled on the boot command line, I'm now able to\n" - "> do the kexec load, but not the unload. :/ \302\240 After the kexec load with\n" + "> do the kexec load, but not the unload. :/ ? After the kexec load with\n" "\n" "I have tried on Qemu with OVMF, I can load and unload second kernel by\n" "kexec tool (on openSUSE is in kexec-tools RPM): \n" @@ -97,6 +89,10 @@ "The kernel is also signed by pesign.\n" "\n" "Regards\n" - Joey Lee + "Joey Lee \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 -fef9062558b3c2ee731aaa65ebfe58ddc8c8d23677733f9175a5d0bfda55a04a +be5b02a52acebe707241d3a2837951edb1b46aea6044c1b550cbd67b7b61381d
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.