Re:SSL broken. (TLS 1.0 cryptographic attack that works. ...
by willvarfar on Monday September 19, 2011 @07:23PM
(#3015615)
It claims to be a practical working attack, and it says they haven't found a practical solution. The title accurately reflects how I interpret the gist of the situation.
[ Parent
| on HN ]
Re:SSL broken. (TLS 1.0 cryptographic attack that works. ...
by dekz on Monday September 19, 2011 @07:28PM
(#3015622)
This attack could only be potentially practical against web browsers, not other applications implementing TLS.
Re:SSL broken. (TLS 1.0 cryptographic attack that works. ...
by aclimatt on Monday September 19, 2011 @07:29PM
(#3015628)
They claim to also be able to perform the attack on other applications using TLS (such as VPNs), not just web browsers.
Re:SSL broken. (TLS 1.0 cryptographic attack that works. ...
by dekz on Monday September 19, 2011 @08:02PM
(#3015709)
Quite possibly, but this is about BEAST and the ability of loading malicious Javascript. Performing the feat of code injection on a non-browser application is something completely different. If something is injecting code into your native application or throwing known plaintext into your socket streams then you've already been compromised.
Re:SSL broken. (TLS 1.0 cryptographic attack that works. ...
by dfox on Monday September 19, 2011 @08:34PM
(#3015768)
You don't need to inject code, you need to inject traffic. Injecting code into client is only one way to do that. For example in many VPN deployments you can inject traffic into secure channel directly.