diff for duplicates of <1522103487.3541.162.camel@linux.vnet.ibm.com> diff --git a/a/1.txt b/N1/1.txt index 7340426..583bc60 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -31,7 +31,7 @@ On Wed, 2018-03-14 at 16:57 +0100, Petr Vorel wrote: > (19f8a84713ed "ima: measure and appraise the IMA policy itself"). If you can determine that writing the policy should fail and then -detect that it actually did fail, the latter option is more complete. +detect that it actually did fail, the latter option is more complete. > BTW load_policy() use old approach catting the content into sysfs policy file. > Maybe it'd be good to echo policy filename into sysfs policy file for kernel > @@ -39,7 +39,7 @@ detect that it actually did fail, the latter option is more complete. Cat'ing the file doesn't work if the policy has to be signed. I haven't tried writing the policy pathname, when the file doesn't -require it to be signed. There's no reason that it wouldn't work. +require it to be signed. There's no reason that it wouldn't work. > * ima_measurement.sh,ima_violations.sh: Avoid using tmpfs filesystem [1]. You > suggested using RAM block device. Would it be ok to use filesystem created on diff --git a/a/content_digest b/N1/content_digest index 8824abd..4897bd8 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,10 +1,8 @@ "ref\020180314155731.5943-1-pvorel@suse.cz\0" "From\0Mimi Zohar <zohar@linux.vnet.ibm.com>\0" - "Subject\0Re: [RFC PATCH v2 0/4] Rewrite tests into new API + fixes\0" + "Subject\0[LTP] [RFC PATCH v2 0/4] Rewrite tests into new API + fixes\0" "Date\0Mon, 26 Mar 2018 18:31:27 -0400\0" - "To\0Petr Vorel <pvorel@suse.cz>" - " ltp@lists.linux.it\0" - "Cc\0linux-integrity@vger.kernel.org\0" + "To\0ltp@lists.linux.it\0" "\00:1\0" "b\0" "Hi Petr,\n" @@ -40,7 +38,7 @@ "> (19f8a84713ed \"ima: measure and appraise the IMA policy itself\").\n" "\n" "If you can determine that writing the policy should fail and then\n" - "detect that it actually did fail, the latter option is more complete. \n" + "detect that it actually did fail, the latter option is more complete.\302\240\n" "\n" "> BTW load_policy() use old approach catting the content into sysfs policy file.\n" "> Maybe it'd be good to echo policy filename into sysfs policy file for kernel >\n" @@ -48,7 +46,7 @@ "\n" "Cat'ing the file doesn't work if the policy has to be signed. I\n" "haven't tried writing the policy pathname, when the file doesn't\n" - "require it to be signed. There's no reason that it wouldn't work.\n" + "require it to be signed. \302\240There's no reason that it wouldn't work.\n" "\n" "> * ima_measurement.sh,ima_violations.sh: Avoid using tmpfs filesystem [1]. You\n" "> suggested using RAM block device. Would it be ok to use filesystem created on\n" @@ -122,4 +120,4 @@ "> mode change 100755 => 100644 testcases/kernel/security/integrity/ima/tests/ima_setup.sh\n" > -26bb7919e3be47c4c37d7c4569141c701b8cf5f302a8522f8b2b7ca6cf5bd2be +b1bde822360ee07cab341b8253e8e00e2d6bc002e128d04d34f3f40d86aabf8b
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.