In VariableStandaloneMm, the VariableHaveTcgProtocols() always returns FALSE, it causes TCG MOR secure feature does not work in standalone MM environment.
The commit fda8f631edbbf3823760542a06f12bd60fd39181 added the check agaist Tcg/Tcg2 protocols to detele and lock OS-created MOR variable to fix the issue that Fedora 24 and 25 follow the TCG's Platform Reset Attack Mitigation spec and unintentionally create MOR variable.
As Fedora 24 and 25 are EOL today, in order to fix the MOR feature issue in standalone MM environment, revert the above commit fda8f631edbbf3823760542a06f12bd60fd39181.
[ ] Breaking change?
Breaking change - Does this PR cause a break in build or boot behavior?
Examples: Does it add a new library class or move a module to a different repo.
[ ] Impacts security?
Security - Does this PR have a direct security impact?
Examples: Crypto algorithm change or buffer overflow fix.
[ ] Includes tests?
Tests - Does this PR include any explicit test code?
Description
In VariableStandaloneMm, the VariableHaveTcgProtocols() always returns FALSE, it causes TCG MOR secure feature does not work in standalone MM environment.
The commit fda8f631edbbf3823760542a06f12bd60fd39181 added the check agaist Tcg/Tcg2 protocols to detele and lock OS-created MOR variable to fix the issue that Fedora 24 and 25 follow the TCG's Platform Reset Attack Mitigation spec and unintentionally create MOR variable.
As Fedora 24 and 25 are EOL today, in order to fix the MOR feature issue in standalone MM environment, revert the above commit fda8f631edbbf3823760542a06f12bd60fd39181.
How This Was Tested
Integration Instructions
N/A