Fix `extract-openssl-digest' to handle non-prefixed openssl output - #32
Merged
Conversation
Usually the output of `openssl dgst` looks like this: SHA1(install.sh)= a708a8b6996a18c3aed1d9d909f9c52477c72fba But on some systems the prefix is missing and it seems that the digest is already passt to `extract-openssl-digest'. In that case we simply return the output without any processing.
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
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.
Usually the output of
openssl dgstlooks like this:SHA1(install.sh)= a708a8b6996a18c3aed1d9d909f9c52477c72fba
But on some systems the prefix is missing and it seems that the digest is already passed to
extract-openssl-digest. In that case we simply return the output without any processing.Fixes #31