diff for duplicates of <1532439290.3277.52.camel@linux.ibm.com> diff --git a/a/1.txt b/N1/1.txt index 2d25d72..2c65463 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,13 +1,13 @@ On Tue, 2018-07-24 at 12:31 +0000, Udit Agarwal wrote: > Yes the secure keys and CAAM are correlated. Secure keys depends on -> NXP CAAM crypto HW accelerator. Secure key is a random data of +> NXP CAAM crypto HW accelerator. Secure key is a random data of > length X (passed using keyctl command) & derived using CAAM. Blob of > this data is also created using CAAM. Only blob is visible to user > space. -The term "secure keys" is really generic. What makes the "secure -keys" secure? We introduced "trusted keys", because TPM 1.2 didn't -support symmetric keys. We shouldn't just duplicate "trusted keys" +The term "secure keys" is really generic. What makes the "secure +keys" secure? We introduced "trusted keys", because TPM 1.2 didn't +support symmetric keys. We shouldn't just duplicate "trusted keys" for different HW, but improve upon it (eg. symmetric keys never leave the device). diff --git a/a/content_digest b/N1/content_digest index 9b00321..620054a 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,7 +3,7 @@ "ref\0AM5PR0401MB2660B8C1DD5ED9989239EF009E550@AM5PR0401MB2660.eurprd04.prod.outlook.com\0" "From\0Mimi Zohar <zohar@linux.ibm.com>\0" "Subject\0Re: [PATCH 1/2] security/keys/secure_key: Adds the secure key support based on CAAM.\0" - "Date\0Tue, 24 Jul 2018 13:34:50 +0000\0" + "Date\0Tue, 24 Jul 2018 09:34:50 -0400\0" "To\0Udit Agarwal <udit.agarwal@nxp.com>" dhowells@redhat.com <dhowells@redhat.com> zohar@linux.vnet.ibm.com <zohar@linux.vnet.ibm.com> @@ -21,14 +21,14 @@ "b\0" "On Tue, 2018-07-24 at 12:31 +0000, Udit Agarwal wrote:\n" "> Yes the secure keys and CAAM are correlated. Secure keys depends on\n" - "> NXP CAAM crypto HW accelerator. \302\240Secure key is a random data of\n" + "> NXP CAAM crypto HW accelerator. Secure key is a random data of\n" "> length X (passed using keyctl command) & derived using CAAM. Blob of\n" "> this data is also created using CAAM. Only blob is visible to user\n" "> space.\n" "\n" - "The term \"secure keys\" is really generic. \302\240What makes the \"secure\n" - "keys\" secure? \302\240We introduced \"trusted keys\", because TPM 1.2 didn't\n" - "support symmetric keys. \302\240We shouldn't just duplicate \"trusted keys\"\n" + "The term \"secure keys\" is really generic. What makes the \"secure\n" + "keys\" secure? We introduced \"trusted keys\", because TPM 1.2 didn't\n" + "support symmetric keys. We shouldn't just duplicate \"trusted keys\"\n" "for different HW, but improve upon it (eg. symmetric keys never leave\n" "the device).\n" "\n" @@ -37,4 +37,4 @@ "\n" Mimi -cb4036ce1cb1cfbdf5fa1d1495654df6205c1cea54028af4358f934fd0c5d008 +d74b7561f3d53c3a822854cbfd30777605c07e9fceb67079a938dd552fd392f5
diff --git a/a/1.txt b/N2/1.txt index 2d25d72..f849d9d 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,13 +1,13 @@ On Tue, 2018-07-24 at 12:31 +0000, Udit Agarwal wrote: > Yes the secure keys and CAAM are correlated. Secure keys depends on -> NXP CAAM crypto HW accelerator. Secure key is a random data of +> NXP CAAM crypto HW accelerator. ?Secure key is a random data of > length X (passed using keyctl command) & derived using CAAM. Blob of > this data is also created using CAAM. Only blob is visible to user > space. -The term "secure keys" is really generic. What makes the "secure -keys" secure? We introduced "trusted keys", because TPM 1.2 didn't -support symmetric keys. We shouldn't just duplicate "trusted keys" +The term "secure keys" is really generic. ?What makes the "secure +keys" secure? ?We introduced "trusted keys", because TPM 1.2 didn't +support symmetric keys. ?We shouldn't just duplicate "trusted keys" for different HW, but improve upon it (eg. symmetric keys never leave the device). @@ -15,3 +15,8 @@ The new key type should define generic methods, which are implemented for NXP CAAM rypto HW accelerator as an example. 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/N2/content_digest index 9b00321..97871aa 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,40 +1,33 @@ "ref\020180720054656.29143-1-udit.agarwal@nxp.com\0" "ref\01532302451.6206.22.camel@linux.ibm.com\0" "ref\0AM5PR0401MB2660B8C1DD5ED9989239EF009E550@AM5PR0401MB2660.eurprd04.prod.outlook.com\0" - "From\0Mimi Zohar <zohar@linux.ibm.com>\0" - "Subject\0Re: [PATCH 1/2] security/keys/secure_key: Adds the secure key support based on CAAM.\0" - "Date\0Tue, 24 Jul 2018 13:34:50 +0000\0" - "To\0Udit Agarwal <udit.agarwal@nxp.com>" - dhowells@redhat.com <dhowells@redhat.com> - zohar@linux.vnet.ibm.com <zohar@linux.vnet.ibm.com> - jmorris@namei.org <jmorris@namei.org> - serge@hallyn.com <serge@hallyn.com> - linux-integrity@vger.kernel.org <linux-integrity@vger.kernel.org> - keyrings@vger.kernel.org <keyrings@vger.kernel.org> - linux-security-module@vger.kernel.org <linux-security-module@vger.kernel.org> - " linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>\0" - "Cc\0Sahil Malhotra <sahil.malhotra@nxp.com>" - Ruchika Gupta <ruchika.gupta@nxp.com> - Horia Geanta <horia.geanta@nxp.com> - " Aymen Sghaier <aymen.sghaier@nxp.com>\0" + "From\0zohar@linux.ibm.com (Mimi Zohar)\0" + "Subject\0[PATCH 1/2] security/keys/secure_key: Adds the secure key support based on CAAM.\0" + "Date\0Tue, 24 Jul 2018 09:34:50 -0400\0" + "To\0linux-security-module@vger.kernel.org\0" "\00:1\0" "b\0" "On Tue, 2018-07-24 at 12:31 +0000, Udit Agarwal wrote:\n" "> Yes the secure keys and CAAM are correlated. Secure keys depends on\n" - "> NXP CAAM crypto HW accelerator. \302\240Secure key is a random data of\n" + "> NXP CAAM crypto HW accelerator. ?Secure key is a random data of\n" "> length X (passed using keyctl command) & derived using CAAM. Blob of\n" "> this data is also created using CAAM. Only blob is visible to user\n" "> space.\n" "\n" - "The term \"secure keys\" is really generic. \302\240What makes the \"secure\n" - "keys\" secure? \302\240We introduced \"trusted keys\", because TPM 1.2 didn't\n" - "support symmetric keys. \302\240We shouldn't just duplicate \"trusted keys\"\n" + "The term \"secure keys\" is really generic. ?What makes the \"secure\n" + "keys\" secure? ?We introduced \"trusted keys\", because TPM 1.2 didn't\n" + "support symmetric keys. ?We shouldn't just duplicate \"trusted keys\"\n" "for different HW, but improve upon it (eg. symmetric keys never leave\n" "the device).\n" "\n" "The new key type should define generic methods, which are implemented\n" "for NXP CAAM rypto HW accelerator as an example.\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 -cb4036ce1cb1cfbdf5fa1d1495654df6205c1cea54028af4358f934fd0c5d008 +d4bbb4a7a978e869e02380efc81d0ade21056002bcb3aa6220177500d9a208a4
diff --git a/a/content_digest b/N3/content_digest index 9b00321..75bf0ff 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -3,7 +3,7 @@ "ref\0AM5PR0401MB2660B8C1DD5ED9989239EF009E550@AM5PR0401MB2660.eurprd04.prod.outlook.com\0" "From\0Mimi Zohar <zohar@linux.ibm.com>\0" "Subject\0Re: [PATCH 1/2] security/keys/secure_key: Adds the secure key support based on CAAM.\0" - "Date\0Tue, 24 Jul 2018 13:34:50 +0000\0" + "Date\0Tue, 24 Jul 2018 09:34:50 -0400\0" "To\0Udit Agarwal <udit.agarwal@nxp.com>" dhowells@redhat.com <dhowells@redhat.com> zohar@linux.vnet.ibm.com <zohar@linux.vnet.ibm.com> @@ -37,4 +37,4 @@ "\n" Mimi -cb4036ce1cb1cfbdf5fa1d1495654df6205c1cea54028af4358f934fd0c5d008 +c8d5042deff5a319acf58284f62b79558523477e96d4b436026a9f6bb197a647
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.