From 105d65bfedfa0e381dcebd197ef67aab799fc8b1 Mon Sep 17 00:00:00 2001 From: Rob Crittenden Date: Mon, 29 Feb 2016 22:33:23 -0500 Subject: Check filesystem permissions on NSS database at startup See if the configured user has read access to the NSS database during initialization so the server can gracefully shutdown rather than ending up in a forking loop because the database is owned by root and is therefore unreadable once Apache starts forking. Adds a new configuration option, NSSSkipPermissionCheck , to skip this check in case something goes wrong. https://fedorahosted.org/mod_nss/ticket/3 --- docs/mod_nss.html | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'docs') diff --git a/docs/mod_nss.html b/docs/mod_nss.html index c84f938..ec03a07 100644 --- a/docs/mod_nss.html +++ b/docs/mod_nss.html @@ -440,6 +440,18 @@ reads that many bytes, otherwise it reads until the program exits.
NSSRandomSeed startup /dev/urandom 512
NSSRandomSeed startup /usr/bin/makerandom

+NSSSkipPermissionCheck
+
+The NSS database will be checked to ensure that the user configured +to run Apache as has owner or group read access to the database +configured in NSSCertificateDatabase. This check +can be disabled by setting NSSSkipPermissionCheck +to on. The default is off
+
+Example
+
+NSSSkipPermissionCheck on
+
NSSEngine

Enables or disables the SSL protocol. This is usually used within a -- cgit