Blame SOURCES/mod_nss-invalid-protocol-setting.patch

7212c2
From dc6afabbd94fa5b8e1da286ba387814e5df70ff1 Mon Sep 17 00:00:00 2001
7212c2
From: Rob Crittenden <rcritten@redhat.com>
7212c2
Date: Fri, 3 Feb 2017 08:06:14 -0500
7212c2
Subject: [PATCH] Make an invalid protocol setting fatal
7212c2
7212c2
An invalid protocol setting would end up with the default
7212c2
list which is a bit unexpected so kill the server and let
7212c2
the admin figure out what went wrong and fix it.
7212c2
7212c2
Resolves BZ 1389114
7212c2
---
7212c2
 nss_engine_init.c | 1 +
7212c2
 1 file changed, 1 insertion(+)
7212c2
7212c2
diff --git a/nss_engine_init.c b/nss_engine_init.c
7212c2
index 03ac644..0bb2054 100644
7212c2
--- a/nss_engine_init.c
7212c2
+++ b/nss_engine_init.c
7212c2
@@ -785,6 +785,7 @@ static void nss_init_ctx_protocol(server_rec *s,
7212c2
                     ap_log_error(APLOG_MARK, APLOG_WARNING, 0, s,
7212c2
                                  "%s:  Unknown protocol '%s' not supported",
7212c2
                                  protocol_marker, token);
7212c2
+                    nss_die();
7212c2
                 }
7212c2
             }
7212c2
         }
7212c2
-- 
7212c2
2.9.3
7212c2