** Also affects: linux-bluefield (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-bluefield (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux-bluefield (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-bluefield (Ubuntu Focal)
Assignee: (unassigned) => Shravan Kumar Ramani (sramani)
** Changed in: linux-bluefield (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1948434
Title:
Check if secure boot is enabled with development keys
Status in linux-bluefield package in Ubuntu:
Invalid
Status in linux-bluefield source package in Focal:
In Progress
Bug description:
SRU Justification:
[Impact]
Currently, there is no indication from mlx-bootctl when the user reads the
lifecycle_state sysfs as to whether secure boot is enabled with development
keys or production keys. In order to make this clear to the user, add a check
in the driver.
[Fix]
Check the secure boot development mode status bit. If secure boot is enabled
with the development key, then print it to the output buffer when
lifecycle_state_show() is invoked.
[Test Case]
On a system in secure state, if it has been programmed with development keys,
then reading the lifecycle_state sysfs entry in the mlx-bootctl driver should
print a message that indicates the same.
Similarly, a secure system which has been programmed with production keys
must print the appropriate message when the lifecycle_state sysfs is read.
[Regression Potential]
Can be considered minimum.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1948434/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
