Cryptography nerds: How would you describe the forward secrecy properties of a protocol where receivers publish DH shares to a discovery service, along with an AES encrypted cookie of what the secret component is. Receivers hold the AES key and revoke/rotate it every 24 hours.
-
-
What’s stopping you from generating a unique AES key per DH share? Why bundle them under a single key?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.