Skip to content

Commit

Permalink
sas: clarify HKDF calculation uses base64-encoded keys
Browse files Browse the repository at this point in the history
Signed-off-by: Sumner Evans <sumner@beeper.com>
  • Loading branch information
sumnerevans committed Jan 30, 2024
1 parent 9a5cacd commit 9b78c49
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 4 deletions.
1 change: 1 addition & 0 deletions changelogs/client_server/newsfragments/1719.clarification
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Clarify that the HKDF calculation for SAS uses base64-encoded keys rather than the raw key bytes.
8 changes: 4 additions & 4 deletions content/client-server-api/modules/end_to_end_encryption.md
Original file line number Diff line number Diff line change
Expand Up @@ -836,15 +836,15 @@ is the concatenation of:
- The Device ID of the device which sent the
`m.key.verification.start` message, followed by `|`.
- The public key from the `m.key.verification.key` message sent by
the device which sent the `m.key.verification.start` message,
followed by `|`.
the device which sent the `m.key.verification.start` message, encoded as
unpadded base64, followed by `|`.
- The Matrix ID of the user who sent the `m.key.verification.accept`
message, followed by `|`.
- The Device ID of the device which sent the
`m.key.verification.accept` message, followed by `|`.
- The public key from the `m.key.verification.key` message sent by
the device which sent the `m.key.verification.accept` message,
followed by `|`.
the device which sent the `m.key.verification.accept` message, encoded as
unpadded base64, followed by `|`.
- The `transaction_id` being used.

When the `key_agreement_protocol` is the deprecated method `curve25519`,
Expand Down

0 comments on commit 9b78c49

Please sign in to comment.