Bug 1323018 - Need an option to enable the client-initiated renegotiation
Summary: Need an option to enable the client-initiated renegotiation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: httpd
Version: 6.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Luboš Uhliarik
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 1269194 1678536
TreeView+ depends on / blocked
 
Reported: 2016-04-01 01:31 UTC by Hisanobu Okuda
Modified: 2020-05-14 15:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1678536 (view as bug list)
Environment:
Last Closed: 2017-06-01 22:02:00 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Hisanobu Okuda 2016-04-01 01:31:37 UTC
Description of problem:
Apache httpd rejects the client-initiated renegotiation on TLS connection. The behavior can not be changed because it is hard-coded. In some environments, the client-initiated renegotiation is required. An option to enable the client-initiated renegotiation is needed.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 7 Chris Williams 2017-06-01 22:02:00 UTC
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017.  During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification.  Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com


Note You need to log in before you can comment on or make changes to this bug.