Bug 1297755
| Summary: | Can not configure TLSv1.2 for stunnel | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Michael <michael_furman> |
| Component: | stunnel | Assignee: | Tomas Mraz <tmraz> |
| Status: | CLOSED ERRATA | QA Contact: | Stefan Dordevic <sdordevi> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.9 | CC: | dgross, magoldma, salmy, sdordevi, skremen, szidek, zpytela |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | stunnel-4.29-6.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-11 00:41:02 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: | 1057564, 1253743, 1310222 | ||
|
Description
Michael
2016-01-12 11:59:20 UTC
Thank you for the fix!!! When it will be released (approximately)? 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. 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 You have to go through the regular support channels with this request. 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. 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. 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 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 Additional clarification: We develop the product that is installed on RedHat 6 and uses already installed RedHat 6 RPMs. 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 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 |