Tomasz Sterna writes:
>Dnia 2014-04-10, czw o godzinie 00:29 +, Joe Malcolm pisze:
>> How do you do it in 2.3.x?
>
>./configure --enable-experimental
>
>
>> Is there a way to specify an OpenSSL ciphers string?
>
>No. It's hardcoded.
OK - could you clarify the behavior with the --enable-experim
Dnia 2014-04-10, czw o godzinie 00:29 +, Joe Malcolm pisze:
> How do you do it in 2.3.x?
./configure --enable-experimental
> Is there a way to specify an OpenSSL ciphers string?
No. It's hardcoded.
Tomasz Sterna writes:
>Dnia 2014-01-13, pon o godzinie 13:29 +0100, MacLemon pisze:
>> I want to disable SSLv3 in favour of TLSv1 only. (Apple jabberd2 is
>> linked against a pre-historic OpenSSL 0.9.8 so it doesn't support TLS
>> 1.2.) I also want to get rid of weak ciphers and try to enable forwa
Dnia 2014-01-13, pon o godzinie 13:29 +0100, MacLemon pisze:
> I want to disable SSLv3 in favour of TLSv1 only. (Apple jabberd2 is
> linked against a pre-historic OpenSSL 0.9.8 so it doesn't support TLS
> 1.2.) I also want to get rid of weak ciphers and try to enable forward
> secrecy handshake nam
I'm looking for a way to configure the cipher suites used by jabberd 2.2.17-399
(The Apple OS X Server 10.8.5 variant of jabberd).
I've checked the Jabberd2 and Apple's documentation and config files with no
useful result.
I only found incomplete hints on to no-ssl-v2 and no-ssl-v3 in jabberd 1
