On Thu, Feb 16, 2012 at 09:01:53AM -0500, Joe Bogner wrote:
> It mentions being vulnerable to BEAST and offers this link
> https://community.qualys.com/blogs/securitylabs/2011/10/17/mitigating-the-beast-attack-on-tls
This says:
In terms of mitigation, I expect this problem will be largely
addressed on the client side, despite a potential compatibility
problem that may cause some TLS sites to stop working. The only
reliable way to defend against BEAST is to prioritise RC4 cipher
suites, as proposed by PhoneFactor.
Just as an example, here's one way to do the above in Apache:
SSLHonorCipherOrder On
SSLCipherSuite RC4-SHA:HIGH:!ADH
Without real comprehension, I inserted into "src/httpGate.c"
SSL_CTX_set_cipher_list(ctx, "RC4-SHA:HIGH:!ADH")
so that the total change is now:
177c177
< if (!(ctx = SSL_CTX_new(SSLv23_server_method())) ||
---
> if (!(ctx = SSL_CTX_new(SSLv3_server_method())) ||
180c180,181
< !SSL_CTX_check_private_key(ctx)
) {
---
> !SSL_CTX_check_private_key(ctx) ||
> !SSL_CTX_set_cipher_list(ctx, "RC4-SHA:HIGH:!ADH") ) {
I don't know if this helps, though (as I can't reproduce the problem).
The ssllabs.com analyzer still complains, though.
Cheers,
- Alex
--
UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe