X-Git-Url: http://git.nikiroo.be/?p=gofetch.git;a=blobdiff_plain;f=test%2Fexpected%2FLWN%2F0000763729.header.html;fp=test%2Fexpected%2FLWN%2F0000763729.header.html;h=6988e8a200c940939afcb49790ad69d6d8fabd72;hp=c110703fe73fb478e7bf1592110e2cfb1e41719f;hb=3367f6256b5143b7cba2a61de36e74f389a5f379;hpb=b389651b0012a7ba1ff30d164958e155688ac216 diff --git a/test/expected/LWN/0000763729.header.html b/test/expected/LWN/0000763729.header.html index c110703..6988e8a 100644 --- a/test/expected/LWN/0000763729.header.html +++ b/test/expected/LWN/0000763729.header.html @@ -9,11 +9,11 @@
-

[$] Protecting files with fs-verity

+

[$] Protecting files with fs-verity

([Kernel] Aug 30, 2018 18:50 UTC (Thu) (corbet))

- The developers of the Android system have, among their many goals, the wish to better protect Android devices against persistent compromise. It is bad if a device is taken over by an attacker; it's worse if it remains compromised even after a reboot. Numerous mechanisms for ensuring the integrity of installed system files have been proposed and implemented over the years. But it seems there is always room for one more; to fill that space, the fs-verity mechanism is being proposed as a way to protect individual files from malicious modification. + The developers of the Android system have, among their many goals, the wish to better protect Android devices against persistent compromise. It is bad if a device is taken over by an attacker; it's worse if it remains compromised even after a reboot. Numerous mechanisms for ensuring the integrity of installed system files have been proposed and implemented over the years. But it seems there is always room for one more; to fill that space, the [1]fs-verity mechanism is being proposed as a way to protect individual files from malicious modification.



[1] https://lwn.net/ml/linux-fsdevel/20180824161642.1144-1-ebiggers@kernel.org/