Skip to content

Commit

Permalink
Merge pull request #849 from matheusd/onion-nonce-size
Browse files Browse the repository at this point in the history
Clarify nonce size for onion cipher
  • Loading branch information
Roasbeef authored Mar 2, 2021
2 parents 9046803 + ffa0a3c commit 946bbeb
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions 04-onion-routing.md
Original file line number Diff line number Diff line change
Expand Up @@ -78,8 +78,8 @@ There are a number of conventions adhered to throughout this document:
- Elliptic curve: for all computations involving elliptic curves, the Bitcoin
curve is used, as specified in [`secp256k1`][sec2]
- Pseudo-random stream: [`ChaCha20`][rfc8439] is used to generate a
pseudo-random byte stream. For its generation, a fixed null-nonce
(`0x0000000000000000`) is used, along with a key derived from a shared
pseudo-random byte stream. For its generation, a fixed 96-bit null-nonce
(`0x000000000000000000000000`) is used, along with a key derived from a shared
secret and with a `0x00`-byte stream of the desired output size as the
message.
- The terms _origin node_ and _final node_ refer to the initial packet sender
Expand Down Expand Up @@ -127,7 +127,7 @@ The pseudo-random byte stream is used to obfuscate the packet at each hop of the
path, so that each hop may only recover the address and HMAC of the next hop.
The pseudo-random byte stream is generated by encrypting (using `ChaCha20`) a
`0x00`-byte stream, of the required length, which is initialized with a key
derived from the shared secret and a zero-nonce (`0x00000000000000`).
derived from the shared secret and a 96-bit zero-nonce (`0x000000000000000000000000`).

The use of a fixed nonce is safe, since the keys are never reused.

Expand Down

0 comments on commit 946bbeb

Please sign in to comment.