diff for duplicates of <1509385178.3583.159.camel@linux.vnet.ibm.com> diff --git a/a/1.txt b/N1/1.txt index 6663df6..4d5c3e8 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -3,21 +3,21 @@ On Mon, 2017-10-30 at 17:05 +0000, David Howells wrote: > > > > Did you mean "true" rather than "TRUE"? > > -> > Yes, of course. Commit 9f4b6a254d7a "ima: Fix bool -> > initialization/comparison" already addresses it. Please remove it +> > Yes, of course. ?Commit 9f4b6a254d7a "ima: Fix bool +> > initialization/comparison" already addresses it. ?Please remove it > > from this patch. > > Is that with James? I don't seem to have a copy, and I don't want to cause a > patch collision. -No, it's staged in my next branch. After the disaster during the last +No, it's staged in my next branch. ?After the disaster during the last open window due to a linux-integrity patch, Linus requested linux- -integrity be pulled independently of the security pull request. We'll +integrity be pulled independently of the security pull request. ?We'll see how that goes during the next open window. James is staging the subsystem patches independently of each other, in case of a similar problem, so that they can be pulled separately. - There's a new "next-general" branch. +?There's a new "next-general" branch. > > > I guess also that oopsing is okay if the allocation fails. We've run out of > > > memory during early boot, after all. @@ -28,7 +28,7 @@ case of a similar problem, so that they can be pulled separately. > Sorry - I overlooked the fact that the variable is not used if it's not zero. > > > If it fails, there needs to be some indication of the failure, which there -> > currently isn't. Perhaps also prevent loading a custom policy. +> > currently isn't. ?Perhaps also prevent loading a custom policy. > > Does it need to panic (probably fine as a small memory alloc failed)? If it > doesn't set this policy what's the effect on things using @@ -41,3 +41,8 @@ secure boot rules, files that should be appraised (eg. kernel modules, kexec'ed kernel image, firmware) won't be. 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 6a20a59..c204536 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,13 +2,10 @@ "ref\01508774387.3639.128.camel@linux.vnet.ibm.com\0" "ref\0750.1509378910@warthog.procyon.org.uk\0" "ref\03691.1509383138@warthog.procyon.org.uk\0" - "From\0Mimi Zohar <zohar@linux.vnet.ibm.com>\0" - "Subject\0Re: [RFC PATCH] ima: require secure_boot rules in lockdown mode\0" + "From\0zohar@linux.vnet.ibm.com (Mimi Zohar)\0" + "Subject\0[RFC PATCH] ima: require secure_boot rules in lockdown mode\0" "Date\0Mon, 30 Oct 2017 13:39:38 -0400\0" - "To\0David Howells <dhowells@redhat.com>\0" - "Cc\0linux-integrity <linux-integrity@vger.kernel.org>" - Matthew Garrett <mjg59@google.com> - " linux-security-module <linux-security-module@vger.kernel.org>\0" + "To\0linux-security-module@vger.kernel.org\0" "\00:1\0" "b\0" "On Mon, 2017-10-30 at 17:05 +0000, David Howells wrote:\n" @@ -16,21 +13,21 @@ "> \n" "> > > Did you mean \"true\" rather than \"TRUE\"?\n" "> > \n" - "> > Yes, of course. Commit 9f4b6a254d7a \"ima: Fix bool\n" - "> > initialization/comparison\" already addresses it. Please remove it\n" + "> > Yes, of course. ?Commit 9f4b6a254d7a \"ima: Fix bool\n" + "> > initialization/comparison\" already addresses it. ?Please remove it\n" "> > from this patch.\n" "> \n" "> Is that with James? I don't seem to have a copy, and I don't want to cause a\n" "> patch collision.\n" "\n" - "No, it's staged in my next branch. After the disaster during the last\n" + "No, it's staged in my next branch. ?After the disaster during the last\n" "open window due to a linux-integrity patch, Linus requested linux-\n" - "integrity be pulled independently of the security pull request. We'll\n" + "integrity be pulled independently of the security pull request. ?We'll\n" "see how that goes during the next open window.\n" "\n" "James is staging the subsystem patches independently of each other, in\n" "case of a similar problem, so that they can be pulled separately.\n" - " There's a new \"next-general\" branch.\n" + "?There's a new \"next-general\" branch.\n" "\n" "> > > I guess also that oopsing is okay if the allocation fails. We've run out of\n" "> > > memory during early boot, after all.\n" @@ -41,7 +38,7 @@ "> Sorry - I overlooked the fact that the variable is not used if it's not zero.\n" "> \n" "> > If it fails, there needs to be some indication of the failure, which there\n" - "> > currently isn't. Perhaps also prevent loading a custom policy.\n" + "> > currently isn't. ?Perhaps also prevent loading a custom policy.\n" "> \n" "> Does it need to panic (probably fine as a small memory alloc failed)? If it\n" "> doesn't set this policy what's the effect on things using\n" @@ -53,6 +50,11 @@ "secure boot rules, files that should be appraised (eg. kernel modules,\n" "kexec'ed kernel image, firmware) won't be.\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 -544fa545d2a41de8c7cef9912129d6cbe87599bea1beba64bcd162d0ad3f9a38 +7717675133bf129a4e3a7014064ceb702d3298db5f35f649d56f334a94b08881
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.