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.
Since the referenced bugs are closed, I copied the offending contents into this bug:
I think in below paragraphs/lines "SSL 3" should be "SSLv3" and "SSL 2" shoould be "SSLv2" in mod_nss.html
Line 1461-62:
=============
<h1><a name="SSLv2"></a>Why is SSLv2 disabled?</h1>
All major browsers (Firefox, Internet Explorer, Mozilla, Netscape, Opera, and
Safari) support SSL 3 and TLS so there is no need for a web server to support
SSL 2. There are some known attacks against SSL 2 that are handled by SSL
3/TLS. SSLv2 also doesn't support useful features like client authentication.
<br>
Line 418:
=========
</big></big><br>
Specifies the number of seconds SSL 3 sessions are cached.<br>
<br>
Line 405:
=========
<br>
Specifies the number of seconds SSL 2 sessions are cached.<br>
<br>
Verified.
Version ::
mod_nss-1.0.11-6.el7.x86_64
Results ::
[root@rhel7-4 yum.repos.d]# vim /usr/share/doc/mod_nss-1.0.11/mod_nss.html
...
<h1><a name="SSLv2"></a>Why is SSLv2 disabled?</h1>
All major browsers (Firefox, Internet Explorer, Mozilla, Netscape, Opera, and
Safari) support SSLv3 and TLS so there is no need for a web server to support
SSLv2. There are some known attacks against SSLv2 that are handled by
SSLv3/TLS. SSLv2 also doesn't support useful features like client
authentication.
<br>
</big></big><br>
Specifies the number of seconds SSLv3 sessions are cached.<br>
<br>
[root@rhel7-4 yum.repos.d]# grep -i "SSL [23]" /usr/share/doc/mod_nss-1.0.11/mod_nss.html
[root@rhel7-4 yum.repos.d]#
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-2015-2305.html