Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix two links to the psk section which were missing # #44

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+2 −2
Open

Fix two links to the psk section which were missing # #44

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions noise.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -570,7 +570,7 @@ remove options, Alice and Bob could include the list as prologue data.
Note that while the parties confirm their prologues are identical, they don't
mix prologue data into encryption keys. If an input contains secret data that’s
intended to strengthen the encryption, a PSK handshake should be used
instead (see [Section 9](pre-shared-symmetric-keys)).
instead (see [Section 9](#pre-shared-symmetric-keys)).


# 7. Handshake patterns
Expand All @@ -581,7 +581,7 @@ A **message pattern** is some sequence of tokens from the set `("e", "s", "ee",
"es", "se", "ss", "psk")`. The handling of these tokens within
`WriteMessage()` and `ReadMessage()` has been described previously, except for
the `"psk"` token, which will be described in [Section
9](pre-shared-symmetric-keys). Future specifications might introduce other
9](#pre-shared-symmetric-keys). Future specifications might introduce other
tokens.

A **pre-message pattern** is one of the following sequences of tokens:
Expand Down