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

diff --git a/a/1.txt b/N1/1.txt
index 34f23e7..1f61a40 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -8,7 +8,7 @@ On Sat, 2017-10-28 at 16:34 +0800, joeyli wrote:
 > > > > 
 > > > > On Mon, Oct 23, 2017 at 11:54:43AM -0400, Mimi Zohar wrote:
 > > > > > On Thu, 2017-10-19 at 15:51 +0100, David Howells wrote:
-> > > > > > From: Chun-Yi Lee <joeyli.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
+> > > > > > From: Chun-Yi Lee <joeyli.kernel@gmail.com>
 > > > > > > 
 > > > > > > When KEXEC_VERIFY_SIG is not enabled, kernel should not loads image
 > > > > > > through kexec_file systemcall if securelevel has been set.
@@ -20,9 +20,9 @@ On Sat, 2017-10-28 at 16:34 +0800, joeyli wrote:
 > > > > > leaves out testing to see if the integrity subsystem is enabled.
 > > > > > 
 > > > > > Commit 503ceaef8e2e "ima: define a set of appraisal rules requiring
-> > > > > file signatures" was upstreamed.  An additional patch could force
+> > > > > file signatures" was upstreamed. ?An additional patch could force
 > > > > > these rules to be added to the custom policy, if lockdown is enabled.
-> > > > >  This and other patches in this series could then check to see if
+> > > > > ?This and other patches in this series could then check to see if
 > > > > > is_ima_appraise_enabled() is true.
 > > > > > 
 > > > > > Mimi
@@ -31,14 +31,14 @@ On Sat, 2017-10-28 at 16:34 +0800, joeyli wrote:
 > > > > I have updated the patch title and description, and I also added
 > > > > is_ima_appraise_enabled() as the following. Is it good to you?
 > > > 
-> > > Yes, that works.  Thanks!  Remember is_ima_appraise_enabled() is
+> > > Yes, that works. ?Thanks! ?Remember is_ima_appraise_enabled() is
 > > > dependent on the "ima: require secure_boot rules in lockdown mode"
-> > > patch - http://kernsec.org/pipermail/linux-security-module-archive/201
+> > > patch -?http://kernsec.org/pipermail/linux-security-module-archive/201
 > > > 7-October/003910.html.
 > > > 
 > > > The IMA "secure_boot" policy can be specified on the boot command line
-> > > as ima_policy="secure_boot".  It requires kernel modules, firmware,
-> > > kexec kernel image and the IMA custom policy to be signed.  In
+> > > as ima_policy="secure_boot". ?It requires kernel modules, firmware,
+> > > kexec kernel image and the IMA custom policy to be signed. ?In
 > > > lockdown mode, these rules are enabled by default and added to the
 > > > custom policy.
 > > > 
@@ -52,15 +52,15 @@ On Sat, 2017-10-28 at 16:34 +0800, joeyli wrote:
 > > > ima_post_read_file() respectively.
 > > 
 > > Hm, with "lockdown" enabled on the boot command line, I'm now able to
-> > do the kexec load, but not the unload.  :/   After the kexec load with
+> > do the kexec load, but not the unload.  :/ ? After the kexec load with
 > 
 > I have tried on Qemu with OVMF, I can load and unload second kernel by
 > kexec tool (on openSUSE is in kexec-tools RPM):  
 > 
 > # kexec -u -s
 
-Thanks, I left off the "-s" option, causing it to fail.  This is the
-correct behavior.  So both with/without the "-s" option are working
+Thanks, I left off the "-s" option, causing it to fail. ?This is the
+correct behavior. ?So both with/without the "-s" option are working
 properly.
 
 > I add -s for using kexec-load-file, and I signed kernel by pesign.
@@ -85,3 +85,8 @@ Yes, based on the patches in David's tree, "lockdown" is being carried
 to the target OS properly.
 
 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/N1/content_digest
index e23889e..cfb1d29 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -5,19 +5,10 @@
  "ref\01509027463.5886.26.camel@linux.vnet.ibm.com\0"
  "ref\01509132746.3729.9.camel@linux.vnet.ibm.com\0"
  "ref\020171028083446.GG20348@linux-l9pv.suse\0"
