You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think what must have happened is that you checked out the source code using the release tag AWS-LC-FIPS 3.0. Unfortunately, for a few days, the tag AWS-LC-FIPS 3.0 was pointing to the wrong commit. Apologies.
To fix your locally checked out code, I believe you have to delete the tag and check out the release again.
Problem:
AWS-LC-FIPS 3.0.0 reports "1.40.0" as its version string, indeed openssl/base.h contains:
#define AWSLC_VERSION_NUMBER_STRING "1.40.0"
Where AWS-LC-FIPS 2.0.17 has the right string:
#define AWSLC_VERSION_NUMBER_STRING "2.0.17"
Is this something intentional, will the new 3.0 branch keep the version string corresponding to its non-FIPS version?
The text was updated successfully, but these errors were encountered: