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 1297755 - Can not configure TLSv1.2 for stunnel
Summary: Can not configure TLSv1.2 for stunnel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: stunnel
Version: 6.9
Hardware: All
OS: All
unspecified
high
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: Stefan Dordevic
URL:
Whiteboard:
Depends On:
Blocks: 1057564 1253743 1310222
TreeView+ depends on / blocked
 
Reported: 2016-01-12 11:59 UTC by Michael
Modified: 2019-10-10 10:51 UTC (History)
7 users (show)

Fixed In Version: stunnel-4.29-6.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-11 00:41:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2179981 0 None None None 2016-02-26 15:11:36 UTC
Red Hat Product Errata RHBA-2016:0922 0 normal SHIPPED_LIVE stunnel bug fix update 2016-05-10 22:53:15 UTC

Description Michael 2016-01-12 11:59:20 UTC 
Description of problem:

I need to configure TLSv1.2 protocol for stunnel.
I need to do it to be PCI DSS 3.1 compliant.

Unfortunately when I configure it as following (in file stunnel.conf):

sslVersion = TLSv1.2

I get this error:

Starting stunnel: file stunnel.conf line 10: Incorrect version of SSL protocol

Please note that according to the stunnel chanelog it supported from Version 5.00, 2014.03.06:

https://www.stunnel.org/sdf_ChangeLog.html



Version-Release number of selected component (if applicable):
stunnel-4.29-3.el6_6.1.x86_64


How reproducible:
Configure stunnel and restart service


Steps to Reproduce:
1. configure in file stunnel.conf the following:

sslVersion = TLSv1.2

2. restart the service 
service stunnel restart


Actual results:
Error is appear 
Starting stunnel: file stunnel.conf line 10: Incorrect version of SSL protocol


Expected results:
service restarted successfully.


Additional info:
Comment 4 Michael 2016-01-17 11:07:57 UTC 
Thank you for the fix!!!
When it will be released (approximately)?
Comment 5 Tomas Mraz 2016-01-18 09:09:44 UTC 
It will be released as part of the RHEL-6.8 stunnel erratum if all goes well. I can't give you a date but you can extrapolate from previous RHEL-6 updates.
Comment 6 Michael 2016-01-18 09:30:25 UTC 
Thanks for the update but according to the link it can take about half year:
 https://access.redhat.com/articles/3078

When QA will complete the test?
Will be I able to download the RPM before it will come to RPM repository?

We need it ASAP - we need to prepare our product to be PCI DSS 3.1 complaint
Comment 7 Tomas Mraz 2016-01-18 09:38:40 UTC 
You have to go through the regular support channels with this request.
Comment 8 Michael 2016-01-18 11:08:28 UTC 
Thanks for the fast reply!

Why it can not be releases as the bug fix similar to this:
https://rhn.redhat.com/errata/RHSA-2016-0024.html

I think other companies also will not be able to be PCI DSS 3.1 complaint due to this bug.
Comment 9 Michael 2016-01-21 12:38:29 UTC 
Dear RedHat people,

This bug is the security issue.

Can its fix be released similar to this problem?
https://rhn.redhat.com/errata/RHSA-2016-0024.html


It is not correct way to solve it via support channels.

Probably we will tell to our customers that the product is not PCI DSS 3.1 complaint due to the RedHat bug.
Comment 10 Steve Almy 2016-02-03 14:59:09 UTC 
Hi Michael,

If you have a support entitlement agreement with Red Hat, please contact Red Hat Support to get the proper help with an interim fix.

Thanks
Comment 12 Michael 2016-03-09 07:15:14 UTC 
Dear Red Hat people,
We do not need the interim fix
We need RPM will be in the repository.

We develop the product that is used by many Fortune 500 companies like AT&T, Verizon, Target etc.

These companies need to take RPM from the repository.

Now we will need to tell them that These companies not be able to be PCI DSS 3.1 complaint due to this bug.

Why it can not be releases as the bug fix similar to this:
https://rhn.redhat.com/errata/RHSA-2016-0024.html
Comment 13 Michael 2016-03-10 08:51:31 UTC 
Additional clarification: We develop the product that is installed on RedHat 6 and uses already installed RedHat 6 RPMs.
Comment 14 Matt Goldman 2016-04-13 20:04:13 UTC 
Hi Michael,

If you have a support entitlement agreement with Red Hat, please contact Red Hat Support to get the proper help with an interim fix.

Thanks
Comment 19 errata-xmlrpc 2016-05-11 00:41:02 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.