-
Notifications
You must be signed in to change notification settings - Fork 248
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
Fallback to webpki certs if no native certs found, in hyper client from aws_smithy_runtime. #1167
Comments
Hi, thank you for submitting a feature request! A clarifying question. Without the suggested feature, can you work around by using the code snippet mentioned in this guide (search for |
I will test that, thanks 👍( and get back to you afterwards ) Although I think even if that works a fallback to the webpki certs would probably still make sense :) |
Greetings! It looks like this issue hasn’t been active in longer than a week. We encourage you to check if this is still an issue in the latest release. Because it has been longer than a week since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or add an upvote to prevent automatic closure, or if the issue is already closed, please feel free to open a new one. |
I'll get back to this, just haven't found the time yet :) |
Ok so I've tested your suggestion and I can confirm that the following works in our code: aws_sdk_s3::Config::builder()
.http_client(
HyperClientBuilder::new().build(
HttpsConnectorBuilder::new()
.with_webpki_roots()
.https_only()
.enable_http1()
.enable_http2()
.build(),
),
)
..... |
Although I still think a fallback to webpki certs makes sense if no native ones are found. Is it welcome that I try to implement that in a pr or would I be wasting my time on that? :) |
Describe the feature
fallback to the webpki root certs if no native certs are found
Use Case
I like to use a project that uses this sdk in a
FROM scratch
docker image in which no ca-certificates is available. Falling back to webpki certs if that happens would allow this usecase.Proposed Solution
Update hyper_rustls to at least v0.25 (from v0.24, current latest version would be v0.27.2) and check the result returned by with_native_certs() starting from that version, calling with_webpki_certs if that errors. Basically replace the following code like so:
to
(there is probably a nicer way to write it but you should get the gist of it)
Other Information
No response
Acknowledgements
A note for the community
Community Note
The text was updated successfully, but these errors were encountered: