Provide some means of optionally using OpenSSL as backing cryptographic lib for FIPS applications #712
-
I'm not sure if FIPS certification has been addressed already, but looking at the available Go cryptographic libraries, it looks like there's OpenSSL wrappers that are api compatible with the native one. Providing some ability to swap the backing cryptographic code to OpenSSL could provide a pretty simple way for people who require FIPS certified libraries to still be able to smallstep and applications using the libs. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
There's a couple of solutions for this:
For example, Rancher uses this image https://hub.docker.com/r/goboring/golang to build the "RKE Government" version of RKE2.
There's a great article explaining this in more detail |
Beta Was this translation helpful? Give feedback.
There's a couple of solutions for this:
step-ca
with Go's dev.boringcrypto branch, see README.boringcrypto.md, this branch is generally up-to-date with latest versions of Go and replaces crypto primitives with the ones using BoringSSL that is FIPS compliant, although officially they say this:For example, Rancher uses this image https://hub.docker.com/r/goboring/golang to build the "RKE Government" version of RKE2.