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

Rename ca_trust_file to ca_trust_path #450

Merged
merged 1 commit into from
May 15, 2019

Conversation

marcparadise
Copy link
Contributor

@marcparadise marcparadise commented May 14, 2019

WinRM expects ca_trust_path not ca_trust_file

Signed-off-by: Marc A. Paradise marc.paradise@gmail.com

@marcparadise marcparadise changed the title Rename ca_trust_path to ca_trust_file Rename ca_trust_file to ca_trust_path May 14, 2019
Copy link
Contributor

@miah miah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we test this?

@marcparadise marcparadise force-pushed the use-correct-ca-trust-name branch from 4402b59 to 2bae9dc Compare May 15, 2019 18:12
@marcparadise
Copy link
Contributor Author

I've updated this with a check of default, but I couldn't find a meaningful way to verify that it's getting passed through to WinRMConnection - the only locations to validate it are private.

WinRM expects `ca_trust_file` not `ca_trust_path`

Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
@marcparadise marcparadise force-pushed the use-correct-ca-trust-name branch from 2bae9dc to 1631a4d Compare May 15, 2019 20:13
@marcparadise
Copy link
Contributor Author

In the category of 'iffy is better than nothing'... I added validations for the configuration we're passing into WinRM::Connection, using winrm_transport_inst.send to get the value since connection_options is private.

@miah miah merged commit d5d6882 into inspec:master May 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants