-
-
Notifications
You must be signed in to change notification settings - Fork 390
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
Support external crypto implementations. #1496
Conversation
@djc I think the visibility changes here make sense, since they're effectively part of the crypto provider API. WDYT? |
be1d69c
to
2a45cd0
Compare
@djc I believe I've addressed your concerns. PTAL |
2a45cd0
to
e7cdeb2
Compare
2e71fdb
to
f1cce12
Compare
This allows the provider integration tests to be run against any crypto provider. For now, only rustls is supported. This will be updated in the future once the boringssl provider has landed. Requires quinn-rs#1496.
@Ralith did you want to take a look as well? |
This allows the provider integration tests to be run against any crypto provider. For now, only rustls is supported. This will be updated in the future once the boringssl provider has landed. Requires quinn-rs#1496.
f1cce12
to
a9c56fd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Ralith would be great to get your feedback on these changes, too.
a9c56fd
to
6b5c6c0
Compare
This allows the provider integration tests to be run against any crypto provider. For now, only rustls is supported. This will be updated in the future once the boringssl provider has landed. Requires quinn-rs#1496.
6b5c6c0
to
78b29b8
Compare
This allows the provider integration tests to be run against any crypto provider. For now, only rustls is supported. This will be updated in the future once the boringssl provider has landed. Requires quinn-rs#1496.
78b29b8
to
43abca3
Compare
This allows the provider integration tests to be run against any crypto provider. For now, only rustls is supported. This will be updated in the future once the boringssl provider has landed. Requires quinn-rs#1496.
43abca3
to
ce962f3
Compare
@Ralith PTAL |
This allows the provider integration tests to be run against any crypto provider. For now, only rustls is supported. This will be updated in the future once the boringssl provider has landed. Requires quinn-rs#1496.
ce962f3
to
9839437
Compare
This allows the provider integration tests to be run against any crypto provider. For now, only rustls is supported. This will be updated in the future once the boringssl provider has landed. Requires quinn-rs#1496.
9839437
to
cce6a25
Compare
@djc if I'm reading the lint error correctly, I think it's an existing issue with |
Yup, new clippy lints from Rust 1.68. Addressed in #1506. |
@djc @Ralith this is blocking quinn-rs/quinn-boring#2. Any chance we can get this in soon? |
We'll get to it when we get to it -- we're maintaining Quinn on a voluntary basis and you're adding code paths here that are somewhat far out of the core use case. Some patience will be required, just have your downstream code depend on a Git commit for now? |
@djc understood. Thanks! |
Thanks for your patience and persistence here; I've been preoccupied, but I do want to land this. |
cce6a25
to
8ddee78
Compare
8ddee78
to
c4be42f
Compare
c4be42f
to
8b44416
Compare
These changes are needed for the BoringSSL crypto provider (quinn-rs#1488), which will reside in a separate repository.
8b44416
to
0123241
Compare
Yes -- if you would like one sooner rather than later, can you send a PR to bump the quinn-proto version number? |
These changes are needed for the BoringSSL crypto provider (#1488), which will reside in a separate repository.