Feature #17495
Run most of our test suite with Secure Boot enabled
Start date:
Due date:
% Done:
0%
Feature Branch:
Type of work:
Code
Starter:
Affected tool:
Deliverable for:
Description
UEFI Secure Boot restricts some operations that would otherwise be allowed and has thus potential to break stuff, due to kernel lockdown (see Feature #17493).
Once we support Secure Boot, it could be that we start seeing problems that are hard to understand/reproduce because they only occur when Secure Boot is enabled.
Running as much as we can of our test suite with Secure Boot enabled would mitigate this problem.
Subtasks
Related issues
Blocked by Tails - |
Resolved | 2018-12-17 | |
Blocks Tails - Feature #16209: Core work: Foundations Team | Confirmed | ||
Blocks Tails - Feature #17493: Check what to do wrt. kernel lockdown | Confirmed |
History
#1 Updated by intrigeri 2020-02-23 07:08:35
- blocked by
Feature #6560: UEFI Secure boot added
#2 Updated by intrigeri 2020-02-23 07:08:44
- blocks Feature #16209: Core work: Foundations Team added
#3 Updated by intrigeri 2020-05-04 13:45:51
- Description updated
#4 Updated by intrigeri 2020-05-04 13:46:24
- related to Feature #17493: Check what to do wrt. kernel lockdown added
#5 Updated by intrigeri 2020-05-04 13:49:48
- related to deleted (
Feature #17493: Check what to do wrt. kernel lockdown)
#6 Updated by intrigeri 2020-05-04 13:50:03
- blocks Feature #17493: Check what to do wrt. kernel lockdown added