diff for duplicates of <1538997900.15382.90.camel@linux.ibm.com> diff --git a/a/1.txt b/N1/1.txt index ab3d3a6..fb31df7 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -13,8 +13,8 @@ On Fri, 2018-10-05 at 12:25 -0700, Matthew Garrett wrote: In the trusted mount scenario, we trust the data should not change between calculating the file hash and reading the file data, making it -similar to other local filesystems. Unlike other local filesystems, -however, we can't detect when the file changes. For this reason we +similar to other local filesystems. Unlike other local filesystems, +however, we can't detect when the file changes. For this reason we need to re-calculate the file hash to measure/appraise the file each time. @@ -22,7 +22,7 @@ time. > also trust it to give you back an accurate hash if you ask for one. Going from trusting the filesystem to behave properly, to trusting the -file hash that the filesystem provides is a major leap. We don't do +file hash that the filesystem provides is a major leap. We don't do this today for any local filesystem. > 2) You don't trust FUSE mounts, in which case you pass @@ -35,7 +35,7 @@ this today for any local filesystem. If you trust a FUSE filesystem to not only behave properly, but also to return file hashes, what is the value of measuring/appraising the -files? Define a custom policy that doesn't measure/appraise files on +files? Define a custom policy that doesn't measure/appraise files on FUSE filesystems. Mimi diff --git a/a/content_digest b/N1/content_digest index 9b3e993..314a0f7 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -29,8 +29,8 @@ "\n" "In the trusted mount scenario, we trust the data should not change\n" "between calculating the file hash and reading the file data, making it\n" - "similar to other local filesystems. Unlike other local filesystems,\n" - "however, we can't detect when the file changes. For this reason we\n" + "similar to other local filesystems. \302\240Unlike other local filesystems,\n" + "however, we can't detect when the file changes. \302\240For this reason we\n" "need to re-calculate the file hash to measure/appraise the file each\n" "time.\n" "\n" @@ -38,7 +38,7 @@ "> also trust it to give you back an accurate hash if you ask for one.\n" "\n" "Going from trusting the filesystem to behave properly, to trusting the\n" - "file hash that the filesystem provides is a major leap. We don't do\n" + "file hash that the filesystem provides is a major leap. \302\240We don't do\n" "this today for any local filesystem.\n" "\n" "> 2) You don't trust FUSE mounts, in which case you pass\n" @@ -51,9 +51,9 @@ "\n" "If you trust a FUSE filesystem to not only behave properly, but also\n" "to return file hashes, what is the value of measuring/appraising the\n" - "files? Define a custom policy that doesn't measure/appraise files on\n" + "files? \302\240Define a custom policy that doesn't measure/appraise files on\n" "FUSE filesystems.\n" "\n" Mimi -aa6803d1ebab7bd97fcd13d417a3e8e3008118ff90915a10ae2361a0f8495234 +764dcfd68a24c3e070b5e61ec742deb75cca572cfdf5dfb3c87804232b327609
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.