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.
Bug 1215707 - regression: Stunnel should default to fips=no
Summary: regression: Stunnel should default to fips=no
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: stunnel
Version: 6.7
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: 6.8
Assignee: Tomas Mraz
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On:
Blocks: 1217621 1253743 1271982 1310222
TreeView+ depends on / blocked
 
Reported: 2015-04-27 14:05 UTC by Miroslav Vadkerti
Modified: 2019-09-12 08:25 UTC (History)
7 users (show)

Fixed In Version: stunnel-4.29-6.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1490851 (view as bug list)
Environment:
Last Closed: 2016-05-11 00:40:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Patch which should fix the regressions (1.75 KB, patch)
2015-09-17 11:53 UTC, Tomas Mraz 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0922 0 normal SHIPPED_LIVE stunnel bug fix update 2016-05-10 22:53:15 UTC

Description Miroslav Vadkerti 2015-04-27 14:05:11 UTC 
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:
Comment 1 Kai Engert (:kaie) (inactive account) 2015-09-17 11:22:00 UTC 
I agree with the request.

I've just upgraded a RHEL 6.x box to 6.7 latest, and stunnel stopped to work, with the given error message.

The machine doesn't use FIPS, so the FIPS related error message is confusing.
Comment 2 Kai Engert (:kaie) (inactive account) 2015-09-17 11:22:48 UTC 
Raising priority because it's a regression.
Comment 3 Kai Engert (:kaie) (inactive account) 2015-09-17 11:27:24 UTC 
some relevant public discussion, which claims the error message means that the problem is with openssl:
https://www.stunnel.org/pipermail/stunnel-users/2012-March/003608.html
Comment 5 Tomas Mraz 2015-09-17 11:51:42 UTC 
Not only that, but enabling the FIPS mode by default (even if the prelink did not mess with openssl) means that the stunnel will behave quite differently in regards to used ciphersuites and protocol versions. The defaults are quite different in the non-FIPS enabled build from the FIPS enabled build.
I suppose there will be customer regression reports too.
Comment 6 Tomas Mraz 2015-09-17 11:53:33 UTC 
Created attachment 1074406 [details]
Patch which should fix the regressions

This patch also changes the default method to all - which is the only appropriate for default currently as the TLSv1 method does not enable TLSv1.2 which should be used whenever possible.
Comment 15 errata-xmlrpc 2016-05-11 00:40:36 UTC 
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, 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://rhn.redhat.com/errata/RHBA-2016-0922.html
Note You need to log in before you can comment on or make changes to this bug.