Understanding Advanced Secrecy

I recently pointed out to a friend from a friend who said that Google is moving in the direction of secrecy. From what I understand, the essence of hidden secrecy seems to be that private keys are not stored in persistent storage.

I have various doubts about how something like this can be implemented.

  • What if the server drops without warning - do I need to rebuild the key pairs? Do I need to publish the key again to create another certificate?
  • Can someone please point me to the / pdf messages where the implementation of something like this is described. Recommended reading resources?
  • Do you know anyone who has implemented direct secrecy? Have you tried something like this in your workplace?

Thank!

+5
source share
2 answers

There are still long-term keys in Forward Secrecy . The only consequence is that compromising a long-term key will not allow an attacker to violate temporary session keys when changing a long-term key. This means that the long-term key should not be inferred from another (older) key.

Here is a good overview on this topic.

According to Wikipedia :

  • PFS is an optional feature in IPsec (RFC 2412).
  • Ssh.
  • Out-of-office messaging, a cryptographic protocol, and a library for many instant messaging clients provide excellent direct confidentiality as well as forbidden encryption.
  • , Transport Layer Security SSLv3, PFS .
+4

TLS Diffie-Hellman (DH). Vanilla DH , , . TLS , RSA.

TLS ciphersuites, PFS, , . TLS PFS, , , PFS CPU.

+1

All Articles