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

Require deserialized RAMF messages to use allowed cryptographic algorithms only #27

Open
gnarea opened this issue Dec 6, 2019 · 0 comments
Open

Require deserialized RAMF messages to use allowed cryptographic algorithms only #27

gnarea opened this issue Dec 6, 2019 · 0 comments
Assignees
@gnarea
Milestone
Production release

Comments

@gnarea
Copy link
Member

gnarea commented Dec 6, 2019 •
edited

Per RS-018.

For example, PKI.js supports SHA-1, but RS-018 disallows it.
@gnarea gnarea self-assigned this Dec 6, 2019
@gnarea gnarea added this to To do in relaynet-core-js v1.0 Alpha 1 via automation Dec 6, 2019
@gnarea gnarea added this to the Production release milestone Feb 10, 2020
@gnarea gnarea changed the title Enforce requirements on CMS SignedData and EnvelopedData values Require deserialized RAMF messages to use allowed cryptographic algorithms Mar 27, 2020
@gnarea gnarea mentioned this issue Mar 27, 2020
Open
@gnarea gnarea changed the title Require deserialized RAMF messages to use allowed cryptographic algorithms Require deserialized RAMF messages to use allowed cryptographic algorithms only Mar 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gnarea gnarea

Labels
None yet
Projects
None yet
Milestone
Production release
Development

No branches or pull requests
1 participant
@gnarea