3 ms·

I'm sure these guys have thought about the longevity of data at rest when selecting the security strengths on the EC curves and RSA keys. These chosen parameter

by dekz 15y ago

I'm sure these guys have thought about the longevity of data at rest when selecting the security strengths on the EC curves and RSA keys. These chosen parameters are quite high and they link to an article which mentions a period of up to 2040 before having to be re-encrypted or expected potentially be broken. Make your own conclusions about that. I'm not certainly a fan of session resumption and renegotiation's from a potential security aspect, anyone care to persuade me apart from a performance standpoint?

marshray 15y ago
Look at it this way: session resumption enables you not start the handshake all over again from scratch for every TCP connection your browser makes. This mean you can actually do more secure things like preferring DHE on the initial handshake because it happens much less often. The session ticket support enables Google to use session resumption across their massively load-balanced SSL terminators. I don't think Google is using renegotiation in this architecture, but I think we got renegotiation nailed down tight with RFC 5746.