- "ref\020171028083446.GG20348-g7OFGfmEpDh8S/rGE13EwQ@public.gmane.org\0"
- "From\0Mimi Zohar <zohar-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>\0"
- "Subject\0Re: [PATCH 07/27] kexec_file: Disable at runtime if securelevel has been set\0"
+ "From\0zohar@linux.vnet.ibm.com (Mimi Zohar)\0"
+ "Subject\0[PATCH 07/27] kexec_file: Disable at runtime if securelevel has been set\0"
  "Date\0Sun, 29 Oct 2017 18:26:05 -0400\0"
- "To\0joeyli <jlee-IBi9RG/b67k@public.gmane.org>\0"
- "Cc\0David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>"
-  linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  gnomes-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org
-  linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org
-  linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  jforbes-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
- " Matthew Garrett <mjg59-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>\0"
+ "To\0linux-security-module@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "On Sat, 2017-10-28 at 16:34 +0800, joeyli wrote:\n"
@@ -30,7 +21,7 @@
  "> > > > \n"
  "> > > > On Mon, Oct 23, 2017 at 11:54:43AM -0400, Mimi Zohar wrote:\n"
  "> > > > > On Thu, 2017-10-19 at 15:51 +0100, David Howells wrote:\n"
- "> > > > > > From: Chun-Yi Lee <joeyli.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\n"
+ "> > > > > > From: Chun-Yi Lee <joeyli.kernel@gmail.com>\n"
  "> > > > > > \n"
  "> > > > > > When KEXEC_VERIFY_SIG is not enabled, kernel should not loads image\n"
  "> > > > > > through kexec_file systemcall if securelevel has been set.\n"
@@ -42,9 +33,9 @@
  "> > > > > leaves out testing to see if the integrity subsystem is enabled.\n"
  "> > > > > \n"
  "> > > > > Commit 503ceaef8e2e \"ima: define a set of appraisal rules requiring\n"
- "> > > > > file signatures\" was upstreamed. \302\240An additional patch could force\n"
+ "> > > > > file signatures\" was upstreamed. ?An additional patch could force\n"
  "> > > > > these rules to be added to the custom policy, if lockdown is enabled.\n"
- "> > > > > \302\240This and other patches in this series could then check to see if\n"
+ "> > > > > ?This and other patches in this series could then check to see if\n"
  "> > > > > is_ima_appraise_enabled() is true.\n"
  "> > > > > \n"
  "> > > > > Mimi\n"
@@ -53,14 +44,14 @@
  "> > > > I have updated the patch title and description, and I also added\n"
  "> > > > is_ima_appraise_enabled() as the following. Is it good to you?\n"
  "> > > \n"
- "> > > Yes, that works. \302\240Thanks! \302\240Remember is_ima_appraise_enabled() is\n"
+ "> > > Yes, that works. ?Thanks! ?Remember is_ima_appraise_enabled() is\n"
  "> > > dependent on the \"ima: require secure_boot rules in lockdown mode\"\n"
- "> > > patch -\302\240http://kernsec.org/pipermail/linux-security-module-archive/201\n"
+ "> > > patch -?http://kernsec.org/pipermail/linux-security-module-archive/201\n"
  "> > > 7-October/003910.html.\n"
  "> > > \n"
  "> > > The IMA \"secure_boot\" policy can be specified on the boot command line\n"
- "> > > as ima_policy=\"secure_boot\". \302\240It requires kernel modules, firmware,\n"
- "> > > kexec kernel image and the IMA custom policy to be signed. \302\240In\n"
+ "> > > as ima_policy=\"secure_boot\". ?It requires kernel modules, firmware,\n"
+ "> > > kexec kernel image and the IMA custom policy to be signed. ?In\n"
  "> > > lockdown mode, these rules are enabled by default and added to the\n"
  "> > > custom policy.\n"
  "> > > \n"
@@ -74,15 +65,15 @@
  "> > > ima_post_read_file() respectively.\n"
  "> > \n"
  "> > Hm, with \"lockdown\" enabled on the boot command line, I'm now able to\n"
- "> > do the kexec load, but not the unload.  :/ \302\240 After the kexec load with\n"
+ "> > do the kexec load, but not the unload.  :/ ? After the kexec load with\n"
  "> \n"
  "> I have tried on Qemu with OVMF, I can load and unload second kernel by\n"
  "> kexec tool (on openSUSE is in kexec-tools RPM):  \n"
  "> \n"
  "> # kexec -u -s\n"
  "\n"
