summaryrefslogtreecommitdiff
path: root/RELEASE_NOTES.md
diff options
context:
space:
mode:
authorClaire McQuin <claire@getchef.com>2014-08-15 16:01:48 -0700
committerClaire McQuin <claire@getchef.com>2014-08-15 16:01:48 -0700
commit515fa094e8bfc1e34a387837bacd29c5300bfc4c (patch)
tree530a37ec3de9ed054320188e89068673726cad17 /RELEASE_NOTES.md
parent4e62358a305513b8235d59485d61f540e5dc6a4a (diff)
downloadchef-515fa094e8bfc1e34a387837bacd29c5300bfc4c.tar.gz
Update for new config default enable client-side key generation
Diffstat (limited to 'RELEASE_NOTES.md')
-rw-r--r--RELEASE_NOTES.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index cc62bf3b48..54b94a10c7 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -165,3 +165,8 @@ end
You must use the windows_service resource to utilize the `:configure_startup` action and `startup_type` attribute. The service resource
does not support them.
+
+## Client-side key generation enabled by default
+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.