From c73bc5d8b7cf4705f074cb098466fe6ed536318d Mon Sep 17 00:00:00 2001 From: Yusef Napora Date: Thu, 9 May 2019 14:33:21 -0400 Subject: [PATCH] small fix --- secio/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/secio/README.md b/secio/README.md index e7eed1c..e5bd916 100644 --- a/secio/README.md +++ b/secio/README.md @@ -193,7 +193,7 @@ The peers serialize their `Exchange` messages and write them over the wire. Upon receiving the remote peer's `Exchange`, the local peer will compute the remote peer's expected `corpus` using the known proposal bytes and the ephemeral public key sent by the remote peer in the `Exchange`. The `signature` can then be validated using the -permanent public key of the remote peer obtained in the initial `Proposal`. +permanent public key of the remote peer obtained in the initial proposal. Peers MUST close the connection if the signature does not validate. @@ -318,7 +318,7 @@ The first packet transmitted by each peer must be the remote peer's nonce. Each peer will decrypt the message body and validate the HMAC signature, comparing the decrypted output to the nonce recieved in the initial -`Proposal` message. If either peer is unable to validate the initial +`Propose` message. If either peer is unable to validate the initial packet against the known nonce, they must abort the connection. If both peers successfully validate the initial packet, the secure channel has