sodium_crypto_sign* always produce non-empty-string#1985
Merged
ondrejmirtes merged 1 commit intophpstan:1.9.xfrom Nov 8, 2022
Slamdunk:sodium_crypto_sign
Merged
sodium_crypto_sign* always produce non-empty-string#1985ondrejmirtes merged 1 commit intophpstan:1.9.xfrom Slamdunk:sodium_crypto_sign
sodium_crypto_sign* always produce non-empty-string#1985ondrejmirtes merged 1 commit intophpstan:1.9.xfrom
Slamdunk:sodium_crypto_sign
Conversation
Member
|
Thank you. |
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.
By design
libsodiumnever produce or allow consumption of empty keys or an empty signature.That's true for basically all
sodium_*functions, but I prefer to propose here PRs only for what I know and I have first hand experience on.