As far as I know, there's no way of measuring the sufficiency of Livepatch. A new kernel will usually have fixes for other bugs and less-impactful vulnerabilities on top of what Livepatch is taking care of, and it's impossible to know whether those fixes will be of significance to the user.
If a user wants to rely on Livepatch entirely (or 'until further notice'), unattended-upgrades can be set to blacklist automatic kernel upgrades.
I certainly don't see any value, in any circumstance, of installing a new kernel automatically but not alerting the user that it's not running, which is one of the things this bug is about, as well as failing to reboot automatically when unattended-upgrades has been set to do so.
Hi Robie -
I think that's a separate issue!
As far as I know, there's no way of measuring the sufficiency of Livepatch. A new kernel will usually have fixes for other bugs and less-impactful vulnerabilities on top of what Livepatch is taking care of, and it's impossible to know whether those fixes will be of significance to the user.
If a user wants to rely on Livepatch entirely (or 'until further notice'), unattended-upgrades can be set to blacklist automatic kernel upgrades.
I certainly don't see any value, in any circumstance, of installing a new kernel automatically but not alerting the user that it's not running, which is one of the things this bug is about, as well as failing to reboot automatically when unattended-upgrades has been set to do so.