Bug 2132694
Summary: | GOLANG_FIPS=1 go get fails with "x509: certificate specifies an incompatible key usage" [rhel-8.8] | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Edjunior Barbosa Machado <emachado> | |
Component: | golang | Assignee: | David Benoit <dbenoit> | |
Status: | CLOSED ERRATA | QA Contact: | Edjunior Barbosa Machado <emachado> | |
Severity: | unspecified | Docs Contact: | Jacob Taylor Valdez <jvaldez> | |
Priority: | unspecified | |||
Version: | 8.8 | CC: | asm, danken, dbenoit, emachado, igkioka, sipoyare, tstellar | |
Target Milestone: | rc | Keywords: | Triaged | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | go-toolset:rhel8:8080020221017124915:17f3f959 | Doc Type: | Bug Fix | |
Doc Text: |
.`golang` now supports 4096 bit keys in x509 FIPS mode
Previously, `golang` did not support the 4096 bit keys in x509 FIPS mode. Consequently, when the user used 4096 bit keys the program crashed. With this update, `golang` now supports 4096 bit keys in x509 FIPS mode.
|
Story Points: | --- | |
Clone Of: | ||||
: | 2133019 (view as bug list) | Environment: | ||
Last Closed: | 2023-05-16 08:24:23 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 2133019 |
Description
Edjunior Barbosa Machado
2022-10-06 12:15:39 UTC
I am told that this bug affects RHEL-8.6, too, and therefore OCP-4.12. Can this be backported? (In reply to Dan Kenigsberg from comment #5) > I am told that this bug affects RHEL-8.6, too, and therefore OCP-4.12. Can > this be backported? I was unable to reproduce this with rhel-8.6 latest released golang-1.17.12-1.module+el8.6.0+16014+a372c00b (go-toolset-rhel8-8060020220720230014.97d7f71f) on RHEL-8.6.0-updates-20221019.0. Could you please confirm which version of golang package is being used? I was able to reproduce in OCP-4.12 (rhel-8.6) 1. creating debug pod with admin privileges: $ oc debug deployment/cluster-cloud-controller-manager-operator --as-root -n openshift-cloud-controller-manager-operator 2. install gdb sh-4.4# yum install gdb -y 3. check go runtime version of the operator: sh-4.4# gdb /cluster-controller-manager-operator -ex "p 'runtime.buildVersion'" -ex q output: $1 = 0x1a65878 "go1.19.1" (In reply to Motty Sisam from comment #7) > output: > $1 = 0x1a65878 "go1.19.1" I'm not familiar with ocp environment, but judging by this output, it is probably using a newer version of golang. RHEL-8.6 shipped go 1.17, whereas go 1.19 was just recently introduced with RHEL-8.8 builds. I've seen David ack the doc text in the verbatim RHEL 9 version of this bug. Setting r_d_t Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (go-toolset:rhel8 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:2761 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |