Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-05-01 14:44:09 +02:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

put steps in a list

Browse source
This commit is contained in:
Hubert Chathi 2023-07-04 17:24:49 -04:00
parent 5485179627
commit f1bc8face6
1 changed files with 26 additions and 26 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
content/client-server-api/modules/end_to_end_encryption.md
View file

@ -777,7 +777,7 @@ The method used to calculate these MACs depends upon the value of the
message. All current implementations should use the `hkdf-hmac-sha256.v2` method which is
defined as follows:
An HMAC key is generated using HKDF, as defined in [RFC
1. An HMAC key is generated using HKDF, as defined in [RFC
5869](https://tools.ietf.org/html/rfc5869), using SHA-256 as the hash
function. The shared secret is supplied as the input keying material. No salt
is used, and in the info parameter is the concatenation of:
@ -791,7 +791,7 @@ is used, and in the info parameter is the concatenation of:
- The Key ID of the key being MAC-ed, or the string `KEY_IDS` if the
item being MAC-ed is the list of key IDs.
A MAC is then generated using HMAC as defined in [RFC
2. A MAC is then generated using HMAC as defined in [RFC
2104](https://tools.ietf.org/html/rfc2104) with the key generated above and
using SHA-256 as the hash function.
@ -806,7 +806,7 @@ form `{algorithm}:{keyId}`. For example, the key list could look like:
reconstruct the list from the names in the `mac` property of the
`m.key.verification.mac` message and ensure that no keys were added or removed.
The MAC values are base64-encoded and sent in a
3. The MAC values are base64-encoded and sent in a
[`m.key.verification.mac`](#mkeyverificationmac) message.
{{% boxes/note %}}