Fix cipher block size as IV length for legacy credential activation#420
Open
hslatman wants to merge 1 commit intogoogle:mainfrom
Open
Fix cipher block size as IV length for legacy credential activation#420hslatman wants to merge 1 commit intogoogle:mainfrom
hslatman wants to merge 1 commit intogoogle:mainfrom
Conversation
josephlr
approved these changes
Dec 17, 2025
Member
josephlr
left a comment
josephlr
left a comment
There was a problem hiding this comment.
Good catch!
Per https://pkg.go.dev/crypto/cipher#NewCFBEncrypter:
The iv must be the same length as the Block's block size.
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
2 participants
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.
This is similar to https://github.com/google/go-tpm/blob/main/tpm2/child_object_crypto.go#L46, but for the
legacy/tpm2package.