You can set the SSLProtocol only for the first VirtualHost in theĬonfiguration file. Server and/or all name-based VirtualHosts supporting TLSĪnd another here: Is it possible to set an SSLProtocol in Apache for a single VirtualHost (poodle)?. Unless you have IP VirtualHosts, in practice the settings from theįirst occurrence of the SSLProtocol directive are used for the whole That's enough!Ī similar issue was posted here: How to disable TLS 1.1 & 1.2 in Apache?. So, check if this is your case (the answer is "yes" for virtually everyone) and change the protocols in that file. As the name of this file begins with "s", it will load before the vhosts configured in nf (which begins with "v"). Most users have an ssl.conf file in their servers, with a vhost for port 443 configured there. Disable it in the OpenSSL config file with:įirst of all, you must identify what is the default vhost for port 443 in your server (the first SSL vhost loaded by Apache) and edit it's configuration file.The options used in the above function is defined at line 444 in pkg.sslmod/mod_ssl.hĪll protocols gets enabled at line 586 in pkg.sslmod/ssl_engine_init.c whereafter specific protocols gets disabled on the subsequent lines How to disable it then? SSLProtocol gets parsed at line 925 in pkg.sslmod/ssl_engine_config.c OpenSSL v1.0.1 has some known issues with TLSv1.2 but if it's supported I suppose the same goes for that as for TLSv1.1 it's not recognized/handled by mod_ssl and thus never disabled. OpenSSL supports a protocol setting for TLSv1.1, but since the SSLProtocol does not account for this options, it never gets disabled. In this case, where SSLv3 is the only protocol to have been explicitly enabled, the 3 others will be disabled.
Upon initiating a new server context, ALL available protocols will be enabled, and the above char is inspected using some nifty bitwise AND operations to determine what protocols should be disabled. When the SSLProtocol has been parsed, it results in a char looking something like this: 0 1 0 0 Bear with me, this is gonna get amateur-stack-overflowish: Intrigued by this bug (and yes, I've been able to reproduce it) I've taken a look at the source code for the latest stable version of mod_ssl and found an explanation.
0 kommentar(er)
