gitea-mirror/rosenpass
1
0
Fork 0
mirror of https://github.com/rosenpass/rosenpass.git synced 2025-12-12 07:40:30 -08:00
Code Issues Packages Projects Releases Wiki Activity

fix(whitepaper): Inconsistency between implementation and whitepaper about labels for txki/txkr

Browse Source 
Fix of Fig. 5 follows later.
This commit is contained in:
Karolin Varner
2025-08-11 15:18:41 +02:00
parent 221c583508
commit d2a85a0d6b
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
papers/whitepaper.md
View File

@@ -257,7 +257,7 @@ The different labels are:
* `"mix"` – Mixing further values into the chaining key; i.e. into the protocol state.
* `"user"` – Labels for external uses; these are what generate the `osk` (output shared key). See Sec. \ref{symmetric-keys}.
* `"handshake encryption"` – Used when encrypting data using a shared key as part of the protocol execution; e.g. used to generate the `auth` (authentication tag) fields in protocol packages.
* `"initiator session encryption"` and `"responder session encryption"` – For transmission of data after the key-exchange finishes. See Sec. \ref{symmetric-keys}.
* `"initiator handshake encryption"` and `"responder handshake encryption"` – For transmission of data after the key-exchange finishes. See Sec. \ref{symmetric-keys}.
## Hashes
@@ -823,6 +823,8 @@ Changes, in particular:
\end{quote}
```
9. In the whitepaper we used the labels `"initiator session encryption"` and `"responder session encryption"`, but in the implementation we used `"initiator handshake encryption"` and `"responder handshake encryption"`. While the whitepaper was correct and the implementation was not, we opt to harmonize the whitepaper with the implementation to avoid a breaking change.
#### 2025-06-24 – Specifying the `osk` used for WireGuard as a protocol extension
\vspace{0.5em}