diff options
author | danielsdeleo <dan@getchef.com> | 2014-03-26 12:12:46 -0700 |
---|---|---|
committer | danielsdeleo <dan@getchef.com> | 2014-03-26 12:12:46 -0700 |
commit | e6b441adc398ea99f09d7641de82eea28b686449 (patch) | |
tree | c93fe23b7f23ca3b3b3992e7abf2238d71ab9a45 /DOC_CHANGES.md | |
parent | 6231d5f3faa6d94051c3a7878742b3b9a684e374 (diff) | |
download | chef-e6b441adc398ea99f09d7641de82eea28b686449.tar.gz |
Add new config option to DOC_CHANGES
Diffstat (limited to 'DOC_CHANGES.md')
-rw-r--r-- | DOC_CHANGES.md | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/DOC_CHANGES.md b/DOC_CHANGES.md index b259729c01..f29af23d30 100644 --- a/DOC_CHANGES.md +++ b/DOC_CHANGES.md @@ -115,4 +115,28 @@ workaround. This is highly discouraged. If some behavior of Chef prevents a user from enabling SSL certificate verification, they are encouraged to file a bug report. +### New Configuration Option: `local_key_generation` + +Chef 11.x servers support client-side generation of keys when creating +new clients. Generating the keys on the client provides two benefits: 1) +the private key never travels over the network, which improves security; +2) the CPU load imposed by key creation is moved to the node and +distributed, which allows the server to handle more concurrent client +registrations. + +For compatibility reasons, this feature is opt-in, but will likely be +the default or even only behavior in Chef 12. + +To enable it, add this to client.rb before running chef-client on a node +for the first time: + +``` +local_key_generation true +``` + +The default value of this setting is `false` + +*NOTE:* Chef servers that implement the 10.x API do not support this +feature. Enabling this on a client that connects to a 10.X API server +will cause client registration to silently fail. Don't do it. |