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.
+++ This bug was initially created as a clone of Bug #979798 +++
Description of problem:
nss >= 3.14 supports TLS 1.1 so mod_tls should support it automatically
Version-Release number of selected component (if applicable):
mod_nss-1.0.8-20.1.fc19.armv7hl
nss-3.14.3-13.0.fc19.armv7hl
How reproducible:
always
Steps to Reproduce:
1. specify NSSProtocol TLSv1.1 in /etc/apache/conf.d/nss.conf
2. connect to the server with client that supports just TLS >= 1.1
3.
Actual results:
connection fails
Expected results:
connection is established
Additional info:
TLSv1.2 should be picked up automatically once nss supports it, too
(In reply to David Jaša from comment #0)
> +++ This bug was initially created as a clone of Bug #979798 +++
>
> Description of problem:
> nss >= 3.14 supports TLS 1.1 so mod_tls should support it automatically
>
> Version-Release number of selected component (if applicable):
> mod_nss-1.0.8-20.1.fc19.armv7hl
> nss-3.14.3-13.0.fc19.armv7hl
>
Support for TLS v1.1 in RHEL 6 has been provided since mod_nss-1.0.8-17.el6, so I am marking this bug as a DUPLICATE of 'Bugzilla Bug #816394 - [RFE] Provide Apache 2.2 support for TLS v1.1 via NSS through mod_nss . . .'.
The patch which supported this has now been ported upstream and is available in the following Brew builds which are awaiting karma in Bodhi:
* mod_nss-1.0.8-24.fc18
* mod_nss-1.0.8-24.fc19
* mod_nss-1.0.8-24.fc20
Please feel free to provide karma for these builds.
Finally, I noticed that since the packages referenced must be customized builds for the 'armv7hl' architecture, please try using the appropriate Fedora SRPM to reproduce your packages.
> How reproducible:
> always
>
> Steps to Reproduce:
> 1. specify NSSProtocol TLSv1.1 in /etc/apache/conf.d/nss.conf
> 2. connect to the server with client that supports just TLS >= 1.1
> 3.
>
> Actual results:
> connection fails
>
> Expected results:
> connection is established
>
> Additional info:
> TLSv1.2 should be picked up automatically once nss supports it, too
*** This bug has been marked as a duplicate of bug 816394 ***