(BOLT-389) Initial implementation of WinRM --[no-]ssl-verify#343
(BOLT-389) Initial implementation of WinRM --[no-]ssl-verify#343MikaelSmith merged 3 commits intopuppetlabs:masterfrom
Conversation
|
That looks great! Are you familiar with our ticketing system? I'd like to have a ticket in JIRA for this in the BOLT project: https://github.com/puppetlabs/bolt/blob/master/CONTRIBUTING.md#issues |
|
@MikaelSmith I've created a New Feature ticket in JIRA here: https://tickets.puppetlabs.com/browse/BOLT-389 |
|
Thanks. Looks like there are still a few rubocop issues. Are you able to run it locally with |
…install the rubocop components
|
@MikaelSmith I had to update the |
|
Ah, they didn't take into account the previous bundle run. Thanks for fixing that. |
|
Here is an example of the command failing when trying to connect to a host with self-signed certs (notice no $ bolt file upload test.txt 'C:\' --nodes winrm://windowshost.domain.tld --user Administrator --password xxx
Started on windowshost.domain.tld...
Failed on windowshost.domain.tld:
Failed to connect to https://windowshost.domain.tld:5986/wsman: SSL_connect returned=1 errno=0 state=error: certificate verify failed
Is the remote host using a self-signed SSL certificate? Use --no-ssl-verify to disable remote host SSL verification.
Failed on 1 node: winrm://windowshost.domain.tldHere is an example of the command working by passing in $ bolt file upload test.txt 'C:\' --nodes winrm://windowshost.domain.tld --user Administrator --password xxx --no-ssl-verify
Started on windowshost.domain.tld...
Finished on windowshost.domain.tld:
Uploaded 'test.txt' to 'windowshost.domain.tld:C:\'
Successful on 1 node: winrm://windowshost.domain.tld
Ran on 1 node in 2.69 seconds |
|
This would be nice to test against the vagrant Windows VM, but setting that up could take some work. I think I'm ok with the unit test level on this. |
Currently Bolt doesn't support ignoring SSL verification for use with self-signed certificats.
To support this i've introduced a new command line switch and config option under the WinRM transport called
ssl-verifythat can be used from the CLI with the--[no-]ssl-verifyoption.In the interest of security i've continued to use the "secure by default" paradigm and make the default value of
--ssl-verifybetrue