Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support verifying legacy DSA signatures in Go 1.16 #50

Closed
wants to merge 1 commit into from

Conversation

cmars
Copy link

@cmars cmars commented Mar 9, 2021

Go 1.16 removed support for DSA signatures from crypto/x509. This change
gives those applications that need to verify legacy PKCS7 certificates,
a little more time to migrate off of DSA.

Fixes #47

Go 1.16 removed support for DSA signatures from crypto/x509. This change
gives those applications that need to verify legacy PKCS7 certificates,
a little more time to migrate off of DSA.
@g-k
Copy link

g-k commented Jul 22, 2021

Thanks! Closing in favor of #55 for the reasons mentioned in my PR there.

@g-k g-k closed this Jul 22, 2021
jcharum pushed a commit to grailbio/base that referenced this pull request Jun 2, 2022
Summary:
AWS Identity Documents are signed with DSA-with-SHA1 signatures, and DSA is
removed from x509/crypto as of Go 1.16. This follows an approach done
by hashicorp/vault#12340, by forking in
https://github.com/mozilla-services/pkcs7 and applying the DSA fix
mozilla-services/pkcs7#50.

Test Plan: - Tested Bazel build and go build from within the folder

Reviewers: aeiser, dborcherding, sdunn, anguyen, gvitta, bbentson

Reviewed By: dborcherding, sdunn

Subscribers: jcharumilind, dnicolaou, pboyapalli, smahadevan

Differential Revision: https://phabricator.grailbio.com/D66326

fbshipit-source-id: cafa39b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Go 1.16: TestVerifyEC2 failure
2 participants