verifySignature: always use the certificate's algorithm #28
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.
VerifySignature previously hardcoded x509.SHA1WithRSA as the
verification signature. As of Go 1.10, the x509 package verifies that
the requested algorithm matches the certificate's public key type.
VerifySignature would then fail for certificates with DSA keys, such
as AWS's EC2 instance identity documents.
Fix this by always using the certificate's algorithm directly.