[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-httpd-bugs
Subject:    [Bug 56306] SSLCertificateKeyFile path garbled if not explicitly given in each vhost
From:       bugzilla () apache ! org
Date:       2014-04-27 8:55:03
Message-ID: bug-56306-7868-tMOF8yK6e5 () https ! issues ! apache ! org/bugzilla/
[Download RAW message or body]

https://issues.apache.org/bugzilla/show_bug.cgi?id=56306

--- Comment #11 from Kaspar Brand <asfbugz@velox.ch> ---
(In reply to Kaspar Brand from comment #9)
> I'm intending to propose an additional backport for 2.4.x.

I've done so now with r1590359. Examining again the configuration from comment
2, I can also provide an explanation for the troubles you experienced when
using your existing (pre-2.4.9) setup: as already mentioned in comment 8, a
vhost-level SSLCertificate[Key]File directive is overriding a globally
configured one in releases up to 2.4.7, but in 2.4.8/2.4.9, it is simply added
to the list.

In your case, you had five VirtualHost blocks with an individual
SSLCertificateFile directive, but no corresponding SSLCertificateKeyFile, and
mod_ssl was trying to read the file name from an uninitialized key_files array
value. The immediate fix for this has already been committed (see comment 9),
but the additional patch in
https://people.apache.org/~kbrand/mod_ssl-2.4.x-pphrase-certkeyfile-compat.diff
will further restore backwards compatibility for existing configurations.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]