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
Background
This line of code in /crypto/tls/boring.go limit the RSA key size to 2048 and 3072, which will cause an issue when we try to establish a TLS connection to the server with 4096 key size. There is an open issue to the official go golang/go#41147 discussing about this. So we are seeking for a go version which replace the boring go with the openssl, and we found this repo.
Issue
However, we found that you didn't patch to the boring.go file I mentioned above, so we will still meet the same problem by using this go version.
Request
Is it possible you can add a patch to that boring.go file to remove or modify the RSA key size checker? It is safe to do it because we are now relying on the underlying openssl to be FIPS compliant, right?
The text was updated successfully, but these errors were encountered:
Background
This line of code in /crypto/tls/boring.go limit the RSA key size to 2048 and 3072, which will cause an issue when we try to establish a TLS connection to the server with 4096 key size. There is an open issue to the official go golang/go#41147 discussing about this. So we are seeking for a go version which replace the boring go with the openssl, and we found this repo.
Issue
However, we found that you didn't patch to the boring.go file I mentioned above, so we will still meet the same problem by using this go version.
Request
Is it possible you can add a patch to that boring.go file to remove or modify the RSA key size checker? It is safe to do it because we are now relying on the underlying openssl to be FIPS compliant, right?
The text was updated successfully, but these errors were encountered: