Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

RSS

client-rekey (3) Versions 0.1.0

Regenerates your client key

Berkshelf/Librarian
Policyfile
Knife
cookbook 'client-rekey', '= 0.1.0'
cookbook 'client-rekey', '= 0.1.0', :supermarket
knife cookbook site install client-rekey
knife cookbook site download client-rekey
README
Dependencies
Quality -%

client-rekey-cookbook

Regenerates a chef-client's API key. You want to use this if you believe your client keys could be exposed as a result of the heartbleed vulnerability.

By default, this cookbook will cause chef-client to rekey itself every 24 hours. This can be adjusted with the attribute node['client-rekey']['interval'], which is the maximum allowed age of the client key in seconds.

The library in this cookbook will honor the client configuration setting local_key_generation. If set to true in the client.rb configuration file, the private key will be generated locally and only the public key will travel over the wire. This requires a Chef 11 server.

Supported Platforms

This is expected to work on all platforms that chef-client supports.

Attributes

node['client-rekey']['interval']: This recipe uses the mtime of your client.pem to determine when it was last updated. If the difference between now and the file's mtime is greater than this interval setting, your client key will be regenerated.

Usage

client-rekey::default

Include client-rekey in your node's run_list:

{
  "run_list": [
    "recipe[client-rekey::default]"
  ]
}

Contributing

  1. Fork the repository on Github
  2. Create a named feature branch (i.e. add-new-recipe)
  3. Write you change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request

License and Authors

License:: Apache 2.0 (see: LICENSE) Author:: Chef Software, inc.

No quality metric results found