All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <1533307535.4337.415.camel@linux.ibm.com>

diff --git a/a/1.txt b/N1/1.txt
index 30b96f3..dac734c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -3,9 +3,9 @@ On Fri, 2018-08-03 at 07:23 -0700, James Bottomley wrote:
 > > 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
@@ -21,7 +21,7 @@ On Fri, 2018-08-03 at 07:23 -0700, James Bottomley 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.
 > > 
@@ -35,8 +35,8 @@ On Fri, 2018-08-03 at 07:23 -0700, James Bottomley wrote:
 > symmetric keys which are later used by a fast bulk encryptor/decryptor
 > based in software.
 > 
-> >  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
+> >  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 402de45..c47d3cb 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -4,7 +4,7 @@
  "ref\01533306238.4140.1.camel@HansenPartnership.com\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 14:45:35 +0000\0"
+ "Date\0Fri, 03 Aug 2018 10:45:35 -0400\0"
  "To\0James Bottomley <James.Bottomley@hansenpartnership.com>"
   David Howells <dhowells@redhat.com>
  " Udit Agarwal <udit.agarwal@nxp.com>\0"
@@ -27,9 +27,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"
@@ -45,7 +45,7 @@
  "> > > Can you convert this into a \"symmetric\" type and make the backend\n"
  "> > > 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"
@@ -59,8 +59,8 @@
  "> symmetric keys which are later used by a fast bulk encryptor/decryptor\n"
  "> based in software.\n"
  "> \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\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\n"
  "> > would unseal/decrypt data, such as an encrypted key.\n"
  "> > \n"
  "> > The \"symmetric\" key type would be a generic interface for different\n"
@@ -74,4 +74,4 @@
  "\n"
  Mimi
 
-1adbd9153c84121cf7adc444a478a5245228bfa25c50ff79c27b6c2f5fdc36ff
+2481757ffd48bfeeac7a920e0380d5dde11de02e2a775ce7a075d7c47a1b43cd

diff --git a/a/1.txt b/N2/1.txt
index 30b96f3..4758021 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -3,9 +3,9 @@ On Fri, 2018-08-03 at 07:23 -0700, James Bottomley wrote:
 > > 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
@@ -21,7 +21,7 @@ On Fri, 2018-08-03 at 07:23 -0700, James Bottomley 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.
 > > 
@@ -35,8 +35,8 @@ On Fri, 2018-08-03 at 07:23 -0700, James Bottomley wrote:
 > symmetric keys which are later used by a fast bulk encryptor/decryptor
 > based in software.
 > 
-> >  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
+> > ?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
@@ -49,3 +49,8 @@ On Fri, 2018-08-03 at 07:23 -0700, James Bottomley wrote:
 encrypted, ecryptfs, ...).
 
 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 402de45..966bbd6 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -2,24 +2,10 @@
  "ref\08060.1533226481@warthog.procyon.org.uk\0"
  "ref\01533297482.4337.373.camel@linux.ibm.com\0"
  "ref\01533306238.4140.1.camel@HansenPartnership.com\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 14:45:35 +0000\0"
- "To\0James Bottomley <James.Bottomley@hansenpartnership.com>"
-  David 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 10:45:35 -0400\0"
+ "To\0linux-security-module@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "On Fri, 2018-08-03 at 07:23 -0700, James Bottomley wrote:\n"
@@ -27,9 +13,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"
@@ -45,7 +31,7 @@
  "> > > Can you convert this into a \"symmetric\" type and make the backend\n"
  "> > > 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"
@@ -59,8 +45,8 @@
  "> symmetric keys which are later used by a fast bulk encryptor/decryptor\n"
  "> based in software.\n"
  "> \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\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\n"
  "> > would unseal/decrypt data, such as an encrypted key.\n"
  "> > \n"
  "> > The \"symmetric\" key type would be a generic interface for different\n"
@@ -72,6 +58,11 @@
  "\"trusted\" keys are currently being used to decrypt other keys (eg.\n"
  "encrypted, ecryptfs, ...).\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
 
-1adbd9153c84121cf7adc444a478a5245228bfa25c50ff79c27b6c2f5fdc36ff
+7b636152375581f625a521cef9f8fbbee160692fb11de1c7a1d2c7cd739f61c4

diff --git a/a/1.txt b/N3/1.txt
index 30b96f3..dfd7a45 100644
--- a/a/1.txt
+++ b/N3/1.txt
@@ -3,9 +3,9 @@ On Fri, 2018-08-03 at 07:23 -0700, James Bottomley wrote:
 > > 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 402de45..6ac1f17 100644
--- a/a/content_digest
+++ b/N3/content_digest
@@ -4,7 +4,7 @@
  "ref\01533306238.4140.1.camel@HansenPartnership.com\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 14:45:35 +0000\0"
+ "Date\0Fri, 03 Aug 2018 10:45:35 -0400\0"
  "To\0James Bottomley <James.Bottomley@hansenpartnership.com>"
   David Howells <dhowells@redhat.com>
  " Udit Agarwal <udit.agarwal@nxp.com>\0"
@@ -27,9 +27,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"
@@ -74,4 +74,4 @@
  "\n"
  Mimi
 
-1adbd9153c84121cf7adc444a478a5245228bfa25c50ff79c27b6c2f5fdc36ff
+21947c8d13633790b4c2c7f783c72e29338b67bfa1aa0f56d8e119641624845c

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.