Repository navigation
Make the crypto module doc match the code on the supported schemes and where the EncryptionInfo is - #165
Merged
Conversation
…d where the EncryptionInfo is - List Standard AES among the supported schemes - Say that 0x299 holds the length of the EncryptionInfo and that the EncryptionInfo starts at 0x29B - Drop from the comment of ENCRYPTION_INFO_OFFSET that it is for Agile Encryption, as every scheme has it Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
CoverageFor 505e582. |
This file contains hidden or 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
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.
Summary
ENCRYPTION_INFO_OFFSETin format.rs said the offset is for Agile Encryption; the length is read there for every scheme, before the scheme is known.🤖 Generated with Claude Code