On 8/22/2012 10:55 AM, Ben Johnson wrote:
On 8/22/2012 9:36 AM, Eric Covener wrote:
On Wed, Aug 22, 2012 at 9:24 AM, Ben Johnson b...@indietorrent.org wrote:
On 8/22/2012 8:56 AM, Eric Covener wrote:
Dovecot dropped its TLS capabilities, but it still started
the server and bound to
Hello,
I find it extremely troubling that when Apache fails to start due to an
SSL-related misconfiguration nothing is logged to that effect.
For example, if a certificate and private key do not match, Apache will
fail to start and, from what I can tell, fails to log anything at all.
Maybe
example?
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
Dovecot dropped its TLS capabilities, but it still started
the server and bound to the non-secure port.
I'd personally prefer the server fail startup rather than operate w/o SSL.
-
To unsubscribe, e-mail:
On 8/22/2012 8:55 AM, Eric Covener wrote:
example?
I provided one in my initial message: when Apache is configured to use a
given SSL certificate and the key and certificate files do not match.
-
To unsubscribe, e-mail:
On 8/22/2012 8:56 AM, Eric Covener wrote:
Dovecot dropped its TLS capabilities, but it still started
the server and bound to the non-secure port.
I'd personally prefer the server fail startup rather than operate w/o SSL.
While that may be, this preference should not be assumed. Even if the
On Wed, Aug 22, 2012 at 9:24 AM, Ben Johnson b...@indietorrent.org wrote:
On 8/22/2012 8:56 AM, Eric Covener wrote:
Dovecot dropped its TLS capabilities, but it still started
the server and bound to the non-secure port.
I'd personally prefer the server fail startup rather than operate w/o
On 8/22/2012 9:36 AM, Eric Covener wrote:
On Wed, Aug 22, 2012 at 9:24 AM, Ben Johnson b...@indietorrent.org wrote:
On 8/22/2012 8:56 AM, Eric Covener wrote:
Dovecot dropped its TLS capabilities, but it still started
the server and bound to the non-secure port.
I'd personally prefer the
For the sake of thoroughness, in which log does this message appear on
your system?
Initially, the ErrorLog in the base server configuration.
When I added an ErrorLog to the specific SSL enabled virtualhost, the
error appeared in the specific ErrorLog.