Use local system's built-in certificates when connecting to dev_s3 amazon bucket. #3237
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eddierubeiz
changed the title
eddierubeiz
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ref #3236
Ruby 3.4 + OpenSSL 3.5 on macOS:
SSLContext#cert_storestarted out nilSomewhere in the AWS SDK / Net::HTTP stack, a cert store was being constructed implicitly.
That implicit store path ended up triggering CRL expectations, leading to the error described in the issue, even though the certificate chain is valid and
openssl s_clientworked fine.Using
OpenSSL::X509::DEFAULT_CERT_FILEseems safe to me; this extra option is only used fordev_s3in any case.