microsoft/mu_feature_dfci

[Bug]: DFCI variable locking should not leverage custom DFCI specific locking

Closed this issue · 0 comments

Is there an existing issue for this?

  • I have searched existing issues

Current Behavior

A recent change was made to lock DFCI variables based on a custom variable. This had a benefit of fewer dependencies on Project Mu only code but it broke certain important scenarios with FASR isolation.

Expected Behavior

variables should be locked in all cases

Steps To Reproduce

On certain dev builds of certain dev systems boot and notice DFCI variables are not locked.

Build Environment

NA

Version Information

2.2.0

Urgency

High

Are you going to fix this?

I will fix it

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response