-
Notifications
You must be signed in to change notification settings - Fork 6
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
[Spec] Signature Format Criteria #6
Comments
Need to update the spec, so we can close this item. Documenting some of the minimum items we have agreed on in the past. These should go in the spec, and being documented here after discussing with the NV2 group on 4/28.
|
Milind - Could you do a PR on this. Once merged, I can close this and the related roadmap item #5 |
@iamsamirzon what do we need to do in rc.1 for this issue? |
I believe just a simple PR on the spec with a final version of the hackmd.doc referenced above. |
@vaninrao10 how do we move forward on this issue since it is planned in rc.2 |
@toddysm , @vaninrao10 , @FeynmanZhou , @yizha1 - Based on RC-2 discussion in today's Notary v2 meeting, I am pushing back this item from the RC-2 roadmap into the backlog. |
Summary
This must be met by any signature format that Notary V2 will use; The Release candidate signature must meet this requirement
Intended Outcome
The specfication PR is merged
Additional context
It is likely that the Signature format used in the Alpha release will not meet all the criteria
The text was updated successfully, but these errors were encountered: