-
Bug
-
Resolution: Done
-
Normal
-
rhel-9.0.0, rhel-9.1.0, rhel-9.2.0, rhel-9.3.0, rhel-9.4
-
ruby-3.1.2-142.module_el9+787+b20bfeee (CentOS Stream), ruby-3.1.2-142.module+el9.4.0+21038+70f870c9 (RHEL)
-
None
-
Important
-
ZStream
-
rhel-sst-pt-python-ruby-nodejs
-
ssg_core_services
-
4
-
15
-
3
-
Dev ack
-
False
-
-
None
-
None
-
Approved Blocker
-
Pass
-
None
-
If docs needed, set a value
-
-
Unspecified
-
None
Description of problem:
With a FIPS enabled RHEL 9 system, a Ruby script that reads in a private key fails to do so. The same key can be read without FIPS enabled.
Version-Release number of selected component (if applicable):
Any Ruby version on RHEL 9.
How reproducible:
Always
Steps to Reproduce:
1. Acquire a RHEL 9 host with FIPS enabled
2. Register the machine
3. dnf module enable ruby
4. dnf install ruby
5. ruby -e "require 'openssl';OpenSSL::PKey.read(File.read('/etc/pki/consumer/key.pem'))"
Actual results:
-e:1:in `read': Could not parse PKey (OpenSSL::PKey::PKeyError)
from -e:1:in `<main>'
Expected results:
No errors
Additional info:
This issue was discovered when attempting to run Red Hat Satellite's foreman_scap_client script. The related BZ – https://bugzilla.redhat.com/show_bug.cgi?id=2168931
- blocks
-
LOG-3933 Fluentd pods are in CrashLoopBackOff status when the cluster has FIPS enabled.
- Closed
-
SAT-19389 RHEL9 clients with FIPS mode, failed to upload compliance report to Satellite and fails with exception(Unable to load certs)
- Closed
-
SAT-25748 RHEL9 clients with FIPS mode, failed to upload compliance report to Satellite and fails with exception(Unable to load certs)
- Closed
- is blocked by
-
RHEL-5586 ruby:3.1/ruby: Rebase to the latest Ruby 3.1 release [rhel-9]
- Closed
- is related to
-
RHEL-12724 ruby: Ruby cannot read private key in FIPS mode on RHEL 9 [rhel-9]
- Closed
- relates to
-
RHEL-12724 ruby: Ruby cannot read private key in FIPS mode on RHEL 9 [rhel-9]
- Closed
- external trackers
- links to
-
RHBA-2023:124477 Major: ruby:3.1 bug fix update
- mentioned on