k12: Implement KT256 #756
Open
k12: Implement KT256 #756
Conversation
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
Implement KT256 as specified in RFC 9861. Also, rename existing types to KT128 in accordance with RFC 9861 (e.g. `KangarooTwelveReader` to `Kt128Reader`).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 implement KT256 as specified in RFC 9861 for the
k12crate.Also, rename existing types (
KangarooTwelve*) toKt128*(e.g.KangarooTwelveReadertoKt128Reader). This is because the KangarooTwelve instance is specified as the KT128 instance in RFC 9861.1Note
For compatibility reasons, the existing types are defined as deprecated aliases for
Kt128*.Footnotes
https://www.rfc-editor.org/rfc/rfc9861.html#section-1-3 ↩