4 ms·
One interesting piece of information from this post is that Intel notified Ubuntu about the issue on November 9. Project Zero notified Intel on June 1, so it to
by Deimorz 9y ago
One interesting piece of information from this post is that Intel notified Ubuntu about the issue on November 9. Project Zero notified Intel on June 1, so it took over 5 months before they passed it on to Ubuntu (and even longer for the other vendors).
That seems like an extremely long time to me, when it (I assume) was pretty obvious that it was going to require OS changes to mitigate.
- eximius 9y agoWhy would Ubuntu need to be notified? Fixes for this are going to be at the Linux Kernel level or (at most) Debian upstream. Canonical shouldn't need to do anything?
- pritambaral 9y agoIf some fixes can be applied via microcode, then the distros will have to be provided the updated microcode. The kernel (mostly) does not handle CPU microcode distribution.
- hd4 9y agoPretty sure Ubuntu are the largest Linux vendor right now, and have their distro on the largest number of servers worldwide.
- crtasm 9y agoFrom TFA >To address the issue, updates to the Ubuntu kernel and processor microcode will be needed. These updates will be announced in future Ubuntu Security Notices once they are available.
- Thaxll 9y agoUbuntu kernel don't rely on Debian. Have you seen how Debian lags behind the rest in terms of versions.
- subsection1h 9y agoLags behind? Linux kernel version 4.14 is available for Debian Stretch: https://packages.debian.org/stretch-backports/linux-image-amd64 https://packages.debian.org/stretch-backports/linux-image-am...
- eximius 9y agoUbuntu certainly used to rely on Debian. When did it change?
- mmagin 9y agoSo, basically Intel kept this stuff to themselves from June through November?