-
Notifications
You must be signed in to change notification settings - Fork 3
Use Serialized Key Length for Serialization outputs #17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we use SerializedKey
directly instead of the constant, this should work before and after trussed-dev/trussed#200.
Co-authored-by: Robin Krahl <[email protected]>
Co-authored-by: Robin Krahl <[email protected]>
Co-authored-by: Robin Krahl <[email protected]>
@KyleKotowick Looks good, thank you! Can you please squash the changes into the original commit? |
When you merge the PR, you can just choose "Squash Merge", no? |
You are right, a squash merge would work in this case, but generally we try to avoid it to keep the structure of multi-commit PRs intact and to keep the signatures on the commits. Anyway, please rebase onto main to fix the CI. |
@robin-nitrokey It's now up-to-date with |
Merged via #19. |
No description provided.