diff for duplicates of <1532302451.6206.22.camel@linux.ibm.com> diff --git a/a/1.txt b/N1/1.txt index 80d163c..f0cb572 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -6,10 +6,10 @@ On Fri, 2018-07-20 at 11:16 +0530, Udit Agarwal wrote: > will only be able to view the blob of the key. The term "trusted keys" comes from the usage of the Trusted Platform -Module (TPM). The term "trusted" now also refers to keyrings, which +Module (TPM). The term "trusted" now also refers to keyrings, which has nothing to do with a TPM. -What is the correlation between the term "secure keys" and CAAM? Are +What is the correlation between the term "secure keys" and CAAM? Are "secure keys", as defined in this patch, limited to a specific HW crypto device? @@ -40,9 +40,9 @@ Mimi > --- /dev/null > +++ b/Documentation/security/keys/secure-key.rst > @@ -0,0 +1,67 @@ -> +===== +> +========== > +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 @@ -589,8 +589,10 @@ Mimi > + > +void caam_sk_redblob_encap_desc(struct sk_req *skreq, struct sk_desc *skdesc) > +{ -> + struct redblob_encap_desc *red_blob_desc > + &skdesc->dma_u.redblob_encapdesc; -> + struct sk_red_blob_encap *red_blob_req > + &skreq->req_u.sk_red_blob_encap; +> + struct redblob_encap_desc *red_blob_desc = +> + &skdesc->dma_u.redblob_encapdesc; +> + struct sk_red_blob_encap *red_blob_req = +> + &skreq->req_u.sk_red_blob_encap; > + u32 *desc = skreq->hwdesc; > + > + init_job_desc(desc, 0); @@ -618,8 +620,10 @@ Mimi > + */ > +void caam_sk_redblob_decap_desc(struct sk_req *skreq, struct sk_desc *skdesc) > +{ -> + struct redblob_decap_desc *red_blob_desc > + &skdesc->dma_u.redblob_decapdesc; -> + struct sk_red_blob_decap *red_blob_req > + &skreq->req_u.sk_red_blob_decap; +> + struct redblob_decap_desc *red_blob_desc = +> + &skdesc->dma_u.redblob_decapdesc; +> + struct sk_red_blob_decap *red_blob_req = +> + &skreq->req_u.sk_red_blob_decap; > + u32 *desc = skreq->hwdesc; > + > + init_job_desc(desc, 0); diff --git a/a/content_digest b/N1/content_digest index 7e2235a..2bf62b1 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,7 +1,7 @@ "ref\020180720054656.29143-1-udit.agarwal@nxp.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\0Sun, 22 Jul 2018 23:34:11 +0000\0" + "Date\0Sun, 22 Jul 2018 19:34:11 -0400\0" "To\0Udit Agarwal <udit.agarwal@nxp.com>" dhowells@redhat.com zohar@linux.vnet.ibm.com @@ -22,10 +22,10 @@ "> will only be able to view the blob of the key.\n" "\n" "The term \"trusted keys\" comes from the usage of the Trusted Platform\n" - "Module (TPM). \302\240The term \"trusted\" now also refers to keyrings, which\n" + "Module (TPM). The term \"trusted\" now also refers to keyrings, which\n" "has nothing to do with a TPM.\n" "\n" - "What is the correlation between the term \"secure keys\" and CAAM? \302\240Are\n" + "What is the correlation between the term \"secure keys\" and CAAM? Are\n" "\"secure keys\", as defined in this patch, limited to a specific HW\n" "crypto device?\n" "\n" @@ -56,9 +56,9 @@ "> --- /dev/null\n" "> +++ b/Documentation/security/keys/secure-key.rst\n" "> @@ -0,0 +1,67 @@\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" @@ -605,8 +605,10 @@ "> +\n" "> +void caam_sk_redblob_encap_desc(struct sk_req *skreq, struct sk_desc *skdesc)\n" "> +{\n" - "> +\tstruct redblob_encap_desc *red_blob_desc > +\t\t\t\t\t&skdesc->dma_u.redblob_encapdesc;\n" - "> +\tstruct sk_red_blob_encap *red_blob_req > +\t\t\t\t\t&skreq->req_u.sk_red_blob_encap;\n" + "> +\tstruct redblob_encap_desc *red_blob_desc =\n" + "> +\t\t\t\t\t&skdesc->dma_u.redblob_encapdesc;\n" + "> +\tstruct sk_red_blob_encap *red_blob_req =\n" + "> +\t\t\t\t\t&skreq->req_u.sk_red_blob_encap;\n" "> +\tu32 *desc = skreq->hwdesc;\n" "> +\n" "> +\tinit_job_desc(desc, 0);\n" @@ -634,8 +636,10 @@ "> + */\n" "> +void caam_sk_redblob_decap_desc(struct sk_req *skreq, struct sk_desc *skdesc)\n" "> +{\n" - "> +\tstruct redblob_decap_desc *red_blob_desc > +\t\t\t\t\t&skdesc->dma_u.redblob_decapdesc;\n" - "> +\tstruct sk_red_blob_decap *red_blob_req > +\t\t\t\t\t&skreq->req_u.sk_red_blob_decap;\n" + "> +\tstruct redblob_decap_desc *red_blob_desc =\n" + "> +\t\t\t\t\t&skdesc->dma_u.redblob_decapdesc;\n" + "> +\tstruct sk_red_blob_decap *red_blob_req =\n" + "> +\t\t\t\t\t&skreq->req_u.sk_red_blob_decap;\n" "> +\tu32 *desc = skreq->hwdesc;\n" "> +\n" "> +\tinit_job_desc(desc, 0);\n" @@ -1319,4 +1323,4 @@ "> +\n" > +#endif /*_SECUREKEY_DESC_H_*/ -997c02773654e762ef8ef5d8171778a214b4fc52fa7856482c83d12cd2f66342 +9a1f792a25535bd5266db28b00182e7b2dd0c4bc0ddd05b510e651bb6f221cf7
diff --git a/a/1.txt b/N2/1.txt index 80d163c..9d938ec 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -6,10 +6,10 @@ On Fri, 2018-07-20 at 11:16 +0530, Udit Agarwal wrote: > will only be able to view the blob of the key. The term "trusted keys" comes from the usage of the Trusted Platform -Module (TPM). The term "trusted" now also refers to keyrings, which +Module (TPM). ?The term "trusted" now also refers to keyrings, which has nothing to do with a TPM. -What is the correlation between the term "secure keys" and CAAM? Are +What is the correlation between the term "secure keys" and CAAM? ?Are "secure keys", as defined in this patch, limited to a specific HW crypto device? @@ -40,9 +40,9 @@ Mimi > --- /dev/null > +++ b/Documentation/security/keys/secure-key.rst > @@ -0,0 +1,67 @@ -> +===== +> +========== > +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 @@ -118,8 +118,8 @@ Mimi > +KEYS-SECURE > +M: Udit Agarwal <udit.agarwal@nxp.com> > +R: Sahil Malhotra <sahil.malhotra@nxp.com> -> +L: linux-security-module@vger.kernel.org -> +L: keyrings@vger.kernel.org +> +L: linux-security-module at vger.kernel.org +> +L: keyrings at vger.kernel.org > +S: Supported > +F: include/keys/secure-type.h > +F: security/keys/secure_key.c @@ -128,7 +128,7 @@ Mimi > + > KEYS/KEYRINGS: > M: David Howells <dhowells@redhat.com> -> L: keyrings@vger.kernel.org +> L: keyrings at vger.kernel.org > diff --git a/include/keys/secure-type.h b/include/keys/secure-type.h > new file mode 100644 > index 000000000000..5b7a5f144e41 @@ -589,8 +589,10 @@ Mimi > + > +void caam_sk_redblob_encap_desc(struct sk_req *skreq, struct sk_desc *skdesc) > +{ -> + struct redblob_encap_desc *red_blob_desc > + &skdesc->dma_u.redblob_encapdesc; -> + struct sk_red_blob_encap *red_blob_req > + &skreq->req_u.sk_red_blob_encap; +> + struct redblob_encap_desc *red_blob_desc = +> + &skdesc->dma_u.redblob_encapdesc; +> + struct sk_red_blob_encap *red_blob_req = +> + &skreq->req_u.sk_red_blob_encap; > + u32 *desc = skreq->hwdesc; > + > + init_job_desc(desc, 0); @@ -618,8 +620,10 @@ Mimi > + */ > +void caam_sk_redblob_decap_desc(struct sk_req *skreq, struct sk_desc *skdesc) > +{ -> + struct redblob_decap_desc *red_blob_desc > + &skdesc->dma_u.redblob_decapdesc; -> + struct sk_red_blob_decap *red_blob_req > + &skreq->req_u.sk_red_blob_decap; +> + struct redblob_decap_desc *red_blob_desc = +> + &skdesc->dma_u.redblob_decapdesc; +> + struct sk_red_blob_decap *red_blob_req = +> + &skreq->req_u.sk_red_blob_decap; > + u32 *desc = skreq->hwdesc; > + > + init_job_desc(desc, 0); @@ -1302,3 +1306,8 @@ Mimi > + struct device *dev); > + > +#endif /*_SECUREKEY_DESC_H_*/ + +-- +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 7e2235a..a5ca13b 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,17 +1,8 @@ "ref\020180720054656.29143-1-udit.agarwal@nxp.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\0Sun, 22 Jul 2018 23:34:11 +0000\0" - "To\0Udit Agarwal <udit.agarwal@nxp.com>" - dhowells@redhat.com - zohar@linux.vnet.ibm.com - jmorris@namei.org - serge@hallyn.com - linux-integrity@vger.kernel.org - keyrings@vger.kernel.org - linux-security-module@vger.kernel.org - " linux-kernel@vger.kernel.org\0" - "Cc\0sahil.malhotra@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\0Sun, 22 Jul 2018 19:34:11 -0400\0" + "To\0linux-security-module@vger.kernel.org\0" "\00:1\0" "b\0" "On Fri, 2018-07-20 at 11:16 +0530, Udit Agarwal wrote:\n" @@ -22,10 +13,10 @@ "> will only be able to view the blob of the key.\n" "\n" "The term \"trusted keys\" comes from the usage of the Trusted Platform\n" - "Module (TPM). \302\240The term \"trusted\" now also refers to keyrings, which\n" + "Module (TPM). ?The term \"trusted\" now also refers to keyrings, which\n" "has nothing to do with a TPM.\n" "\n" - "What is the correlation between the term \"secure keys\" and CAAM? \302\240Are\n" + "What is the correlation between the term \"secure keys\" and CAAM? ?Are\n" "\"secure keys\", as defined in this patch, limited to a specific HW\n" "crypto device?\n" "\n" @@ -56,9 +47,9 @@ "> --- /dev/null\n" "> +++ b/Documentation/security/keys/secure-key.rst\n" "> @@ -0,0 +1,67 @@\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" @@ -134,8 +125,8 @@ "> +KEYS-SECURE\n" "> +M:\tUdit Agarwal <udit.agarwal@nxp.com>\n" "> +R:\tSahil Malhotra <sahil.malhotra@nxp.com>\n" - "> +L:\tlinux-security-module@vger.kernel.org\n" - "> +L:\tkeyrings@vger.kernel.org\n" + "> +L:\tlinux-security-module at vger.kernel.org\n" + "> +L:\tkeyrings at vger.kernel.org\n" "> +S:\tSupported\n" "> +F:\tinclude/keys/secure-type.h\n" "> +F:\tsecurity/keys/secure_key.c\n" @@ -144,7 +135,7 @@ "> +\n" "> KEYS/KEYRINGS:\n" "> M:\tDavid Howells <dhowells@redhat.com>\n" - "> L:\tkeyrings@vger.kernel.org\n" + "> L:\tkeyrings at vger.kernel.org\n" "> diff --git a/include/keys/secure-type.h b/include/keys/secure-type.h\n" "> new file mode 100644\n" "> index 000000000000..5b7a5f144e41\n" @@ -605,8 +596,10 @@ "> +\n" "> +void caam_sk_redblob_encap_desc(struct sk_req *skreq, struct sk_desc *skdesc)\n" "> +{\n" - "> +\tstruct redblob_encap_desc *red_blob_desc > +\t\t\t\t\t&skdesc->dma_u.redblob_encapdesc;\n" - "> +\tstruct sk_red_blob_encap *red_blob_req > +\t\t\t\t\t&skreq->req_u.sk_red_blob_encap;\n" + "> +\tstruct redblob_encap_desc *red_blob_desc =\n" + "> +\t\t\t\t\t&skdesc->dma_u.redblob_encapdesc;\n" + "> +\tstruct sk_red_blob_encap *red_blob_req =\n" + "> +\t\t\t\t\t&skreq->req_u.sk_red_blob_encap;\n" "> +\tu32 *desc = skreq->hwdesc;\n" "> +\n" "> +\tinit_job_desc(desc, 0);\n" @@ -634,8 +627,10 @@ "> + */\n" "> +void caam_sk_redblob_decap_desc(struct sk_req *skreq, struct sk_desc *skdesc)\n" "> +{\n" - "> +\tstruct redblob_decap_desc *red_blob_desc > +\t\t\t\t\t&skdesc->dma_u.redblob_decapdesc;\n" - "> +\tstruct sk_red_blob_decap *red_blob_req > +\t\t\t\t\t&skreq->req_u.sk_red_blob_decap;\n" + "> +\tstruct redblob_decap_desc *red_blob_desc =\n" + "> +\t\t\t\t\t&skdesc->dma_u.redblob_decapdesc;\n" + "> +\tstruct sk_red_blob_decap *red_blob_req =\n" + "> +\t\t\t\t\t&skreq->req_u.sk_red_blob_decap;\n" "> +\tu32 *desc = skreq->hwdesc;\n" "> +\n" "> +\tinit_job_desc(desc, 0);\n" @@ -1317,6 +1312,11 @@ "> +int key_deblob(struct secure_key_payload *p, enum sk_req_type decap_type,\n" "> +\t struct device *dev);\n" "> +\n" - > +#endif /*_SECUREKEY_DESC_H_*/ + "> +#endif /*_SECUREKEY_DESC_H_*/\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 -997c02773654e762ef8ef5d8171778a214b4fc52fa7856482c83d12cd2f66342 +06eb02233fc99b83041c300b86b7c03b737df5cf6f77029f0944cf49525af33d
diff --git a/a/1.txt b/N3/1.txt index 80d163c..69d3a37 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -40,9 +40,9 @@ Mimi > --- /dev/null > +++ b/Documentation/security/keys/secure-key.rst > @@ -0,0 +1,67 @@ -> +===== +> +========== > +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 @@ -589,8 +589,10 @@ Mimi > + > +void caam_sk_redblob_encap_desc(struct sk_req *skreq, struct sk_desc *skdesc) > +{ -> + struct redblob_encap_desc *red_blob_desc > + &skdesc->dma_u.redblob_encapdesc; -> + struct sk_red_blob_encap *red_blob_req > + &skreq->req_u.sk_red_blob_encap; +> + struct redblob_encap_desc *red_blob_desc = +> + &skdesc->dma_u.redblob_encapdesc; +> + struct sk_red_blob_encap *red_blob_req = +> + &skreq->req_u.sk_red_blob_encap; > + u32 *desc = skreq->hwdesc; > + > + init_job_desc(desc, 0); @@ -618,8 +620,10 @@ Mimi > + */ > +void caam_sk_redblob_decap_desc(struct sk_req *skreq, struct sk_desc *skdesc) > +{ -> + struct redblob_decap_desc *red_blob_desc > + &skdesc->dma_u.redblob_decapdesc; -> + struct sk_red_blob_decap *red_blob_req > + &skreq->req_u.sk_red_blob_decap; +> + struct redblob_decap_desc *red_blob_desc = +> + &skdesc->dma_u.redblob_decapdesc; +> + struct sk_red_blob_decap *red_blob_req = +> + &skreq->req_u.sk_red_blob_decap; > + u32 *desc = skreq->hwdesc; > + > + init_job_desc(desc, 0); diff --git a/a/content_digest b/N3/content_digest index 7e2235a..89672e7 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -1,7 +1,7 @@ "ref\020180720054656.29143-1-udit.agarwal@nxp.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\0Sun, 22 Jul 2018 23:34:11 +0000\0" + "Date\0Sun, 22 Jul 2018 19:34:11 -0400\0" "To\0Udit Agarwal <udit.agarwal@nxp.com>" dhowells@redhat.com zohar@linux.vnet.ibm.com @@ -56,9 +56,9 @@ "> --- /dev/null\n" "> +++ b/Documentation/security/keys/secure-key.rst\n" "> @@ -0,0 +1,67 @@\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" @@ -605,8 +605,10 @@ "> +\n" "> +void caam_sk_redblob_encap_desc(struct sk_req *skreq, struct sk_desc *skdesc)\n" "> +{\n" - "> +\tstruct redblob_encap_desc *red_blob_desc > +\t\t\t\t\t&skdesc->dma_u.redblob_encapdesc;\n" - "> +\tstruct sk_red_blob_encap *red_blob_req > +\t\t\t\t\t&skreq->req_u.sk_red_blob_encap;\n" + "> +\tstruct redblob_encap_desc *red_blob_desc =\n" + "> +\t\t\t\t\t&skdesc->dma_u.redblob_encapdesc;\n" + "> +\tstruct sk_red_blob_encap *red_blob_req =\n" + "> +\t\t\t\t\t&skreq->req_u.sk_red_blob_encap;\n" "> +\tu32 *desc = skreq->hwdesc;\n" "> +\n" "> +\tinit_job_desc(desc, 0);\n" @@ -634,8 +636,10 @@ "> + */\n" "> +void caam_sk_redblob_decap_desc(struct sk_req *skreq, struct sk_desc *skdesc)\n" "> +{\n" - "> +\tstruct redblob_decap_desc *red_blob_desc > +\t\t\t\t\t&skdesc->dma_u.redblob_decapdesc;\n" - "> +\tstruct sk_red_blob_decap *red_blob_req > +\t\t\t\t\t&skreq->req_u.sk_red_blob_decap;\n" + "> +\tstruct redblob_decap_desc *red_blob_desc =\n" + "> +\t\t\t\t\t&skdesc->dma_u.redblob_decapdesc;\n" + "> +\tstruct sk_red_blob_decap *red_blob_req =\n" + "> +\t\t\t\t\t&skreq->req_u.sk_red_blob_decap;\n" "> +\tu32 *desc = skreq->hwdesc;\n" "> +\n" "> +\tinit_job_desc(desc, 0);\n" @@ -1319,4 +1323,4 @@ "> +\n" > +#endif /*_SECUREKEY_DESC_H_*/ -997c02773654e762ef8ef5d8171778a214b4fc52fa7856482c83d12cd2f66342 +9437a3ab1fe3937d4a94777073ab1c97822b09921e7f4f7c35134fa64d8287a9
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.