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

fixes #138: adds and implements a CryptographyProvider trait #142

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mozkeeler
Copy link
Collaborator

Was this the sort of thing you were thinking? It's still a bit of a work in progress - e.g. the right build flags aren't there.

@mozkeeler mozkeeler requested a review from jcjones November 7, 2020 00:05
Copy link
Contributor

@jcjones jcjones left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd say that this is going the right places, and I'd merge it right as-is, though we'd have to make ring an optional dependency before the next uplift to m-c.

I think we'll find that we need a richer interface for getting a dyn Key in/out than what's here, but that's an OK start, and nothing here would run afoul of patterns in NSS.

@@ -51,6 +51,7 @@ serde = { version = "1.0", optional = true, features = ["derive"] }
serde_json = { version = "1.0", optional = true }
bytes = { version = "0.5", optional = true, features = ["serde"] }
base64 = { version = "^0.10", optional = true }
ring = "0.16"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gonna have to be a feature I think

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 this pull request may close these issues.

2 participants