Skip to content

Log the default location of trusted CA certificates when tlsTrustCertsFilePath is not specified #429

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

Merged
merged 1 commit into from
Jun 17, 2024

Conversation

BewareMyPower
Copy link
Contributor

Motivation

Currently when tlsTrustCertsFilePath is not specified, default locations of CA certificates will be used. However, these paths are determined by the compile option when building OpenSSL and they are invisible to users. If the OS uses a different path, the TLS connection will fail with no helpful error message.

References:

…sFilePath is not specified

### Motivation

Currently when `tlsTrustCertsFilePath` is not specified, default
locations of CA certificates will be used. However, these paths are
determined by the compile option when building OpenSSL and they are
invisible to users. If the OS uses a different path, the TLS connection
will fail with no helpful error message.
@BewareMyPower BewareMyPower self-assigned this Jun 17, 2024
@BewareMyPower BewareMyPower added this to the 3.6.0 milestone Jun 17, 2024
@BewareMyPower BewareMyPower merged commit 739f0f0 into apache:main Jun 17, 2024
15 checks passed
@BewareMyPower BewareMyPower deleted the bewaremypower/print-ca branch July 4, 2024 02:43
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 this pull request may close these issues.

2 participants