Add SP800-38E limitation #7558
Closed
Add SP800-38E limitation #7558
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
kaleb-himes
force-pushed
the
SRTP-KDF-OPTESTr2
branch
from
b2201da
to
db013c6
Compare
|
Mr @douzzer is working on a way to track the bytes protected by a given key for the streaming service APIs and will push an update to this PR when ready. |
|
See #7560 -- the API change for AES-XTS-stream to support this req wound up having the customary mushrooming impact on the related test+shim code, so I put it up as its own PR that supersedes this one. Thanks @kaleb-himes for driving visiblity around the SP800-38E req! |
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.
Description
Addresses limitation imposed on amount of data that can be protected by a give XTS key per SP800-38E.
Testing
FIPS compliance review
Checklist