Firmware Test Suite

fwts: securebootcert reports failures for missing KEK abd DB variables even when secure boot is not enabled

Bug #1374351 reported by Colin Ian King on 2014-09-26

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Firmware Test Suite	Fix Released	Medium	Ivan Hu

Bug Description

If secureboot is not enabled the securebootcert test still reports failures if the DB and KEK are not found. The test should probably only run if secureboot is enabled.

Related branches

lp:ubuntu/vivid-proposed/fwts

Colin Ian King (colin-king) on 2014-09-26

Changed in fwts:
importance:	Undecided → Medium

Revision history for this message

Alex Hung (alexhung) wrote on 2014-09-26:

I think it would be nice if the test is still run but report as information. This can be used to detect whether secure boot can be turned on with specific OS, ex. Windows or Ubuntu etc.

Revision history for this message

Colin Ian King (colin-king) wrote on 2014-09-26:

Indeed, an info message rather than a hard failure in the non-secureboot mode would be beneficial.

Ivan Hu (ivan.hu) on 2014-09-29

Changed in fwts:
assignee:	nobody → Ivan Hu (ivan.hu)

Revision history for this message

Ivan Hu (ivan.hu) wrote on 2014-09-29:

This test was made to check the readiness for the machine. I might also be good to check the if in setup mode reports as info instead of just report failures.

Revision history for this message

Ivan Hu (ivan.hu) wrote on 2014-09-29:

When secureboot enabled, it's obverious that something wrong with missing DB and
KEK variables, failures will be report. When the secureboot disabled and missing
DB and KEK variables, report the information that the machine is not in
readiness for secureboot.

Ivan Hu (ivan.hu) on 2014-09-29