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
fix: expose aes-cfb ciphers from boringssl #16573
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks for this.
Unlike RIPEMD160
, AES-*-CFB
is a family of ciphers I can actually understand being used in the real world.
CI failures unrelated; merging. |
Release Notes Persisted
|
/trop run backport |
The backport process for this PR has been manually initiated, here we go! :D |
I have automatically backported this PR to "4-0-x", please check out #16617 |
I have automatically backported this PR to "5-0-x", please check out #16618 |
Ref #16195
Closes #16187
Checklist
Release Notes
Notes: Restored support for AES-CFB cipher, which was lost when switching from OpenSSL to BoringSSL.