Skip to content

Provide some means of optionally using OpenSSL as backing cryptographic lib for FIPS applications #712

Answered by maraino
josh-hemphill asked this question in Ideas
Discussion options

You must be logged in to vote

There's a couple of solutions for this:

  1. Compile 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:
To be clear, we are not making any statements or representations about the suitability of this code in relation to 
the FIPS 140-2 standard. Interested users will have to evaluate for themselves whether the code is useful for their
own purposes.

For example, Rancher uses this image https://hub.docker.com/r/goboring/golang to build the "RKE Government" version of RKE2.

  1. Redhat provides a FI…

Replies: 1 comment 8 replies

Comment options

You must be logged in to vote
8 replies
@josh-hemphill
Comment options

@maraino
Comment options

@josh-hemphill
Comment options

@maraino
Comment options

@mmalone
Comment options

Answer selected by josh-hemphill
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Ideas
Labels
None yet
3 participants