diff for duplicates of <1533297482.4337.373.camel@linux.ibm.com> diff --git a/a/1.txt b/N1/1.txt index 9499929..22f75cd 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,9 +1,9 @@ On Thu, 2018-08-02 at 17:14 +0100, David Howells wrote: > Udit Agarwal <udit.agarwal@nxp.com> wrote: > -> > +===== +> > +========== > > +Secure Key -> > +===== +> > +========== > > + > > +Secure key is the new type added to kernel key ring service. > > +Secure key is a symmetric type key of minimum length 32 bytes @@ -18,13 +18,13 @@ On Thu, 2018-08-02 at 17:14 +0100, David Howells wrote: > > Can you convert this into a "symmetric" type and make the backend pluggable? -TPM 1.2 didn't support symmetric keys. For this reason, the TPM +TPM 1.2 didn't support symmetric keys. For this reason, the TPM "unseals" the random number, used as a symmetric key, and returns the "unsealed" data to the kernel. Does anyone know if CAAM or TPM 2.0 have support for symmetric keys? - If they have symmetric key support, there would be no need for the -symmetric key ever to leave the device in the clear. The device would + If they have symmetric key support, there would be no need for the +symmetric key ever to leave the device in the clear. The device would unseal/decrypt data, such as an encrypted key. The "symmetric" key type would be a generic interface for different diff --git a/a/content_digest b/N1/content_digest index 498d7e4..b353131 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,7 +2,7 @@ "ref\08060.1533226481@warthog.procyon.org.uk\0" "From\0Mimi Zohar <zohar@linux.ibm.com>\0" "Subject\0Re: [PATCH v2 1/2] security/keys/secure_key: Adds the secure key support based on CAAM.\0" - "Date\0Fri, 03 Aug 2018 11:58:02 +0000\0" + "Date\0Fri, 03 Aug 2018 07:58:02 -0400\0" "To\0David Howells <dhowells@redhat.com>" " Udit Agarwal <udit.agarwal@nxp.com>\0" "Cc\0zohar@linux.vnet.ibm.com" @@ -22,9 +22,9 @@ "On Thu, 2018-08-02 at 17:14 +0100, David Howells wrote:\n" "> Udit Agarwal <udit.agarwal@nxp.com> wrote:\n" "> \n" - "> > +=====\n" + "> > +==========\n" "> > +Secure Key\n" - "> > +=====\n" + "> > +==========\n" "> > +\n" "> > +Secure key is the new type added to kernel key ring service.\n" "> > +Secure key is a symmetric type key of minimum length 32 bytes\n" @@ -39,13 +39,13 @@ "> \n" "> Can you convert this into a \"symmetric\" type and make the backend pluggable?\n" "\n" - "TPM 1.2 didn't support symmetric keys. \302\240For this reason, the TPM\n" + "TPM 1.2 didn't support symmetric keys. For this reason, the TPM\n" "\"unseals\" the random number, used as a symmetric key, and returns the\n" "\"unsealed\" data to the kernel.\n" "\n" "Does anyone know if CAAM or TPM 2.0 have support for symmetric keys?\n" - "\302\240If they have symmetric key support, there would be no need for the\n" - "symmetric key ever to leave the device in the clear. \302\240The device would\n" + " If they have symmetric key support, there would be no need for the\n" + "symmetric key ever to leave the device in the clear. The device would\n" "unseal/decrypt data, such as an encrypted key.\n" "\n" "The \"symmetric\" key type would be a generic interface for different\n" @@ -53,4 +53,4 @@ "\n" Mimi -f1a10b8b46e0605b04951fb03edd2de9629b3d8172576484d025bb704f5e44fb +8e7df2bd516bdb7771ef01671efb443956aa624c7bff8fe28785ee420668d605
diff --git a/a/1.txt b/N2/1.txt index 9499929..5f09186 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,9 +1,9 @@ On Thu, 2018-08-02 at 17:14 +0100, David Howells wrote: > Udit Agarwal <udit.agarwal@nxp.com> wrote: > -> > +===== +> > +========== > > +Secure Key -> > +===== +> > +========== > > + > > +Secure key is the new type added to kernel key ring service. > > +Secure key is a symmetric type key of minimum length 32 bytes @@ -18,16 +18,21 @@ On Thu, 2018-08-02 at 17:14 +0100, David Howells wrote: > > Can you convert this into a "symmetric" type and make the backend pluggable? -TPM 1.2 didn't support symmetric keys. For this reason, the TPM +TPM 1.2 didn't support symmetric keys. ?For this reason, the TPM "unseals" the random number, used as a symmetric key, and returns the "unsealed" data to the kernel. Does anyone know if CAAM or TPM 2.0 have support for symmetric keys? - If they have symmetric key support, there would be no need for the -symmetric key ever to leave the device in the clear. The device would +?If they have symmetric key support, there would be no need for the +symmetric key ever to leave the device in the clear. ?The device would unseal/decrypt data, such as an encrypted key. The "symmetric" key type would be a generic interface for different devices. 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 498d7e4..dbb0bc8 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,30 +1,17 @@ "ref\020180723111432.26830-1-udit.agarwal@nxp.com\0" "ref\08060.1533226481@warthog.procyon.org.uk\0" - "From\0Mimi Zohar <zohar@linux.ibm.com>\0" - "Subject\0Re: [PATCH v2 1/2] security/keys/secure_key: Adds the secure key support based on CAAM.\0" - "Date\0Fri, 03 Aug 2018 11:58:02 +0000\0" - "To\0David Howells <dhowells@redhat.com>" - " Udit Agarwal <udit.agarwal@nxp.com>\0" - "Cc\0zohar@linux.vnet.ibm.com" - jmorris@namei.org - serge@hallyn.com - denkenz@gmail.com - linux-integrity@vger.kernel.org - keyrings@vger.kernel.org - linux-security-module@vger.kernel.org - linux-kernel@vger.kernel.org - sahil.malhotra@nxp.com - ruchika.gupta@nxp.com - horia.geanta@nxp.com - " aymen.sghaier@nxp.com\0" + "From\0zohar@linux.ibm.com (Mimi Zohar)\0" + "Subject\0[PATCH v2 1/2] security/keys/secure_key: Adds the secure key support based on CAAM.\0" + "Date\0Fri, 03 Aug 2018 07:58:02 -0400\0" + "To\0linux-security-module@vger.kernel.org\0" "\00:1\0" "b\0" "On Thu, 2018-08-02 at 17:14 +0100, David Howells wrote:\n" "> Udit Agarwal <udit.agarwal@nxp.com> wrote:\n" "> \n" - "> > +=====\n" + "> > +==========\n" "> > +Secure Key\n" - "> > +=====\n" + "> > +==========\n" "> > +\n" "> > +Secure key is the new type added to kernel key ring service.\n" "> > +Secure key is a symmetric type key of minimum length 32 bytes\n" @@ -39,18 +26,23 @@ "> \n" "> Can you convert this into a \"symmetric\" type and make the backend pluggable?\n" "\n" - "TPM 1.2 didn't support symmetric keys. \302\240For this reason, the TPM\n" + "TPM 1.2 didn't support symmetric keys. ?For this reason, the TPM\n" "\"unseals\" the random number, used as a symmetric key, and returns the\n" "\"unsealed\" data to the kernel.\n" "\n" "Does anyone know if CAAM or TPM 2.0 have support for symmetric keys?\n" - "\302\240If they have symmetric key support, there would be no need for the\n" - "symmetric key ever to leave the device in the clear. \302\240The device would\n" + "?If they have symmetric key support, there would be no need for the\n" + "symmetric key ever to leave the device in the clear. ?The device would\n" "unseal/decrypt data, such as an encrypted key.\n" "\n" "The \"symmetric\" key type would be a generic interface for different\n" "devices.\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 -f1a10b8b46e0605b04951fb03edd2de9629b3d8172576484d025bb704f5e44fb +bf1701cedd0884969e1d71dcdba86af98e2cde077ffea263d882ca542a6dc81e
diff --git a/a/1.txt b/N3/1.txt index 9499929..811cd5f 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -1,9 +1,9 @@ On Thu, 2018-08-02 at 17:14 +0100, David Howells wrote: > Udit Agarwal <udit.agarwal@nxp.com> wrote: > -> > +===== +> > +========== > > +Secure Key -> > +===== +> > +========== > > + > > +Secure key is the new type added to kernel key ring service. > > +Secure key is a symmetric type key of minimum length 32 bytes diff --git a/a/content_digest b/N3/content_digest index 498d7e4..562376c 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -2,7 +2,7 @@ "ref\08060.1533226481@warthog.procyon.org.uk\0" "From\0Mimi Zohar <zohar@linux.ibm.com>\0" "Subject\0Re: [PATCH v2 1/2] security/keys/secure_key: Adds the secure key support based on CAAM.\0" - "Date\0Fri, 03 Aug 2018 11:58:02 +0000\0" + "Date\0Fri, 03 Aug 2018 07:58:02 -0400\0" "To\0David Howells <dhowells@redhat.com>" " Udit Agarwal <udit.agarwal@nxp.com>\0" "Cc\0zohar@linux.vnet.ibm.com" @@ -22,9 +22,9 @@ "On Thu, 2018-08-02 at 17:14 +0100, David Howells wrote:\n" "> Udit Agarwal <udit.agarwal@nxp.com> wrote:\n" "> \n" - "> > +=====\n" + "> > +==========\n" "> > +Secure Key\n" - "> > +=====\n" + "> > +==========\n" "> > +\n" "> > +Secure key is the new type added to kernel key ring service.\n" "> > +Secure key is a symmetric type key of minimum length 32 bytes\n" @@ -53,4 +53,4 @@ "\n" Mimi -f1a10b8b46e0605b04951fb03edd2de9629b3d8172576484d025bb704f5e44fb +c20b6f5ce26d74d61daa6151f910c44190e0be392d6accdf4c33dd38bd79e06e
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.