<commit_before># CVE-2011-3872 Module #

This module provides two main pieces of functionality:

 * Help me get secure
 * Once secure, help me migrate to a new CA

# Quick Start (PE) #

## Install the Module ##

The first step in the remediation process is to install the cve20113872 module
into your Puppet Master module path.  This will likely be /etc/puppet/modules
or /etc/puppetlabs/puppet/modules for Puppet Enterprise.

(Note, if the module is not yet on the forge, it may be built from source using
`puppet-module build`)

    cd /etc/puppetlabs/puppet/modules
    puppet-module install /tmp/puppetlabs-cve20113872-0.0.1.tar.gz

During the rest of these instructions, the modulepath where this module has
been installed will be referred to as <modulepath>.

## Step 1: Issue a new SSL cert for the master ##

In order to secure your Puppet infrastructure, all agents need to connect to a
DNS name that has not been listed in the certdnsnames option.  This will be
called the _intermediate dns name_ certificate.  To accomplish this goal, the
Puppet Master needs a new SSL certificate with the intermediate DNS name.

Step 1 helps you generate this new certificate and configure Puppet Enterprise
to use it.

PE Only Scripts.  These are specifically designed to work with PE.  These
scripts will need to be adapted to help FOSS users and customers.
<commit_msg>Update README with module build information<commit_after># CVE-2011-3872 Module #

This module provides two main pieces of functionality:

 * Help me get secure
 * Once secure, help me migrate to a new CA

# Quick Start #

This module is designed to be installed from the Forge, but until then:

    cd /tmp
    git clone <EMAIL>:puppetlabs/puppetlabs-cve20113872.git cve20113872
    cd cve20113872
    rake build
    cd <modulepath>
    puppet-module install /tmp/cve20113872/pkg/puppetlabs-cve20113872-0.0.1.tar.gz

## Install the Module ##

The first step in the remediation process is to install the cve20113872 module
into your Puppet Master module path.  This will likely be /etc/puppet/modules
or /etc/puppetlabs/puppet/modules for Puppet Enterprise.

Note, if the module is not yet on the forge, it may be built from source using
the build task:

    rake build
    cd /etc/puppetlabs/puppet/modules
    puppet-module install /tmp/puppetlabs-cve20113872-0.0.1.tar.gz

During the rest of these instructions, the modulepath where this module has
been installed will be referred to as <modulepath>.

## Step 1: Issue a new SSL cert for the master ##

In order to secure your Puppet infrastructure, all agents need to connect to a
DNS name that has not been listed in the certdnsnames option.  This will be
called the _intermediate dns name_ certificate.  To accomplish this goal, the
Puppet Master needs a new SSL certificate with the intermediate DNS name.

Step 1 helps you generate this new certificate and configure Puppet Enterprise
to use it.

PE Only Scripts.  These are specifically designed to work with PE.  These
scripts will need to be adapted to help FOSS users and customers.

{'fraction_non_alphanumeric': 0.04831864185439112, 'fraction_numerical': 0.03297420829252367, 'mean_word_length': 3.91025641025641, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3775563', 'n_tokens_mistral': 956, 'n_tokens_neox': 882, 'n_words': 441}