The readme on github talks about this, and the latest changes to knife-google on github include a better error message in this case. As Chirag says, including cacert.pem with omnibus Chef on Windows is the correct fix and is in progress at the moment.
The issue for this plug-in is tracked at http://tickets.opscode.com/browse/KNIFE-279.
Jeppe, great to see that you’re using this plug-in on Windows.
From: Chirag Jog <email@example.com:firstname.lastname@example.org>
Date: Friday, June 14, 2013 12:56 AM
To: "email@example.com:firstname.lastname@example.org" <email@example.com:firstname.lastname@example.org>, Adam Edwards <email@example.com:firstname.lastname@example.org>
Subject: Re: [chef] SSL problem with embedded ruby on Windows?
Right. This is known issue for Windows. We have bug in JIRA to ship the certificate (self-signed) as part of Chef as we do in linux. Once that is fixed, SSL_CERT_FILE will not be required.
Chief Technology Officer,
Clogeny Technologies | http://clogeny.comhttp://clogeny.com/
(M) 0091-9766619440 | Skype: chirag.jog
On Fri, Jun 14, 2013 at 1:14 PM, Jeppe Nejsum Madsen <email@example.com:firstname.lastname@example.org> wrote:
I seem to have a problem with the embedded ruby when running on windows. It looks like the cacert.pem file is not located correctly:
irb(main):001:0> require ‘open-uri’
irb(main):002:0> open "https://google.com"
OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
from C:/opscode/chef/embedded/lib/ruby/1.9.1/net/http.rb:799:in `connect’
Not sure if this is expected or not. Setting SSL_CERT_FILE solves the issue.
There seems to be at least two ca-bundle.pem files in the embedded ruby, but not sure if they are supposed to be located automagically?