Skip to content
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

We need to revisit SSL config #8600

lamont-granquist opened this issue May 29, 2019 · 0 comments


None yet
1 participant
Copy link

commented May 29, 2019

I think there's now three ways to insert SSL certs into chef-client. There's the default ruby location, the SSL_CERT_FILE(?) environment variable and the trusted_certs dir that knife ssl fetch uses. The latter location would ideally be what we'd use universally, but not everything can go through Chef::HTTP (e.g. the gem installer in cookbooks uses bundler directly and we cannot inject Chef::HTTP into it). We need to revisit looking at if we can make all this unified, as was originally intended.

Also, on upgrades we now remove /opt/chef entirely both in the Chef-15 installer and in the chef_client_updater cookbook, which means that we wipe the ssl certs if they were installed directly into /opt/chef. The contents of those directories probably need to be preserved on upgrade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.