Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CryptoPkg: Require exact crypto version match #1157

Merged

Conversation

Javagedes
Copy link
Contributor

@Javagedes Javagedes commented Sep 23, 2024

Description

Crypto versioning is not currently backwards compatible. This change updates the check to require an exact match of the crypto version.

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

How This Was Tested

N/A

Integration Instructions

N/A

@github-actions github-actions bot added the impact:non-functional Does not have a functional impact label Sep 23, 2024
Crypto versioning is not currently backwards compatible.  This change
updates the check to require an exact match of the crypto version.
@Javagedes Javagedes enabled auto-merge (squash) September 23, 2024 19:47
@makubacki makubacki added the type:design-change A new proposal or modification to a feature design label Sep 23, 2024
@Javagedes Javagedes removed the impact:non-functional Does not have a functional impact label Sep 23, 2024
@Javagedes Javagedes merged commit 34455f5 into microsoft:dev/202405 Sep 23, 2024
33 checks passed
Javagedes added a commit to Javagedes/mu_basecore that referenced this pull request Sep 23, 2024
## Description

Crypto versioning is not currently backwards compatible. This change
updates the check to require an exact match of the crypto version.

- [ ] Impacts functionality?
- [ ] Impacts security?
- [ ] Breaking change?
- [ ] Includes tests?
- [ ] Includes documentation?

## How This Was Tested

N/A

## Integration Instructions

N/A
Javagedes added a commit to Javagedes/mu_basecore that referenced this pull request Sep 24, 2024
## Description

Crypto versioning is not currently backwards compatible. This change
updates the check to require an exact match of the crypto version.

- [ ] Impacts functionality?
- [ ] Impacts security?
- [ ] Breaking change?
- [ ] Includes tests?
- [ ] Includes documentation?

## How This Was Tested

N/A

## Integration Instructions

N/A
Javagedes added a commit that referenced this pull request Sep 24, 2024
## Description

Crypto versioning is not currently backwards compatible. This change
updates the check to require an exact match of the crypto version.

- [ ] Impacts functionality?
- [ ] Impacts security?
- [ ] Breaking change?
- [ ] Includes tests?
- [ ] Includes documentation?

## How This Was Tested

N/A

## Integration Instructions

N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:design-change A new proposal or modification to a feature design
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants