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

Allow passing custom crypto provider #137

Open
thunderbiscuit opened this issue Jul 27, 2024 · 0 comments · May be fixed by #138
Open

Allow passing custom crypto provider #137

thunderbiscuit opened this issue Jul 27, 2024 · 0 comments · May be fixed by #138

Comments

@thunderbiscuit
Copy link
Member

thunderbiscuit commented Jul 27, 2024

See comment here, and idea for how to tackle here.

Can we just expose the rustls provider API here: https://docs.rs/rustls/latest/rustls/crypto/struct.CryptoProvider.html so I can pass in my own provider? We can have a rustls-aws-lc feature that adds a constructor that uses that. Can do the same for rustls-ring. But I'd like to able to fix this kind of issue in the future without having to wait for a merge.

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.

1 participant