All of lore.kernel.org
 help / color / mirror / Atom feed

diff for duplicates of <1347e0c5-40c9-34a4-9c54-60bd2917b2d7@linux.vnet.ibm.com>

diff --git a/a/1.txt b/N1/1.txt
index 7eec6ca..ef03139 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -18,7 +18,7 @@ On 05/18/2018 10:39 AM, Mimi Zohar wrote:
 >>>>> abandonned format for the new record type while using
 >>>>> current->audit_context.
 >>> This sounds right, other than "type=INTEGRITY_RULE" (1805) for
->>> ima_audit_measurement().  Could we rename type=1805 to be
+>>> ima_audit_measurement().  Could we rename type=1805 to be
 >> So do we want to change both? I thought that what
 >> ima_audit_measurement() produces looks ok but may not have a good name
 >> for the 'type'. Now in this case I would not want to 'break user space'.
@@ -29,7 +29,7 @@ On 05/18/2018 10:39 AM, Mimi Zohar wrote:
 > Richard, when the containerid is appended to the IMA-audit messages,
 > would we make the audit type name change then?
 >
->>> INTEGRITY_AUDIT or INTEGRITY_IMA_AUDIT?  The new type=1806 audit
+>>> INTEGRITY_AUDIT or INTEGRITY_IMA_AUDIT?  The new type=1806 audit
 >>> message could be named INTEGRITY_RULE or, if that would be confusing,
 >>> INTEGRITY_POLICY_RULE.
 >> For 1806, as we would use it in ima_parse_rule(), we could change that
@@ -41,4 +41,4 @@ One other question is whether IMA's audit calls should all adhere to
 CONFIG_INTEGRITY_AUDIT. Most do but those two that currently use 
 AUDIT_INTEGRITY_RULE do not. Should that be changed as well?
 
-     Stefan
\ No newline at end of file
+     Stefan
\ No newline at end of file
diff --git a/a/content_digest b/N1/content_digest
index 7c403b0..58e2d3c 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -76,7 +76,7 @@
   ">>>>> abandonned format for the new record type while using\n",
   ">>>>> current->audit_context.\n",
   ">>> This sounds right, other than \"type=INTEGRITY_RULE\" (1805) for\n",
-  ">>> ima_audit_measurement(). \302\240Could we rename type=1805 to be\n",
+  ">>> ima_audit_measurement().  Could we rename type=1805 to be\n",
   ">> So do we want to change both? I thought that what\n",
   ">> ima_audit_measurement() produces looks ok but may not have a good name\n",
   ">> for the 'type'. Now in this case I would not want to 'break user space'.\n",
@@ -87,7 +87,7 @@
   "> Richard, when the containerid is appended to the IMA-audit messages,\n",
   "> would we make the audit type name change then?\n",
   ">\n",
-  ">>> INTEGRITY_AUDIT or INTEGRITY_IMA_AUDIT? \302\240The new type=1806 audit\n",
+  ">>> INTEGRITY_AUDIT or INTEGRITY_IMA_AUDIT?  The new type=1806 audit\n",
   ">>> message could be named INTEGRITY_RULE or, if that would be confusing,\n",
   ">>> INTEGRITY_POLICY_RULE.\n",
   ">> For 1806, as we would use it in ima_parse_rule(), we could change that\n",
@@ -99,7 +99,7 @@
   "CONFIG_INTEGRITY_AUDIT. Most do but those two that currently use \n",
   "AUDIT_INTEGRITY_RULE do not. Should that be changed as well?\n",
   "\n",
-  " \302\240\302\240\302\240 Stefan"
+  "     Stefan"
 ]
 
-ff8fe6d0981ef17d399de3a36157494d05c6186edc21b9129068af667d9dd732
+2edf147ed00c3981b783f873e49b5229cb8ad66622aa1521eef4a8035e5c24f7
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.