Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

should aws-smithy-client care webpki dos attack risk #2947

Closed
stanal opened this issue Aug 24, 2023 · 3 comments
Closed

should aws-smithy-client care webpki dos attack risk #2947

stanal opened this issue Aug 24, 2023 · 3 comments

Comments

@stanal
Copy link

stanal commented Aug 24, 2023

https://rustsec.org/advisories/RUSTSEC-2023-0052.html rustsec report one risk on webpki, and webpki fix it in latest version https://github.com/rustls/webpki/releases/tag/v%2F0.101.4
should aws-smithy-client care about this risk and update webpki which used by rustls ( although rustls has not update webpki for now)

@jdisanti
Copy link
Collaborator

I think once rustls has changed its minimum version, we will update the minimum version of rustls. For now, you can fix this for your project by running cargo update.

@stanal
Copy link
Author

stanal commented Aug 25, 2023

I think once rustls has changed its minimum version, we will update the minimum version of rustls. For now, you can fix this for your project by running cargo update.

thx, I have another question, I find that in mr #2675 removed the native-tls, and replace by rustls, why do that, does rustls is reliable than native-tls, I'm confused which one to use is the best choose. can you give some suggestions for me, very thx ...

@jdisanti
Copy link
Collaborator

Answered in #2675

@smithy-lang smithy-lang locked and limited conversation to collaborators Aug 28, 2023
@rcoh rcoh converted this issue into discussion #2953 Aug 28, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants