Comment on The POODLE bites againComments−resonantcore11yWe look forward to TLS 1.2 support being the norm. (And then, hopefully, the ratification and adoption of TLS 1.3)A 50% adoption rate is excellent news. Still a long way to go, but that's worth toasting over.−yuhong11yWhat is frustrating is how many such servers have TLS 1.3 intolerance (even PayPal), and often the same servers are also affected by this bug. I wonder what TLS implementation is this.−feld11yTLS 1.3 isn't finished yet...−yuhong11yI know, the goal is to prepare.−feld11yI'm not sure what you mean then by servers having TLS 1.3 intolerance.−yuhong11yIt does not respond properly to clients trying to negotiate TLS 1.3. It should return a ServerHello showing the supported TLS 1.2 version.−feld11yI wasn't aware there was a TLS 1.3 PoC that people could use for testing.−yuhong11yIt is as simple as setting the version in the ClientHello message.−feld11yOh, I see
Comments
We look forward to TLS 1.2 support being the norm. (And then, hopefully, the ratification and adoption of TLS 1.3)
A 50% adoption rate is excellent news. Still a long way to go, but that's worth toasting over.
What is frustrating is how many such servers have TLS 1.3 intolerance (even PayPal), and often the same servers are also affected by this bug. I wonder what TLS implementation is this.
TLS 1.3 isn't finished yet...
I know, the goal is to prepare.
I'm not sure what you mean then by servers having TLS 1.3 intolerance.
It does not respond properly to clients trying to negotiate TLS 1.3. It should return a ServerHello showing the supported TLS 1.2 version.
I wasn't aware there was a TLS 1.3 PoC that people could use for testing.
It is as simple as setting the version in the ClientHello message.
Oh, I see