Forge Home

Modules

Resources

PuppetEcosystemPuppet CommunityUpdates

sshd

Augeas based module to manage the SSHD server
Project URLRSS FeedReport issues

7,914 downloads

6,442 latest version

4.9 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.2.10 (latest)
  • 0.2.9
  • 0.2.8
  • 0.2.7
  • 0.2.6
  • 0.2.5
  • 0.2.4
  • 0.2.3 (deleted)
  • 0.2.2
  • 0.2.1
  • 0.2.0
released Nov 18th 2017
This version is compatible with:
  • Puppet Enterprise 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >=3.8.0

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'ljkimmel99-sshd', '0.2.9'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add ljkimmel99-sshd
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install ljkimmel99-sshd --version 0.2.9

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

ljkimmel99/sshd — version 0.2.9 Nov 18th 2017

sshd

Table of Contents

  1. Overview
  2. Module Description
  3. Setup - The basics of getting started with sshd
  4. Usage - Configuration options and additional functionality
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module

Overview

This module configures SSHD flexibly with Augeas.

Module Description

This module configures sshd with Augeas. SSHD has numerous configuration items and I'd prefer not to update modules frequently as options are added and removed. Using Augeas allows the administrator to simply add arbitrary parameters at will.

The module provides a defined type (sshd_settings) that allows multiple other classes to directly apply settings for SSHD.

The idea behind this class was to provide a simple class that takes minimal input parameters but that still provides deep customizability of the underlying service (SSHD).

Setup

What sshd affects

  • This module installs the SSHD package (system dependent).
  • This module enables and runs the SSHD service.
  • This module provides a defined type to pass a hash of setting-value pairs to configure SSHD.

Usage

Caveats

This module utilizes the standard sshd lens from Augeas. It currently only accepts simple key/ value pairs. Because of this one may need to enlist augtool to validate that the setting being applied works as expected. For example, the 'Ciphers' option takes a string of comma-separated values ({'Ciphers' => 'aes128-ctr,aes192-ctr,aes256-ctr'}). However, while 'MACs' would appear to be the same, it does not actually function that way. The lens forces each element of the comma- separated list for this value to be a subnode. That is to say that to set the option MACs hmac-sha2-256,hmac-sha2-512 you actually have to pass the hash: {'MACs/1' => 'hmac-sha2-256', 'MACs/2' => 'hmac-sha2-512'}.

Not all options have been tested and some may not work as simple key/value pairs.

Parameters

sshd_config

This parameter provides the full path to the SSHD configuration file.

Default: OS dependent (RHEL: /etc/ssh/sshd_config)

svc_name

This configures the name of the operating system service.

Default: OS dependent (RHEL: sshd)

sshd_pkg_name

This configures the name of the distribution package.

Default: OS dependent (RHEL: openssh-server)

custom_settings

This is a hash of key/value (setting name/setting value) to pass as the configuration.

Default: {}

set_comments

This is a boolean specifying whether or not to place a comment above each setting applied in the sshd configuration. Since the entire file is not managed it is convenient to inform administrators editing the file locally about the fact that certain parameters may be overwritten by Puppet. Setting the value to true will create a comment by each setting. Setting it to false will remove any existing comments on passed settings.

Default: true

priv_key_mode

This specifies the permissions to configure on local sshd key files (under /etc/ssh/). The local key files are reported by a bundled custom fact (local_ssh_priv_keys).

Default: 0600

pub_key_mode

This specifies the permissions to configure on local sshd cert files (under /etc/ssh/). The local cert files are reported by a bundled custom fact (local_ssh_pub_keys).

Default: 0644

lens

The name of the lens to use with Augeas.

Default: sshd.lns

Facts

local_ssh_priv_keys

Dynamically determined list of private keys under /etc/ssh.

local_ssh_pub_keys

Dynamically determined list of public keys under /etc/ssh.

Defined Types

sshd_settings

This defined type takes in a hash of arbitrary settings ($settings) and applies them to the sshd configuration file. Some care must be taken that inclusion of this type in multiple classes don't configure the same setting. Configuring the same setting (but with differing values) will cause multiple changes during each Puppet run and the results will be unpredictable. Passing the same setting (with same value) in multiple classes will result in a duplicate declaration error.

The type also takes a parameter, $context. This parameter allows further tweaking when settings don't meet the simple key/value paradigm. It is passed to Augeas as a 'context' so that settings can be applied at a lower level than directly underneath the 'file'.

Finally, it also takes the $set_comment parameter which performs the same function as the class paramter $set_comments.

Examples

This example shows a basic usage where the sshd class in declared with custom settings and then another class uses the defined type (sshd::sshd_settings) to add further settings.

  class class1 () {
    class { 'sshd':
      custom_settings => {
                         'Banner' => '/etc/issue',
                         'Protocol' => '2',
                         },
    }
  }

  class class2 () {
    sshd::sshd_settings { 'SSHD Settings required for Class2':
      settings  =>  {
                    'Ciphers' => 'aes128-ctr,aes192-ctr,aes256-ctr',
                    'MACs/1' => 'hmac-sha2-256',
                    'MACs/2' => 'hmac-sha2-512',
                    },
      }
  }

The defined type was also designed to ignore settings that have a nil/undef value. This is useful in cases where you have a base class that applies to all systems and applies a default set of SSHD settings but some systems need to override one or more of those settings for another purpose. Here is an example that uses Hiera (hiera_hash with merging):

  ---
  # Base Hiera data
  class1::sshd_settings:
    'Banner': '/etc/issue'
    'Protocol': '2'
    'GSSAPIAuthentication': 'no'

  ---
  # Override Hiera data
  class1::sshd_settings:
    'GSSAPIAuthentication': ~

  class2::sshd_settings:
    'GSSAPIAuthentication': 'yes'
    'Ciphers': 'aes128-ctr,aes192-ctr,aes256-ctr'
    'MACs/1': 'hmac-sha2-256'
    'MACs/2': 'hmac-sha2-512'

  class class1 (
    $sshd_custom_settings  = hiera_hash('class1::sshd_settings'),
  ) {
    sshd::sshd_settings { 'Class1 SSHD Settings':
      settings  =>  $sshd_custom_settings,
    }
  }

  class class2 (
    $sshd_custom_settings  = hiera_hash('class2::sshd_settings'),
  ) {
    sshd::sshd_settings { 'Class2 SSHD Settings':
      settings  =>  $sshd_custom_settings,
    }
  }

Limitations

  • As of 17-November-2017 this module is only built to support RHEL 6/7 as these are the only versions of Linux I am actively working with. I am open to adding support for others if people want to provide input.
  • There is no validation of configuration settings. While this allows for administrators to pass invalid values it is also part of the design goal of the module. Being able to pass arbitrary configuration settings allows the module to function across a wide range of sshd and OS versions without modification.
  • This module was built for a limited set of purposes. The goal is to add features over time but it will likely occur as requested or as I find a need for something new.
  • This module was built to work with Puppet 3.8 and, for the time being, needs to remain compatible. For this reason there is an embedded defined type within the provided defined type. This embedded type provides the ability to implicitly loop over the passed in settings hash.

Development

Submit issues and pull requests at: https://github.com/ljkimmel/sshd