Update README.md for ssl.ca.certificates #791
Conversation
try #2 to strike a balance between informative/useful/concise
|
@confluentinc It looks like @chicagobuss just signed our Contributor License Agreement. 👍 Always at your service, clabot |
| package which needs to be installed through `apt`, `yum`, et.al. | ||
|
|
||
| On MacOS, different versions can store CA certificates in different locations. | ||
| On MacOS Mojave and later, for instance, this is usually ` '/private/etc/ssl/cert.pem'`. |
There was a problem hiding this comment.
I don't think this is entirely accurate. I think the bundled openssl version may look there but MacOS itself stores them in the keychain database. I believe this to be the reason why openssl s_client -connect works but the Python client complains. It'd be good to verify this statement prior to proceeding as this may be one of those "works on my machine" type situations rather than works on MacOS Mojave+.
| package which needs to be installed through `apt`, `yum`, et.al. | ||
|
|
||
| On MacOS, different versions can store CA certificates in different locations. | ||
| On MacOS Mojave and later, for instance, this is usually ` '/private/etc/ssl/cert.pem'`. |
There was a problem hiding this comment.
Inconsistent formatting, drop the '.
|
Joshua Buss seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
try number 2 to strike a balance between informative/useful/concise