3 ms·
> Access to the master keys for a SSL/TLS session isn't like that at all. They could retroactively capture, archive, and decrypt any traffic to the site at all
by nwh 13y ago
> Access to the master keys for a SSL/TLS session isn't like that at all. They could retroactively capture, archive, and decrypt any traffic to the site at all with nothing but the undetectable network taps we already believe they have.
They can't in every case, especially for Google, who use a newer SSL that supports perfect forward secrecy. You are completely correct in the differing magnitudes of attack detectability though.
- roc 13y agoThat's only true of Google traffic as of late 2011. So historical SSL data captured anywhere between, say 2002 - 2011, could still be decrypted with these keys, right?
- nwh 13y agoRight. I believe that Google has changed them several times even in the last few years though, so it could be that even they don't have access to the old static keys anymore.
- EGreg 13y agoAre there good links you can recommend for implementing SSL with perfect forward secrecy?
- 23david 13y agothis one seemed fine. worked for me: https://community.qualys.com/blogs/securitylabs/2013/06/25/ssl-labs-deploying-forward-secrecy https://community.qualys.com/blogs/securitylabs/2013/06/25/s...