Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
applies to RHEL-7.4 too,
stunnel defaults to fips=yes
+++ This bug was initially created as a clone of Bug #1215707 +++
Description of problem:
The fix in bug 1171879 introduced an usability change in stunnel and on a non-FIPS machine with enabled prelink stunnel will fail:
# stunnel /tmp/tmp.SOoewnl3DD/BUILD/curl-7.19.7/tests/stunnel.conf
2015.04.27 08:48:11 LOG7[3068:3078223664]: Snagged 64 random bytes from /root/.rnd
2015.04.27 08:48:11 LOG7[3068:3078223664]: Wrote 1024 new random bytes to /root/.rnd
2015.04.27 08:48:11 LOG7[3068:3078223664]: RAND_status claims sufficient entropy for the PRNG
2015.04.27 08:48:11 LOG7[3068:3078223664]: PRNG seeded successfully
2015.04.27 08:48:11 LOG7[3068:3078223664]: Certificate: ./stunnel.pem
2015.04.27 08:48:11 LOG7[3068:3078223664]: Certificate loaded
2015.04.27 08:48:11 LOG7[3068:3078223664]: Key file: ./stunnel.pem
2015.04.27 08:48:11 LOG7[3068:3078223664]: Private key loaded
2015.04.27 08:48:11 LOG7[3068:3078223664]: SSL context initialized for service curltest
2015.04.27 08:48:11 LOG3[3068:3078223664]: FIPS_mode_set: 2D06C06E: error:2D06C06E:FIPS routines:FIPS_module_mode_set:fingerprint does not match
This can cause various issues in customer setups. FIPS failures in non-FIPS mode are not wanted.
Version-Release number of selected component (if applicable):
stunnel-4.29-3.el6_6.1
How reproducible:
100%
Steps to Reproduce:
1. have prelink installed and setup
2. booted in non-FIPS mode
3. No fips option in configuration file
4. run stunnel
Actual results:
FIPS error
Expected results:
No FIPS error
Additional info:
Actually on RHEL-7 the stunnel always defaulted to the FIPS mode which means if switching it back to non-fips mode it could be seen as a regression. So this is something not eligible for RHEL-7.