New Signing message (Legacy) #1422
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RReichert
force-pushed
the
rodrigor/CLDAPPS-1503-new-signature-message
branch
3 times, most recently
from
ac12a2d to
e767040
Compare
RReichert
force-pushed
the
rodrigor/CLDAPPS-1503-new-signature-message
branch
from
e767040 to
74dc673
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Adding a new "digital signature" message which hopes to replace the "ECDSA Signature" message, the latter is specific to one algorithm whereas the former allows us to introduce additional signature types.
API compatibility
No, this is a new message.
API compatibility plan
N/A
JIRA Reference
https://swift-nav.atlassian.net/browse/CLDAPPS-1503