linux: Implement secure boot state variables
Bug #1593075 reported by
Tim Gardner
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Trusty |
Fix Released
|
Medium
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Unassigned |
Bug Description
User space needs a way to determine the state of secure boot and MOKSBState.
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in linux (Ubuntu): | |
status: | New → Triaged |
tags: | added: kernel-da-key xenial |
Changed in linux (Ubuntu Xenial): | |
status: | Triaged → Fix Committed |
tags: |
added: verification-done-trusty removed: verification-needed-trusty |
tags: |
added: verification-done-vivid removed: verification-needed-vivid |
tags: |
added: verification-done-wily removed: verification-needed-wily |
Changed in linux (Ubuntu Trusty): | |
importance: | Undecided → Medium |
status: | New → Fix Committed |
tags: | removed: verification-done-trusty |
tags: |
added: verification-done-trusty removed: verification-needed-trusty |
To post a comment you must log in.
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- xenial' to 'verification- done-xenial' .
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!