Fixed mismatched key length in documentation #42
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
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
copybara-service bot
pushed a commit
that referenced
this pull request
Oct 24, 2025
Fixed mismatched key length in documentation Updated the documentation advertising the creation of a 256-bit key, while the implementation below creates a 128-bit key. Note that in general, there are slight discrepancies between the examples in the developer documentation (https://developers.google.com/tink/) in the different languages, sometimes creating 128-bit keys and 256-bit keys otherwise. Closes ##42 PiperOrigin-RevId: 823507617 Change-Id: I6deacd044f430e5d47a771e870510b57a210e647
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.
Updated the documentation advertising the creation of a 256-bit key, while the implementation below creates a 128-bit key. Note that in general, there are slight discrepancies between the examples in the developer documentation (https://developers.google.com/tink/) in the different languages, sometimes creating 128-bit keys and 256-bit keys otherwise.