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
fix path to SUSE CA bundle #884
Conversation
@mcalmer this path was used based on a live instance of suse and testing an issue with a consumer (salt) - see related issue saltstack/salt#32743 Are there any differences with the files? |
SUSE bring a yast module called yast2 ca_mgm to create own CA certificates and sign certificates. This file contains only 1 certificate and is not a bundle. Older SLES never used bundles. We used openssl directory structure. Every file contain only one certificate. Of cause in SLES11 there is still a problem. But including a single CA is only a workaround which will help only in a few cases. |
The path list is a collection so you can add both and we can cover 12 and 11 cases? They are done in sequence so put the newer one first
From: Michael Calmer notifications@github.com SUSE bring a yast module called yast2 ca_mgm to create own CA certificates and sign certificates. This file contains only 1 certificate and is not a bundle. Older SLES never used bundles. We used openssl directory structure. Every file contain only one certificate. Of cause in SLES11 there is still a problem. But including a single CA is only a workaround which will help only in a few cases. — |
Agreed. This will at least not break older installations. I will adapt the PR. |
|
Changes Title (replace this with a logical title for your changes)
Description
Fix the path to the SUSE CA bundle. The old path is a special CA file and not the CA bundle.
Status