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.

Sign up for GitHub

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

Jump to bottom

EnvelopedData: SubjectKeyIdentifier shouldn't be allowed as a recipient key id #59

Open
gnarea opened this issue Mar 30, 2020 · 1 comment
Open

EnvelopedData: SubjectKeyIdentifier shouldn't be allowed as a recipient key id #59

gnarea opened this issue Mar 30, 2020 · 1 comment
Labels
bug Something isn't working
Milestone
Production release

Comments

@gnarea
Copy link
Member

gnarea commented Mar 30, 2020

Only IssuerAndSerialNumber should be allowed.

We should enforce this post-deserialization as in the JVM library.
@gnarea gnarea added the bug Something isn't working label Mar 30, 2020
@gnarea gnarea added this to the Production release milestone Mar 30, 2020
@gnarea
Copy link
Member Author

gnarea commented Apr 20, 2020

Or maybe it should be allowed now that PKI.js supports it and Bouncy Castle has always supported it? PeculiarVentures/PKI.js#261

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
Production release
Development

No branches or pull requests
1 participant
@gnarea