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

bsw_gpg (11) Versions 0.2.3

Installs/Configures gpg using an LWRP based approach

Berkshelf/Librarian
Policyfile
Knife
cookbook 'bsw_gpg', '~> 0.2.3'
cookbook 'bsw_gpg', '~> 0.2.3', :supermarket
knife cookbook site install bsw_gpg
knife cookbook site download bsw_gpg
README
Dependencies
Changelog
Quality

gpg Cookbook

LWRP focused cookbook that helps load public or private keys into your GPG keyring from either a string, a cookbook file, or a Chef vault item. The cookbook will check to see if the key fingerprint and user name already exist in the key ring before converging. The resources automatically choose secret vs. public keyrings based on the header of the base64 key contents.

If a key with the same username/email address combo already exists in the keyring, it will be deleted first and replaced with the new key. If either the old or new key has multiple uids, a match on ANY of the email addresses between old and new keys is considered to be a match and will cause the old key to be deleted and replaced.

Requirements

  • Ubuntu
  • CentOS
  • RHEL
  • Scientific Linux

Attributes

None, LWRP focused

Usage

Include the bsw_gpg::default recipe in your cookbook, which will install the gnupg2 package

Install from a string

bsw_gpg_load_key_from_string 'a string key' do
    key_contents '-----BEGIN PGP PUBLIC KEY BLOCK----- (rest of key here'
    for_user 'joe' # The user you want to install the key to
end

Install from a cookbook file

public_key_in_base_64 = cookbook_file_contents 'something.pub','mycookbookname'
bsw_gpg_load_key_from_string 'a cookbook key' do
    key_contents public_key_in_base_64
    for_user 'joe' # The user you want to install the key to
end

Install from a Chef vault item

bsw_gpg_load_key_from_chef_vault 'a chef vault key' do
    data_bag 'thedatabag'
    item 'the_item'
    json_key 'json_key' # Expects to find a hash key with the base64 key contents in it            
    for_user 'joe' # The user you want to install the key to
end

Install from a key server

bsw_gpg_load_key_from_key_server 'some key' do
  key_server 'keyserver.ubuntu.com'
  key_id '561F9B9CAC40B2F7'
  for_user 'root'
end

Use a non-default keyring

You can use this on any of the resources

bsw_gpg_load_key_from_key_server 'some key' do
  key_server 'keyserver.ubuntu.com'
  key_id '561F9B9CAC40B2F7'
  for_user 'root'
  keyring_file_public 'stuff_public.gpg'  
end

When adding a private key with a custom keyring, you must supply both a public and private key file. Resource will complain if you do not. For example:

bsw_gpg_load_key_from_string 'a string key' do
    key_contents '-----BEGIN PGP PRIVATE KEY BLOCK----- (rest of key here'
    for_user 'joe' # The user you want to install the key to
    keyring_file_public 'stuff_public.gpg'
    keyring_file_secret 'stuff_secret.gpg'
end

Force the trust-db rebuild

You can use this on any of the resources. By default, the LWRP lets gpg2 update the trustdb whenever it's executing commands on the default keyring. When it's a custom keyring, in order to avoid gpg2 complaining about not being able to find keys you trust, the LWRP will add --no-auto-check-trustdb. If you want to override this behavior, you can do so like below

# TrustDB check would normally be disabled
bsw_gpg_load_key_from_key_server 'some key' do
  key_server 'keyserver.ubuntu.com'
  key_id '561F9B9CAC40B2F7'
  for_user 'root'
  keyring_file_public 'stuff.gpg'
  disable_trust_db_check false
end
# TrustDB check would normally be enabled
bsw_gpg_load_key_from_key_server 'some key' do
  key_server 'keyserver.ubuntu.com'
  key_id '561F9B9CAC40B2F7'
  for_user 'root'
  disable_trust_db_check true
end

Force trusting (or not) of newly imported keys

By default, after importing the key, if a private key is being imported into the default keyring, these LWRPs runs the equivalent of echo "<keyFingerprint>:6:\n" | gpg2 --import-ownertrust. If you wish to force the trust to be imported (or not imported) regardless of the default, you can do something like this.

# Example 1
bsw_gpg_load_key_from_chef_vault 'a chef vault key' do
    data_bag 'thedatabag'
    item 'the_item'
    json_key 'json_key' # Expects to find a hash key with the base64 key contents in it            
    for_user 'joe' # The user you want to install the key to
    force_import_owner_trust false # Will prevent an import that otherwise would have occurred
end
# Example 1
bsw_gpg_load_key_from_chef_vault 'a chef vault key' do
  data_bag 'thedatabag'
  item 'the_item'
  json_key 'json_key' # Expects to find a hash key with the base64 key contents in it            
  for_user 'joe' # The user you want to install the key to
  keyring_file_secret 'stuff_secret.gpg'
  keyring_file_public 'stuff_public.gpg'
  force_import_owner_trust true # Will force an import that otherwise would NOT have occurred  
end

Contributing

  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  3. Write your change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request using Github

License and Authors

Authors: Brady Wied

Copyright (c) 2014, BSW Technology Consulting LLC All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

ruby_rvm Applicable Versions

gpg CHANGELOG

This file is used to list changes made in each version of the gpg cookbook.

0.2.3

  • [Brady] - RSpec3 updates
  • [intoximeter] - ChefSpec matchers and updated metadata compatibility

0.2.2

0.2.1

  • [Brady] - README syntax fix

0.2.0

  • [Brady] - It doesn't make sense to allow importing private keys into non default keyrings without requiring a public keyring path as well, so modified the LWRPs to have 2 different keyring_file parameters (see README).

0.1.6

  • [Brady] - Handle output that changed with gnupg 2.0.26

Check the Markdown Syntax Guide for help with Markdown.

The Github Flavored Markdown page describes the differences between markdown on github and standard markdown.

Collaborator Number Metric
            

0.2.3 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

0.2.3 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

0.2.3 failed this metric

FC064: Ensure issues_url is set in metadata: bsw_gpg/metadata.rb:1
FC065: Ensure source_url is set in metadata: bsw_gpg/metadata.rb:1
FC066: Ensure chef_version is set in metadata: bsw_gpg/metadata.rb:1
FC069: Ensure standardized license defined in metadata: bsw_gpg/metadata.rb:1
Run with Foodcritic Version 11.1.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

0.2.3 failed this metric

bsw_gpg does not have a valid open source license.
Acceptable licenses include Apache-2.0, apachev2, Apache 2.0, MIT, mit, GPL-2.0, gplv2, GNU Public License 2.0, GPL-3.0, gplv3, GNU Public License 3.0.

No Binaries Metric
            

0.2.3 passed this metric

Publish Metric
            

0.2.3 passed this metric

Supported Platforms Metric
            

0.2.3 passed this metric

Testing File Metric
            

0.2.3 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

0.2.3 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must include a tag that matches this cookbook version number