driver fails on ssl-verify when run on a ssl intercepting network

[mattstratton]

More and more commonly, users are wanting to leverage these tools inside of an enterprise network that has SSL Intercepting features enabled (see https://bto.bluecoat.com/webguides/proxysg/security_first_steps/Content/Solutions/SSL/ssl_solution.htm for one such example).

On a network with this enabled, attempts to verify the SSL certificates will fail, as the cert will not show as valid (as the cert is from the proxy device and not the actual destination).

Example output of running kitchen inside such a network:

-----> Starting Kitchen (v1.7.3)
D      winrm requested, loading winrm gem (["~> 1.6"])
D      winrm is loaded.
D      winrm-fs requested, loading winrm-fs gem (["~> 0.4.1"])
D      winrm-fs is loaded.
-----> Creating <default-windows-2012r2>...
D      ------Exception-------
D      Class: Kitchen::ActionFailed
D      Message: Failed to complete #create action: [SSL_connect returned=1 errno=0 state=error: certificate verify failed]
D      ---Nested Exception---
D      Class: Seahorse::Client::NetworkingError
D      Message: SSL_connect returned=1 errno=0 state=error: certificate verify failed
D      ------Backtrace-------

Ideally, there should be some type of setting in the driver to bypass ssl verification for such cases.

[mattstratton]

Possibly helpful info - amazon-archives/aws-sdk-core-ruby#166 (comment)