fix(registry): correct TUAK naming and bcrypt pattern syntax #751
+3
−3
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
Signed-off-by: Mehrn0ush <mehrnoush.vaseghi@gmail.com>
Mehrn0ush
force-pushed
the
fix/crypto-registry-typos
branch
from
e7d7612 to
501135d
Compare
Member
|
cc: @bhess |
bhess
approved these changes
Jan 5, 2026
Contributor
bhess
left a comment
bhess
left a comment
There was a problem hiding this comment.
Looks good to me!
Thank you @Mehrn0ush for reviewing and correcting the entries.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
As discussed in ticket #750, this PR fixes data-quality issues in the Cryptography Registry.
Fixes #750
Details
bcrypt[-{cost)]→bcrypt[-{cost}])