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
Is your feature request related to a problem? Please describe.
Binaries that we build on our own aren't FIPS-enabled
Describe the solution you'd like
The same set of golang packages that we build off internally but FIPS-enabled. Since FIPS enabled builds requires CGO_ENABLED=1 we could have or either a set of -static packages or either a -fips based one, without loosing the static packages that we ship now which are handy in different contexts.
Adds meta/cos-minimal package which requires the minimal set of packages
in order to have a minimal functioning cOS derivative.
This is also in the long-term very handy if we are going to have a
separate set of packages which are fips-enabled (#491)
Signed-off-by: Ettore Di Giacinto <edigiacinto@suse.com>
Adds meta/cos-minimal package which requires the minimal set of packages
in order to have a minimal functioning cOS derivative.
This is also in the long-term very handy if we are going to have a
separate set of packages which are fips-enabled (#491)
Signed-off-by: Ettore Di Giacinto <edigiacinto@suse.com>
Is your feature request related to a problem? Please describe.
Binaries that we build on our own aren't FIPS-enabled
Describe the solution you'd like
The same set of golang packages that we build off internally but FIPS-enabled. Since FIPS enabled builds requires
CGO_ENABLED=1
we could have or either a set of-static
packages or either a-fips
based one, without loosing the static packages that we ship now which are handy in different contexts.Additional context
https://github.com/golang/go/blob/dev.boringcrypto.go1.12/misc/boring/README.md
The text was updated successfully, but these errors were encountered: