denyhosts

contributions requested
Configure DenyHosts

153,859 downloads

152,352 latest version

3.5 quality score

Support the Puppet Community by contributing to this module

You are welcome to contribute to this module by suggesting new features, currency updates, or fixes. Every contribution is valuable to help ensure that the module remains compatible with the latest Puppet versions and continues to meet community needs. Complete the following steps:

  1. Review the module’s contribution guidelines and any licenses. Ensure that your planned contribution aligns with the author’s standards and any legal requirements.
  2. Fork the repository on GitHub, make changes on a branch of your fork, and submit a pull request. The pull request must clearly document your proposed change.

For questions about updating the module, contact the module’s author.

Version information

  • 0.1.0 (latest)
  • 0.0.1
released May 8th 2014

Start using this module

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

Add this module to your Puppetfile:

mod 'puppetlabs-denyhosts', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add puppetlabs-denyhosts
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install puppetlabs-denyhosts --version 0.1.0

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

puppetlabs/denyhosts — version 0.1.0 May 8th 2014

puppetlabs-denyhosts

This module supplies basic configuration for DenyHosts

Class: denyhosts

It provides a class that controls which hosts are allowed to connect and the email address to alert on violations, for example:

class { "denyhosts":
  adminemail => "",
  allow      => [ 'host1', 'host2', 'host3' ],
}

The email address defaults to root@localhost.

You could also use a hiera look-up to query the data:

class { "denyhosts":
  adminemail => "",
  allow      => hiera("allowhosts"),
}