3 ms·
Context: https://lobste.rs/s/zwkuza/intel_cpus_might_leak_information_about https://lobste.rs/s/zwkuza/intel_cpus_might_leak_information... > That discussion w
by tlrobinson 8y ago
Context: https://lobste.rs/s/zwkuza/intel_cpus_might_leak_information_about https://lobste.rs/s/zwkuza/intel_cpus_might_leak_information...
> That discussion was ongoing when OpenBSD caught wind of this – presumably because someone who was embargoed felt that OpenBSD deserved to know – and then fixed it in the worst possible way. (Namely, by snarkily indicating that it was to address a CPU vulnerability.) This was then compounded by Theo’s caustic presentation at BSDCan, which was honestly irresponsible: he clearly didn’t pull eager FPU out of thin air (“post-Spectre rumors”), and should have considered himself part of the embargo in spirit if not in letter.