You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.
kniffe ssl fetch works, but knife ssl check fails on Win 7. I'm running ChefDk 0.3.6 against a Chef 12 server running on Ubuntu 14.04 at EC2. U:\ is my home directory.
PS U:\> knife ssl fetch
WARNING: Certificates from chefserv01.companyname.com will be fetched and placed in your trusted_cert
directory (U:/.chef\trusted_certs).
Knife has no means to verify these are the correct certificates. You should
verify the authenticity of these certificates after downloading.
Adding certificate for chefserv01.companyname.com in U:/.chef\trusted_certs/chefserv01_companyname_com.crt
PS U:\> knife ssl check
Connecting to host chefserv01.companyname.com:443
ERROR: The SSL certificate of chefserv01.companyname.com could not be verified
Certificate issuer data: /C=US/ST=WA/L=Seattle/O=YouCorp/OU=Operations/CN=chefserv01.companyname.com/emailAddress=you@example.com
Configuration Info:
OpenSSL Configuration:
* Version: OpenSSL 1.0.0l 6 Jan 2014
* Certificate file: C:/Users/Luis/Code/luislavena/knap-build/var/knapsack/software/x86-windows/openssl/1.0.0n/ssl/cert.pem
* Certificate directory: C:/Users/Luis/Code/luislavena/knap-build/var/knapsack/software/x86-windows/openssl/1.0.0n/ssl/certs
Chef SSL Configuration:
* ssl_ca_path: nil
* ssl_ca_file: "C:/opscode/chefdk/embedded/ssl/certs/cacert.pem"
* trusted_certs_dir: "U:/.chef\\trusted_certs"
TO FIX THIS ERROR:
If the server you are connecting to uses a self-signed certificate, you must
configure chef to trust that server's certificate.
By default, the certificate is stored in the following location on the host
where your chef-server runs:
/var/opt/chef-server/nginx/ca/SERVER_HOSTNAME.crt
Copy that file to you trusted_certs_dir (currently: U:/.chef\trusted_certs)
using SSH/SCP or some other secure method, then re-run this command to confirm
that the server's certificate is now trusted.
FWIW, I had trouble with berks a while back and implemented the SSL_CERT_FILE fix.
The text was updated successfully, but these errors were encountered:
Well I just got this working after finding this blog post. The fix was to set the trusted_certs_dir in my knife.rb:
trusted_certs_dir 'U:/.chef/trusted_certs`
PS U:\> knife ssl fetch
WARNING: Certificates from chefserv01.companyname.com will be fetched and placed in your trusted_cert
directory (U:\/.chef/trusted_certs).
Knife has no means to verify these are the correct certificates. You should
verify the authenticity of these certificates after downloading.
Adding certificate for chefserv01.companyname.com in U:\/.chef/trusted_certs/chefserv01_companyname_com.crt
PS U:\> knife ssl check
Connecting to host chefserv01.companyname.com:443
Successfully verified certificates from `chefserv01.companyname.com'
PS U:\>
My guess is it didn't work with the default path because of my strange home directory setup, but I have not verified.
kniffe ssl fetch
works, butknife ssl check
fails on Win 7. I'm running ChefDk 0.3.6 against a Chef 12 server running on Ubuntu 14.04 at EC2.U:\
is my home directory.FWIW, I had trouble with
berks
a while back and implemented the SSL_CERT_FILE fix.The text was updated successfully, but these errors were encountered: