News for hackers. Stuff that matters.
Re:NSA admits listening to U.S. phone calls without warrants by gojomo on Saturday June 15, 2013 @08:46PM (#5886854)
You keep confidently asserting that, but many of the exact same compartmentalization and security procedures which protect the private keymatter also make a secret private key disclosure easier to keep hidden.

How would we know otherwise?

As you note, that "would be a more outrageous and damning discovery" - so there's more incentive to keep it closely held. It would help the NSA do what it feels it must, simply by using its other network taps. And, it would help minimize the risk of discovery without involving extra employees and ongoing connections, all while retaining the ability for Page/Drummond/etc to deny involvement.

Those add up to making a key compromise more attractive for NSA and Google than the alternatives.

Re:NSA admits listening to U.S. phone calls without warrants by kniht on Saturday June 15, 2013 @09:08PM (#5886936)
TLS client authentication allows the server to detect when an active MITM attempts to get into the connection[1]. This means that if you hold the theory that the NSA is acting as a MITM with Google's private keys, you also have to assume that they know they'll be detected the second anyone tries to use a client certificate to connect.

[1] http://security.stackexchange.com/questions/26142/do-client-...

Re:NSA admits listening to U.S. phone calls without warrants by sneak on Wednesday June 19, 2013 @08:44AM (#5905150)
If you have the key from the server, and it's not using a cipher suite that supports forward secrecy, then you do not need to actively MITM to decrypt the traffic. All you need is the long term key and the intercepts. You can then decrypt the session key from the initial connection setup.

This is why the DHE/EDH modes exist. It uses DH to agree on a session key, then uses the long term key just to ensure the DH agreement hasn't been actively mitm'd. The session key is never transmitted or permanently stored, so once the connection cache expires, nobody can decrypt retroactively, not even the parties to the conversation.