X-Git-Url: http://git.nikiroo.be/?p=gofetch.git;a=blobdiff_plain;f=test%2Fexpected%2FLWN%2F0000764209.header.html;fp=test%2Fexpected%2FLWN%2F0000764209.header.html;h=e0e86dfce12747b38542473e2c3951f9cf90e997;hp=6042eaf22b6f5a667583e4df10ad3eccbf99eef0;hb=e818d449fee8a5397ab2f05df63bbeffc4c67dc0;hpb=a6a7ff9f2e7f42f17eaa69be2bfad201195b3eb4 diff --git a/test/expected/LWN/0000764209.header.html b/test/expected/LWN/0000764209.header.html index 6042eaf..e0e86df 100644 --- a/test/expected/LWN/0000764209.header.html +++ b/test/expected/LWN/0000764209.header.html @@ -13,7 +13,7 @@
([Kernel] Sep 5, 2018 21:47 UTC (Wed) (corbet))

- The Spectre variant 2 vulnerability allows the speculative execution of incorrect (in an attacker-controllable way) indirect branch predictions, resulting in the ability to exfiltrate information via side channels. The kernel has been reasonably well protected against this variant since shortly after its disclosure in January. It is, however, possible for user-space processes to use Spectre v2 to attack each other; thus far, the mainline kernel has offered relatively little protection against such attacks. A recent proposal from Jiri Kosina may change that situation, but there are still some disagreements around the details. + The Spectre variant 2 vulnerability allows the speculative execution of incorrect (in an attacker-controllable way) indirect branch predictions, resulting in the ability to exfiltrate information via side channels. The kernel has been reasonably well protected against this variant since shortly after its disclosure in January. It is, however, possible for user-space processes to use Spectre v2 to attack each other; thus far, the mainline kernel has offered relatively little protection against such attacks. A recent [1]proposal from Jiri Kosina may change that situation, but there are still some disagreements around the details.



[1] https://lwn.net/ml/linux-kernel/nycvar.YFH.7.76.1809041619510.15880@cbobk.fhfr.pm/