Allow ssl_verify_mode to be configured

[Domon]

In Chef 11.12.0+, insecure SSL verification mode triggers a warning like this:

SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the middle
attacks.

To fix this issue add an entry like this to your configuration file:

```
  # Verify all HTTPS connections (recommended)
  ssl_verify_mode :verify_peer

  # OR, Verify only connections to chef-server
  verify_api_cert true
```

To check your SSL configuration, or troubleshoot errors, you can use the
`knife ssl check` command like so:

```
  knife ssl check -c /home/vagrant/chef-solo/solo.rb
```

This pull request allows ssl_verify_mode to be configured.

When not configured, it defaults to :verify_peer to prevent the above warning. 😄

[matschaffer]

Thanks! Do you know offhand how far back ssl_verify_mode is compatible with regards to chef versions?

[Domon]

I believe the ssl_verify_mode setting was introduced in Chef 0.5.2. (Its example client.rb.)

[matschaffer]

Wow. That's pretty far back. Thanks for the verification and the PR!

On Saturday, April 19, 2014, Chun-wei Kuo notifications@github.com wrote:

I believe the ssl_verify_mode setting was introducedhttps://github.com/opscode/chef/commit/af843190f9be71469c4a20ef8f9021b292c05588in Chef 0.5.2. (Its example
client.rbhttps://github.com/opscode/chef/blob/4dbefb3728643479f9e7f08c3d517c23b12bb29a/example-repository/config/client.rb
.)

Reply to this email directly or view it on GitHubhttps://github.com//pull/363#issuecomment-40862901
.

-Mat

about.me/matschaffer