pcrlock: log if we generate an "empty" policy
Such a policy won't provide any protection, but it's still entirely fine to have it like this in various contexts, for example at OS install time, to allocate the nvindex and reference it in enrollments. However, it does deserve mention, hence log about it at LOG_NOTICE level. This is based on a similar patch by Arnaud Patard <arnaud.patard@collabora.com> proposed at #33663.
This commit is contained in:
committed by
Mike Yuan
parent
2c8184a8d2
commit
f9807539b0
@@ -4438,6 +4438,9 @@ static int make_policy(bool force, RecoveryPinMode recovery_pin_mode) {
|
||||
if (r < 0)
|
||||
return r;
|
||||
|
||||
if (!force && new_prediction.pcrs == 0)
|
||||
log_notice("Set of PCRs to use for policy is empty. Generated policy will not provide any protection in its current form. Proceeding.");
|
||||
|
||||
usec_t predict_start_usec = now(CLOCK_MONOTONIC);
|
||||
|
||||
r = tpm2_pcr_prediction_run(el, &new_prediction);
|
||||
|
||||
Reference in New Issue
Block a user