Re: [users@httpd] Weirdo intepretation of SSLprotocol order

2015-05-11 Thread Yann Ylavic
On Mon, May 11, 2015 at 11:30 AM, wrote: > > Do you mean - building 2.2.29 from apache.org sources ? Yes, at least for testing purpose. This would help backporting the change from 2.4.x to 2.2.x. Regards, Yann. - To unsubscrib

Re: [users@httpd] Weirdo intepretation of SSLprotocol order

2015-05-11 Thread apache
Hello, Well - a patched version... what do you mean -i've build apache22-2.2.29_2 from ports... so its already up to date. However openssl runtime is openssl-1.0.1_16, where i see there is a openssl-1.0.2_1 available from ports. I prefer to build from ports, in order to host a standardized en

Re: [users@httpd] Weirdo intepretation of SSLprotocol order

2015-05-07 Thread Yann Ylavic
Hello, you may hit an issue fixed in [1] (for upcoming 2.4.13). Can you manage to build a patched httpd-2.2.29 from sources? Regards, Yann. [1] http://svn.us.apache.org/r1663258 On Wed, May 6, 2015 at 2:54 PM, wrote: > hello, > > > So i have an apache 2.2.29 running Prefork on FreeBSD 64bit

[users@httpd] Weirdo intepretation of SSLprotocol order

2015-05-06 Thread apache
hello, So i have an apache 2.2.29 running Prefork on FreeBSD 64bit. I have a number of vhosts included - one vhost per domain name. In any of these vhost containers the SSLProtocol directive seems to be ignored, but only the default vhost is dictating the SSLProtocol for all other (this is o