Update shared crypto to v1.0.0 #1245
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
impact:breaking-change
apop5
approved these changes
Dec 17, 2024
Flickdm
approved these changes
Dec 17, 2024
Major Changes: - Note: Shared Crypto now follows straightforward [semantic versioning](https://semver.org/). The version number is incremented based on the type of changes made to the shared crypto binaries. The version number is not tied to the version of the underlying crypto provider. - Note: Prior to adopting semantic versioning in the `1.0.0` release, the version number followed a form of `YYYY.MM.PATCH`. The `1.0.0` release was the first to use semantic versioning and proceeds any of those versions. Breaking Change - Standalone MM Integration Two options are now provided for Standalone MM. **It is important to select the option based on the Standalone MM core used on your platform**: - [StandaloneMmPkg](https://github.com/tianocore/edk2/tree/master/StandaloneMmPkg/Core) - Use `STANDALONEMM_CRYPTO_SERVICES` - [MmSupervisorPkg](https://github.com/microsoft/mu_feature_mm_supv/tree/main/MmSupervisorPkg/Core) - Use `STANDALONEMM_MMSUPV_CRYPTO_SERVICES` Since the MM Supervisor currently does not support `AARCH64`, only a `X64` MM Supervisor Standalone MM binary is available. A platform should not have both `STANDALONEMM_CRYPTO_SERVICES` and `STANDALONEMM_MMSUPV_CRYPTO_SERVICES` set to non-`NONE` values. --- See https://github.com/microsoft/mu_crypto_release/releases/tag/v1.0.0 for the detailed set of changes. Signed-off-by: Michael Kubacki <[email protected]>
makubacki
force-pushed
the
update_shared_crypto_1_0_0
branch
from
a31cab7 to
e05bf66
Compare
ProjectMuBot
pushed a commit
that referenced
this pull request
Dec 18, 2024
## Description #### Major Changes: - Note: Shared Crypto now follows straightforward [semantic versioning](https://semver.org/). The version number is incremented based on the type of changes made to the shared crypto binaries. The version number is not tied to the version of the underlying crypto provider. - Note: Prior to adopting semantic versioning in the `1.0.0` release, the version number followed a form of `YYYY.MM.PATCH`. The `1.0.0` release was the first to use semantic versioning and proceeds any of those versions. --- See https://github.com/microsoft/mu_crypto_release/releases/tag/v1.0.0 for the detailed set of changes. --- - [x] Impacts functionality? - [ ] Impacts security? - [x] Breaking change? - [ ] Includes tests? - [ ] Includes documentation? - [x] Backport to release branch? ## How This Was Tested - Use shared crypto ext dep on a platform already using it - Integration on a X64 MM Supervisor Standalone MM platform - Integration on a X64 non-MM Supervisor Standalone MM platform ## Integration Instructions #### Breaking Change - Standalone MM Integration Two options are now provided for Standalone MM. **It is important to select the option based on the Standalone MM core used on your platform**: - [StandaloneMmPkg](https://github.com/tianocore/edk2/tree/master/StandaloneMmPkg/Core) - Use `STANDALONEMM_CRYPTO_SERVICES` - [MmSupervisorPkg](https://github.com/microsoft/mu_feature_mm_supv/tree/main/MmSupervisorPkg/Core) - Use `STANDALONEMM_MMSUPV_CRYPTO_SERVICES` Since the MM Supervisor currently does not support `AARCH64`, only a `X64` MM Supervisor Standalone MM binary is available. A platform should not have both `STANDALONEMM_CRYPTO_SERVICES` and `STANDALONEMM_MMSUPV_CRYPTO_SERVICES` set to non-`NONE` values. Signed-off-by: Michael Kubacki <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Major Changes:
Note: Shared Crypto now follows straightforward semantic versioning. The version number is incremented based on the type of changes made to the shared crypto binaries. The version number is not tied to the version of the underlying crypto provider.
Note: Prior to adopting semantic versioning in the
1.0.0release, the version number followed a form ofYYYY.MM.PATCH. The1.0.0release was the first to use semantic versioning and proceeds any of those versions.See https://github.com/microsoft/mu_crypto_release/releases/tag/v1.0.0 for the detailed set of changes.
How This Was Tested
Integration Instructions
Breaking Change - Standalone MM Integration
Two options are now provided for Standalone MM. It is important to select the option based on the Standalone MM core used on your platform:
STANDALONEMM_CRYPTO_SERVICESSTANDALONEMM_MMSUPV_CRYPTO_SERVICESSince the MM Supervisor currently does not support
AARCH64, only aX64MM Supervisor Standalone MM binary is available. A platform should not have bothSTANDALONEMM_CRYPTO_SERVICESandSTANDALONEMM_MMSUPV_CRYPTO_SERVICESset to non-NONEvalues.