- "Thanks, I left off the \"-s\" option, causing it to fail. \302\240This is the\n"
- "correct behavior. \302\240So both with/without the \"-s\" option are working\n"
+ "Thanks, I left off the \"-s\" option, causing it to fail. ?This is the\n"
+ "correct behavior. ?So both with/without the \"-s\" option are working\n"
  "properly.\n"
  "\n"
  "> I add -s for using kexec-load-file, and I signed kernel by pesign.\n"
@@ -106,6 +97,11 @@
  "Yes, based on the patches in David's tree, \"lockdown\" is being carried\n"
  "to the target OS properly.\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
 
-682e833c5728ace9fcc492223733ede6b103459c53493fd82bb940ec4a62ca76
+23e8031058556263365547a1fbb853d100a7c4e52118cf60c43337996e09fdaf

diff --git a/a/1.txt b/N2/1.txt
index 34f23e7..a0b00b3 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -8,7 +8,7 @@ On Sat, 2017-10-28 at 16:34 +0800, joeyli wrote:
 > > > > 
 > > > > On Mon, Oct 23, 2017 at 11:54:43AM -0400, Mimi Zohar wrote:
 > > > > > On Thu, 2017-10-19 at 15:51 +0100, David Howells wrote:
-> > > > > > From: Chun-Yi Lee <joeyli.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
+> > > > > > From: Chun-Yi Lee <joeyli.kernel@gmail.com>
 > > > > > > 
 > > > > > > When KEXEC_VERIFY_SIG is not enabled, kernel should not loads image
 > > > > > > through kexec_file systemcall if securelevel has been set.
diff --git a/a/content_digest b/N2/content_digest
index e23889e..ee4ad9c 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -5,19 +5,18 @@
  "ref\01509027463.5886.26.camel@linux.vnet.ibm.com\0"
  "ref\01509132746.3729.9.camel@linux.vnet.ibm.com\0"
  "ref\020171028083446.GG20348@linux-l9pv.suse\0"
- "ref\020171028083446.GG20348-g7OFGfmEpDh8S/rGE13EwQ@public.gmane.org\0"
- "From\0Mimi Zohar <zohar-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>\0"
+ "From\0Mimi Zohar <zohar@linux.vnet.ibm.com>\0"
  "Subject\0Re: [PATCH 07/27] kexec_file: Disable at runtime if securelevel has been set\0"
  "Date\0Sun, 29 Oct 2017 18:26:05 -0400\0"
- "To\0joeyli <jlee-IBi9RG/b67k@public.gmane.org>\0"
- "Cc\0David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>"
-  linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  gnomes-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org
-  linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org
-  linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-  jforbes-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
- " Matthew Garrett <mjg59-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>\0"
+ "To\0joeyli <jlee@suse.com>\0"
+ "Cc\0David Howells <dhowells@redhat.com>"
+  linux-security-module@vger.kernel.org
+  gnomes@lxorguk.ukuu.org.uk
+  linux-efi@vger.kernel.org
+  gregkh@linuxfoundation.org
+  linux-kernel@vger.kernel.org
+  jforbes@redhat.com
+ " Matthew Garrett <mjg59@google.com>\0"
  "\00:1\0"
  "b\0"
  "On Sat, 2017-10-28 at 16:34 +0800, joeyli wrote:\n"
@@ -30,7 +29,7 @@
  "> > > > \n"
  "> > > > On Mon, Oct 23, 2017 at 11:54:43AM -0400, Mimi Zohar wrote:\n"
  "> > > > > On Thu, 2017-10-19 at 15:51 +0100, David Howells wrote:\n"
- "> > > > > > From: Chun-Yi Lee <joeyli.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\n"
+ "> > > > > > From: Chun-Yi Lee <joeyli.kernel@gmail.com>\n"
  "> > > > > > \n"
  "> > > > > > When KEXEC_VERIFY_SIG is not enabled, kernel should not loads image\n"
  "> > > > > > through kexec_file systemcall if securelevel has been set.\n"
@@ -108,4 +107,4 @@
  "\n"
  Mimi
 
-682e833c5728ace9fcc492223733ede6b103459c53493fd82bb940ec4a62ca76
+804c2c29b9a43ba42e27098bfa557b185a2ce9284773c3784fa9cef56ea17b77

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.