mirror of
https://github.com/bitcoin/bips.git
synced 2025-03-04 19:16:28 +01:00
Merge pull request #426 from chjj/bip151-aadseq
BIP151: Clarifications on sequence numbers.
This commit is contained in:
commit
0e3f9df412
1 changed files with 2 additions and 2 deletions
|
@ -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.
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue