summaryrefslogtreecommitdiff
path: root/RELEASE_NOTES.md
diff options
context:
space:
mode:
authorClaire McQuin <claire@getchef.com>2014-08-15 16:05:36 -0700
committerClaire McQuin <claire@getchef.com>2014-08-15 16:05:36 -0700
commit93a5248e696c30f19f064c9fd45fe87b8b667b5e (patch)
tree0a3db8c645d04d80b4df4a8acb391441d7287648 /RELEASE_NOTES.md
parent515fa094e8bfc1e34a387837bacd29c5300bfc4c (diff)
downloadchef-93a5248e696c30f19f064c9fd45fe87b8b667b5e.tar.gz
Update for CookbookSiteStreamingUploader change to use config option ssl_verify_mode
Diffstat (limited to 'RELEASE_NOTES.md')
-rw-r--r--RELEASE_NOTES.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index 54b94a10c7..c7567b8de2 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -170,3 +170,7 @@ does not support them.
When creating a new client via the validation_client account, Chef 11 servers allow the client to generate a key pair locally
and send the public key to the server, enhancing scalability. This was disabled by default, since client registration would not
work properly if the remote server implemented only the Chef 10 API.
+
+## CookbookSiteStreamingUploader now uses ssl_verify_mode config option
+The CookbookSiteStreamingUploader now obeys the setting of ssl_verify_mode in the client config. Was previously ignoring the
+config setting and always set to VERIFY_NONE.