-
Notifications
You must be signed in to change notification settings - Fork 103
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
New Let's Encrypt certificate with SHA384 parsing error #2156
Comments
The following test from tempesta-tech/tempesta-test@5beb3e6 passes, while it generates very similar certificate
|
The problem is actually in that Let's Encrypt sends us a certificate bundle, it's certificate concatinated with a CA certificate, and the CA uses
We send the authority certificate only as is and do not use in any way, so we should not parse it and do not sepend memory for the certificate descriptor. |
Let's Encrypt now goes with SHA384 instead of SHA256 signature and Tempesta can't load the certificate:
The certificate uses
prime256r1
, just as previous, so probably we have a certificate parsing bug.The text was updated successfully, but these errors were encountered: