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

Deprecate Asymmetric Signature and Verification Contexts #3659

Closed
reaperhulk opened this issue Jun 2, 2017 · 2 comments · Fixed by #3663
Closed

Deprecate Asymmetric Signature and Verification Contexts #3659

reaperhulk opened this issue Jun 2, 2017 · 2 comments · Fixed by #3663

Comments

@reaperhulk
Copy link
Member

I think we should deprecate these contexts (probably an extended deprecation cycle since it's likely that these APIs are used quite a bit) and steer people exclusively to using the one-shot sign/verify APIs. As part of this we can expand the documentation on Prehashed to show an example of how you can incrementally hash a large file and then pass that hash to the one-shot APIs. Hooray composition.

refs #3656 and #3658

@alex
Copy link
Member

alex commented Jun 2, 2017

This seems good, and facilitates better uptake of eddsa signatures.

@alex
Copy link
Member

alex commented Jun 2, 2017

(This will have to be a very extended deprecation, it goes without saying)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

Successfully merging a pull request may close this issue.

2 participants