-
Notifications
You must be signed in to change notification settings - Fork 24
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
Panic when using OpenSSL 3.3.1 with FIPS Provider 3.0.9 #205
Comments
This has been patched in openssl-3.2.2-2 in CentOS Stream. It's a compatibility issue with the fips provider within openssl so we don't expect any changes required to golang-fips/go. |
Thanks, that pointed to openssl/openssl#24611 which points to openssl/openssl#24661 |
I have the same issue; I am using 3.1.6 openssl + 3.0.8 FIPS.
Did it got fixed any version of linux? |
If your 3.1.6 openssl contains regression openssl/openssl@3a16b60 ensure that it also has the fix up openssl/openssl@14de8da or a revert of the regression.
yes. |
When compiling golang-fips/go with all the up to date patches (up to and including https://github.com/golang-fips/go/blob/main/patches/017-fix-linkage.patch) and running it in FIPS mode with upstream OpenSSL 3.3.1 with FIPS provider at 3.0.9 a panic happens during regular operation (i.e. go mod tidy / go get)
I am currently suspecting the changes in openssl/openssl#23456 and openssl/openssl#24141 are exposing this error, but I didn't yet investigate if there is incompatibility upstream or if bindings in golang-fips/go golang-fips/openssl need adjustment.
The text was updated successfully, but these errors were encountered: