News for hackers. Stuff that matters.

A comment on OpenSSL Security Advisory. Parent comment

Re:OpenSSL Security Advisory by peterwwillis on Thursday June 05, 2014 @11:24AM (#7852382)
Since tls-auth merely creates an HMAC around all the TLS message types, it makes me wonder if there's still an aspect of initiating a TLS connection (or flaws in the HMAC generation?) that could leave tls-auth vulnerable to future TLS-related flaws. But that could be excessive paranoia.
[ Parent | on HN ]
Re:OpenSSL Security Advisory by agwa on Thursday June 05, 2014 @12:58PM (#7852835)
I think that whether tls-auth protects you against CCS Injection will hinge not on the HMAC but on tls-auth's replay protection. An attacker can always replay a previously-sniffed CCS packet with a valid HMAC, so it all comes down to whether that replay will be properly discarded.
[ Parent | on HN ]
Re:OpenSSL Security Advisory by JoachimSchipper on Thursday June 05, 2014 @03:03PM (#7853595)
tls-auth does prevent replays: note the "packet-id for replay protection" at http://openvpn.net/index.php/open-source/documentation/secur....

OpenVPN does a pretty good job, as long as you choose a sane configuration (most importantly, use tls-auth and TLS key negotiation). It's definitely less vulnerable than other TLS stuff due to the tls-auth option.

(Full disclosure: my company provides the hardened OpenVPN-NL, and I've done a little work on that.)

[ Parent | on HN ]