Forward Secrecy for Google HTTPS

Re:Forward Secrecy for Google HTTPS by 101001010111 on Tuesday November 22, 2011 @02:57PM (#3267073)

I am not a cypherpunk, but can/should we differentiate between 1. encouraging those running OpenSSL/TLS servers to use a. sane defaults that allow forward secrecy and b. ephemeral TLS session ticket keys, 2. using Google's in-house EC cipher implementations and 3. doing 1. and 2.?

We could do 1. only and still reap some benefit, correct?

[ Parent | on HN ]

Re:Forward Secrecy for Google HTTPS by tptacek on Tuesday November 22, 2011 @03:23PM (#3267171)

There are environments where ephemeral DH keys violate policy (those sessions can't be passively monitored; some sessions must be), which could militate against PFS suites becoming the default.

DHE is good, but I'm not sure forward secrecy is as pressing a security issue as simple adoption of TLS is. I admire Google's continued efforts to set the standard for its secure deployment, though.

[ Parent | on HN ]

Re:Forward Secrecy for Google HTTPS by marshray on Wednesday November 23, 2011 @12:25AM (#3268885)

Look at it from Google's point of view though:

Now they won't have "lawfully intercepted" packet captures showing up in their mailbox with demands that they decrypt them using their private key.

[ Parent | on HN ]

Re:Forward Secrecy for Google HTTPS by benblack on Tuesday November 22, 2011 @03:06PM (#3267100)

Correct!

[ Parent | on HN ]