Skip to content
This repository has been archived by the owner on Mar 19, 2022. It is now read-only.

Allow ssl_verify_mode to be configured #363

Merged
merged 1 commit into from
Apr 19, 2014

Conversation

Domon
Copy link
Contributor

@Domon Domon commented Apr 18, 2014

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. 😄

Default to :verify_peer.
@matschaffer
Copy link
Owner

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

matschaffer added a commit that referenced this pull request Apr 19, 2014
Allow ssl_verify_mode to be configured
@matschaffer matschaffer merged commit e65c5c1 into matschaffer:master Apr 19, 2014
@Domon
Copy link
Contributor Author

Domon commented Apr 19, 2014

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

@matschaffer
Copy link
Owner

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

On Saturday, April 19, 2014, Chun-wei Kuo [email protected] 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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants