diff for duplicates of <1520436517.5558.2.camel@HansenPartnership.com> diff --git a/a/content_digest b/N1/content_digest index a19d1d0..4efb527 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,7 +3,7 @@ "ref\01520428682.10396.445.camel@linux.vnet.ibm.com\0" "From\0James Bottomley <James.Bottomley@hansenpartnership.com>\0" "Subject\0Re: [PATCH 0/9] KEYS: Blacklisting & UEFI database load\0" - "Date\0Wed, 07 Mar 2018 15:28:37 +0000\0" + "Date\0Wed, 07 Mar 2018 07:28:37 -0800\0" "To\0Mimi Zohar <zohar@linux.vnet.ibm.com>" Jiri Slaby <jslaby@suse.cz> David Howells <dhowells@redhat.com> @@ -39,4 +39,4 @@ "\n" James -9a5b24810c93a93779bc5d24b85fc933073748f417c200d807f05135434b9107 +517fc73b82535e634209dc7883d7fcb8eb8d25830f7566d00dd2ba7b78215b6e
diff --git a/a/1.txt b/N2/1.txt index e676d5e..833140c 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -6,7 +6,7 @@ On Wed, 2018-03-07 at 08:18 -0500, Mimi Zohar wrote: > > to resend the PR to have this merged? [...] > Just because I trust the platform keys prior to booting the kernel, -> doesn't mean that I *want* to trust those keys once booted. There +> doesn't mean that I *want* to trust those keys once booted. ?There > are, however, places where we need access to those keys to verify a > signature (eg. kexec kernel image). @@ -16,9 +16,14 @@ back > Nayna Jain's "certs: define a trusted platform keyring" patch set > introduces a new, separate keyring for these platform keys. -Perhaps, to break the deadlock, we should ask Jiří what the reason is -the distros want these keys to be trusted. Apart from the Microsoft -key, it will also give you an OEM key in your trusted keyring. Is it +Perhaps, to break the deadlock, we should ask Ji?? what the reason is +the distros want these keys to be trusted. ?Apart from the Microsoft +key, it will also give you an OEM key in your trusted keyring. ?Is it something to do with OEM supplied modules? James + +-- +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/N2/content_digest index a19d1d0..c1a012f 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,17 +1,10 @@ "ref\0147931984418.16460.6639993676886095760.stgit@warthog.procyon.org.uk\0" "ref\06eabbb43-295e-9ba0-c0d9-120f48aa0e1d@suse.cz\0" "ref\01520428682.10396.445.camel@linux.vnet.ibm.com\0" - "From\0James Bottomley <James.Bottomley@hansenpartnership.com>\0" - "Subject\0Re: [PATCH 0/9] KEYS: Blacklisting & UEFI database load\0" - "Date\0Wed, 07 Mar 2018 15:28:37 +0000\0" - "To\0Mimi Zohar <zohar@linux.vnet.ibm.com>" - Jiri Slaby <jslaby@suse.cz> - David Howells <dhowells@redhat.com> - " keyrings@vger.kernel.org\0" - "Cc\0matthew.garrett@nebula.com" - linux-security-module@vger.kernel.org - linux-efi@vger.kernel.org - " linux-kernel@vger.kernel.org\0" + "From\0James.Bottomley@hansenpartnership.com (James Bottomley)\0" + "Subject\0[PATCH 0/9] KEYS: Blacklisting & UEFI database load\0" + "Date\0Wed, 07 Mar 2018 07:28:37 -0800\0" + "To\0linux-security-module@vger.kernel.org\0" "\00:1\0" "b\0" "On Wed, 2018-03-07 at 08:18 -0500, Mimi Zohar wrote:\n" @@ -22,7 +15,7 @@ "> > to resend the PR to have this merged?\n" "[...]\n" "> Just because I trust the platform keys prior to booting the kernel,\n" - "> doesn't mean that I *want* to trust those keys once booted. \302\240There\n" + "> doesn't mean that I *want* to trust those keys once booted. ?There\n" "> are, however, places where we need access to those keys to verify a\n" "> signature (eg. kexec kernel image).\n" "\n" @@ -32,11 +25,16 @@ "> Nayna Jain's \"certs: define a trusted platform keyring\" patch set\n" "> introduces a new, separate keyring for these platform keys.\n" "\n" - "Perhaps, to break the deadlock, we should ask Ji\305\231\303\255 what the reason is\n" - "the distros want these keys to be trusted. \302\240Apart from the Microsoft\n" - "key, it will also give you an OEM key in your trusted keyring. \302\240Is it\n" + "Perhaps, to break the deadlock, we should ask Ji?? what the reason is\n" + "the distros want these keys to be trusted. ?Apart from the Microsoft\n" + "key, it will also give you an OEM key in your trusted keyring. ?Is it\n" "something to do with OEM supplied modules?\n" "\n" - James + "James\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 -9a5b24810c93a93779bc5d24b85fc933073748f417c200d807f05135434b9107 +ee6d08952bb85e836ece924f8e114f27cb1ba73a7076702d74d78f59f42e8cb5
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.