what_the_diffie

If end-to-end sec (e.g., crypto signatures) are used, like say with Debian packages which uses GPG, packages and metadata can be released over http without a problem.

Give it a few minutes, someone will make an OCR to ASCII art app.

Also, openssl didn't (or doesn't) appear to care about high-reliability software engineering and the IETF TLS Working Group didn't care about producing a minimum-featured spec that is not overly difficult to implement, maintain and support in the real world. Instead, TLS has become a kitchen-sink, feature-hoarding, experiment-in-production jambalaya.

It's hard to tell from the paper, because they don't include either specific build version numbers of browsers / servers nor date of publication, so their results are difficult (e.g., impossible) to reproduce exactly.

0: https://weakdh.org/imperfect-forward-secrecy.pdf

These major browsers (latest stable on OS X) are currently vulnerable:

- Chrome 43.0.2357.124

- Firefox 38.0.5

- Safari 8.0.6 (10600.6.3)

Not vulnerable

- Opera 30.0.1835.59

Reference: https://www.ssllabs.com/ssltest/viewMyClient.html