зеркало из https://github.com/microsoft/mu_plus.git
b15f3d42b1
## Description
Mfci has a soft dependency on MuVarPolicyFoundationDxe. The phase based
variables (Target\Manufacturer, Target\Product, Target\SerialNumber,
Target\OEM_01 and Target\OEM_02) are locked using
RegisterVarStateVariablePolicy.
Adding documentation to explicitly call out the need for the MsCorePkg's
MuVarPolicyFoundationDxe to enable phase based locking.
- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [x] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
Ran CI locally
## Integration Instructions
n/a
|
||
|---|---|---|
| .. | ||
| Mfci_Feature.md | ||
| Mfci_Integration_Guide.md | ||
| Mfci_Structures.md | ||