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.
Description of problem: mod_nss continues to startup even with invalid protocol parameter for NSSProtocol. For example:
NSSProtocol +TLSv1.2
The above would render the error message below and then mod_nss would continue to startup, support all protocols (sslv3->tlsv1.2).
[Wed Oct 26 17:31:34.561906 2016] [:warn] [pid 2085] NSSProtocol: Unknown protocol '+tlsv1.2' not supported
Version-Release number of selected component (if applicable): mod_nss-1.0.11-6.el7.x86_64
How reproducible: Always.
Steps to Reproduce:
1. yum install httpd mod_nss
2. sed -i 's/^NSSProtocol.*/NSSProtocol +TLSv1.2/' /etc/httpd/conf.d/nss.conf
3. systemctl restart httpd
4. openssl s_client -connect localhost:8443 -ssl3
Actual results: All protocols are supported
Expected results: mod_nss would halt startup of httpd if there is an invalid protocol.
Verified using mod_nss version :: mod_nss-1.0.14-10.el7.x86_64
[root@ipaserver01 ~]# sed -i 's/^NSSProtocol.*/NSSProtocol +TLSv1.2/' /etc/httpd/conf.d/nss.conf
[root@ipaserver01 ~]# systemctl restart httpd
Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.
[root@ipaserver01 ~]# tail -1 /var/log/httpd/error_log
[Fri May 26 07:43:24.891331 2017] [:warn] [pid 16254] NSSProtocol: Unknown protocol '+tlsv1.2' not supported
[root@ipaserver01 ~]# rpm -qa mod_nss httpd
mod_nss-1.0.14-10.el7.x86_64
httpd-2.4.6-67.el7.x86_64
Marking BZ as verified.
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://access.redhat.com/errata/RHBA-2017:2009