diff options
| author | Peter Jones <pjones@redhat.com> | 2014-06-25 10:46:19 -0400 |
|---|---|---|
| committer | Peter Jones <pjones@redhat.com> | 2014-06-25 10:46:52 -0400 |
| commit | 86173dba42ad5ae002ac99cc515e60104da2245c (patch) | |
| tree | 95d833420e0035c051ff1d7ba7215649f6c9535f | |
| parent | c36d88cb16d10fdc8da2abcc00d3c51f0d425e34 (diff) | |
| download | efi-boot-shim-86173dba42ad5ae002ac99cc515e60104da2245c.tar.gz efi-boot-shim-86173dba42ad5ae002ac99cc515e60104da2245c.zip | |
Explain the logic in secure_mode() better.
I was getting confused reading it, and I wrote it, so clearly it needs
more commentry.
Signed-off-by: Peter Jones <pjones@redhat.com>
| -rw-r--r-- | shim.c | 6 |
1 files changed, 6 insertions, 0 deletions
@@ -499,6 +499,12 @@ static BOOLEAN secure_mode (void) return FALSE; } + /* If we /do/ have "SecureBoot", but /don't/ have "SetupMode", + * then the implementation is bad, but we assume that secure boot is + * enabled according to the status of "SecureBoot". If we have both + * of them, then "SetupMode" may tell us additional data, and we need + * to consider it. + */ status = get_variable(L"SetupMode", &Data, &len, global_var); if (status != EFI_SUCCESS) return TRUE; |
