Open m-iwanicki opened 11 months ago
Adding Read From Terminal Until Esc=Exit
to the end of Reset To Default Secure Boot Keys
should fix this issue (754c180), previous solution only worked in that one keyword.
@BeataZdunczyk This can be grouped together with these big secure boot PRs. Added label to group similar issues together.
Device
QEMU
RTE version
QEMU
Affected component(s) or functionality
No response
Brief summary
Get Secure Boot Menu Construction returns Advanced Secure Boot Keys Management menu instead of Secure Boot Configuration
How reproducible
Every time
How to reproduce
mkdir qemu-data
qemu-img create -f qcow2 qemu-data/hdd.qcow2 20G
touch qemu-data/ubuntu.iso
./scripts/ci/qemu-run.sh graphic os
or./scripts/ci/qemu-run.sh graphic os_install
robot -L TRACE -v rte_ip:127.0.0.1 -v snipeit:no -v config:qemu dasharo-security/secure-boot.robot
Bug also happens when using normal ubuntu.iso (for example with Ubuntu 22.04.03) installed or not.
Expected behavior
After resetting secure boot keys to default and returning to previous menu Get Secure Boot Menu Construction should return
${sb_menu} = ['Current Secure Boot State Disabled', 'Enable Secure Boot [ ]', 'Secure Boot Mode <Standard Mode>']
Actual behavior
Returns Advanced Secure Boot Keys Management menu
${sb_menu} = ['> Reset to default Secure Boot Keys', '> Erase all Secure Boot Keys', 'Individual key management:', '> PK Options', '> KEK Options', '> DB Options', '> DBX Options', 'v']
Link to screenshots or logs
Additional context
Doesn't happen when using
./scripts/ci/qemu-run.sh graphic firmware
Solutions you've tried
Fix: Adding
Sleep 3s
inlib/secure-boot-lib.robot
file inMake Sure That Keys Are Provisioned
keyword betweenReset To Default Secure Boot Keys ${advanced_menu}
andExit From Current Menu
. It takes about 2-3 seconds to reset keys to default after choosing yes in this step: