network profile
| bio | website | polarssl.org |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 6 months |
| seen | Jan 23 at 10:57 | |
| stats | profile views | 0 |
Lead maintainer for the SSL library PolarSSL.
Tech enthusiast, angel investor, crypto-nerd..
|
Dec 20 |
comment |
If two endpoints establish a mutual authenticated connection (TLSv1.0) is the medium between the endpoints a concern? Thanks @SteelCityHacker. You are correct.. |
|
Dec 20 |
answered | If two endpoints establish a mutual authenticated connection (TLSv1.0) is the medium between the endpoints a concern? |
|
Dec 19 |
awarded | Supporter |
|
Dec 18 |
answered | help understanding client certificate verification |
|
Dec 18 |
comment |
BEAST: IIS6: Failing PCI scan - are these ciphers OK? Agreed that splitting would at least solve the ability of the server side to support TLS1.1 and TLS1.2 and make the fact that IIS6 does not support it irrelevant. |
|
Dec 17 |
comment |
BEAST: IIS6: Failing PCI scan - are these ciphers OK? I agree that depending on the situation it's not worth the effort :) |
|
Dec 16 |
comment |
BEAST: IIS6: Failing PCI scan - are these ciphers OK? GlennG, The BEAST attack is not a theoretical risk. The issue is with CBC ciphersuites under TLS 1.0 and is definitely a vulnerability. Putting the RC4 ciphersuites first in the order helps most clients.. And the TLS_RSA_WITH_3DES_EDE_CBC_SHA is then for clients not supporting RC4 ciphersuites. Solves the problem for almost all clients, still gives a warning on the SSL Labs check of course.. |
|
Dec 14 |
awarded | Teacher |
|
Dec 14 |
answered | BEAST: IIS6: Failing PCI scan - are these ciphers OK? |
