summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuke-Jr <luke_github1@dashjr.org>2016-07-27 17:02:54 +0000
committerGitHub <noreply@github.com>2016-07-27 17:02:54 +0000
commit0e3f9df4124bc0f52556dcdb21c6d6dda083b294 (patch)
treea207e2d170e5c946cb10950ff97e9f4cc90b4bd7
parent2ac0b472da770dc807eaab94ed2394d2145961f9 (diff)
parent0607a34fcfd139f02a9232449f88cdd3501d9a18 (diff)
downloadbips-0e3f9df4124bc0f52556dcdb21c6d6dda083b294.tar.xz
Merge pull request #426 from chjj/bip151-aadseq
BIP151: Clarifications on sequence numbers.
-rw-r--r--bip-0151.mediawiki4
1 files changed, 2 insertions, 2 deletions
diff --git a/bip-0151.mediawiki b/bip-0151.mediawiki
index cc79712..a4c8b8e 100644
--- a/bip-0151.mediawiki
+++ b/bip-0151.mediawiki
@@ -128,7 +128,7 @@ Processing the message before the authentication succeeds must not be done.
The 4byte sha256 checksum is no longer required because the AEAD.
-Both peers need to track the message number (int64) of sent messages to the remote peer for building a symmetric cipher IV. Padding might be required (96bit IVs).
+Both peers need to track the message sequence number (uint32) of sent messages to the remote peer for building a 64 bit symmetric cipher IV. Sequence numbers are allowed to overflow to zero after 4294967295 (2^32-1).
The encrypted payload will result decrypted in one or many unencrypted messages:
@@ -156,7 +156,7 @@ The Re-Keying must be done after every 1GB of data sent or received (recommended
=== Risks ===
-The encryption does not include an identity authentication scheme. This BIP does not cover a proposal to avoid MITM attacks during the encryption initialization.
+The encryption does not include an identity authentication scheme. This BIP does not cover a proposal to avoid MITM attacks during the encryption initialization.
Identity authentication will be covered in another BIP and will presume communication encryption after this BIP.