Forward Secrecy for Google HTTPS

Re:Forward Secrecy for Google HTTPS by stock_toaster on Tuesday November 22, 2011 @06:10PM (#3267876)

The post made it sound like just the bugfixes are in 1.0.0e, but the performance improvements may have not been accepted yet. I wonder if that is the case?

This is good to see, and I really appreciate the work google has put into making tls/ssl more pervasive.

I do wonder about the performance differences between their faster DHE implementation and what they were using before (RSA-RC4-SHA). I wish they had provided a bit of data on that.

[ Parent | on HN ]

Re:Forward Secrecy for Google HTTPS by tptacek on Tuesday November 22, 2011 @07:45PM (#3268171)

It kind of has to be less performant, just because ECDHE uses more bignum crypto primitives.

[ Parent | on HN ]

Re:Forward Secrecy for Google HTTPS by stock_toaster on Tuesday November 22, 2011 @08:35PM (#3268343)

Yeah, that makes sense.

I was mostly curious about how much faster their new implementation was over the old, and how much slower it was than RSA-RC4-SHA.

[ Parent | on HN ]

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

I think that with the session resumptions they got by using session tickets, this could easily end up being a net gain for them.

[ Parent | on HN ]