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

Fix failure to parse enveloped data in Go 1.10 #59

Merged
merged 1 commit into from
Jul 28, 2021

Conversation

g-k
Copy link

@g-k g-k commented Jul 28, 2021

Go 1.10 is more strict about Asn.1 annotations. This removes the incorrect “explicit” annotation from encryptedContentInfo.EncryptedContent.

I’m also using openssl to generate the fixture now so that we aren’t testing with our own output for Decrypt()

Rebase #40 and cherry-pick of upstream fullsailor@cddbb99

Fixes #37

Go 1.10 is more strict about Asn.1 annotations. This removes the incorrect “explicit” annotation from encryptedContentInfo.EncryptedContent.

I’m also using openssl to generate the fixture now so that we aren’t testing with our own output for `Decrypt()`

Cherry-pick upstream fullsailor@cddbb99
@g-k g-k marked this pull request as ready for review July 28, 2021 13:51
@g-k g-k merged commit 947daa5 into master Jul 28, 2021
@g-k g-k deleted the asn1-optional-encryptedcontent branch July 28, 2021 13:53
hslatman added a commit to hslatman/certificates that referenced this pull request Sep 16, 2021
This includes the fix as described in mozilla-services/pkcs7#59,
which was the reason a fork of the library was used.
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.

asn.1: EncryptedContent should not be marked explicit
2 participants