-
Notifications
You must be signed in to change notification settings - Fork 3.3k
{Packaging} Bump cryptography to 39.0.1 and pyOpenSSL to 23.0.0 #25544
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
Conversation
… and pyOpenSSL to 23.0.0 Signed-off-by: Thomas Spear <[email protected]>
|
Thank you for your contribution tspearconquest! We will review the pull request and get back to you soon. |
|
@microsoft-github-policy-service agree |
1 similar comment
|
@microsoft-github-policy-service agree |
|
Add @bebound for awareness |
|
Thank you for your contribution @tspearconquest. The PR looks good. I will merge it once CI passes. |
|
Ref: https://cryptography.io/en/39.0.1/openssl/#cryptography.hazmat.backends.openssl.openssl_version_text |
….0 (Azure#25544)" This reverts commit 2ecac33.
… and pyOpenSSL to 23.0.0
Related command
Description
Azure-CLI dependency:
cryptographyv38.0.4has a CVE, this release of cryptography patches the CVETesting Guide
cryptography v38.0.4 has a CVE and v39.0.1 is no longer compatible with OpenSSL 1.x releases. All users must upgrade OpenSSL to 3.x to continue using the CLI
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.