From 448ce6b3959efdee3eadc3fe33ab59c9ff910c9e Mon Sep 17 00:00:00 2001 From: Karolin Varner Date: Tue, 3 Oct 2023 13:49:45 +0200 Subject: [PATCH] feat(whitepaper): Detailed info about when security properties are achieved --- papers/whitepaper.md | 1 + 1 file changed, 1 insertion(+) diff --git a/papers/whitepaper.md b/papers/whitepaper.md index b61aefc..2f3e7e5 100644 --- a/papers/whitepaper.md +++ b/papers/whitepaper.md @@ -467,6 +467,7 @@ During the implementation of go-rosenpass, Steffen Vogel found a number of probl - Handle race conditions when both peers complete concurrent handshakes in switched roles. Backwards compatible. Initially addressed in [397a776](https://github.com/rosenpass/rosenpass/commit/397a776c55b1feae1e8e5aceef01cf06bf56b6ed) "fix: Race condition due to concurrent handshake" - Explicitly erase `eski` (forward secrecy). This is a minor security fix: Before this change the specification left erasing the secret key to the implementation. The reference implementation did erase `eski` but only after receiving the responder confirmation package (EmptyData at the time) instructing the initiator to stop retransmission of the InitConf package. With this change, `eski` is erased before transmission of the InitConf package. +- Add detailed information about when in the handshake process security properties are achieved. ## Protocol version 1 -- 2023-03-04