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

Consider making *ring* dependency optional #130

Closed
ctz opened this issue Jul 21, 2023 · 1 comment · Fixed by #134
Closed

Consider making *ring* dependency optional #130

ctz opened this issue Jul 21, 2023 · 1 comment · Fixed by #134

Comments

@ctz
Copy link
Member

ctz commented Jul 21, 2023

The ultimate goal here would be to allow use of the webpki crate with other cryptography libraries.

This would come in two parts, I think:

  • replacing remaining references to ring::io -- much of this was already done, but a handful of instances remain.
  • rework SignatureAlgorithm to be a trait that can be implemented outside the crate, with implementations backed by ring being provided by default (eg, ECDSA_P256_SHA256). Alongside, we should export AlgorithmIdentifier and the common values thereof.
@djc
Copy link
Member

djc commented Jul 21, 2023

Could/should we share a signature trait with rustls somehow?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants