Data volume #372
Closed
Data volume #372
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I included limitations on the amount of data to send, for AES-GCM and ChaCha20-Poly1305. We don't seem to have rekeying capabilities in this branch, but some editing should fix that.
Include data volume limitations
| under one set of keys. For the AES-GCM ciphersuites this limit is | ||
| 2^36 bytes. For ChaCha20-Poly1305 this limit is larger then the size of the | ||
| nonce, and so does not matter. Implementations MUST NOT transmit more than | ||
| 2^36 bytes (64 GiB) encrypted under a single key and MUST rekey (See {{key-update}} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I de-merged this because I'm not sure if we really want to have the same hard limit for ChaCha as for GCM.