Forge Home

ftpserver

Simple FTP server configuration

8,511 downloads

7,509 latest version

4.3 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.1.2 (latest)
  • 0.1.1
  • 0.1.0
released Jun 7th 2016
This version is compatible with:
  • Puppet Enterprise 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >=2.7.20 <5.0.0
  • ,

Start using this module

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

Add this module to your Puppetfile:

mod 'jbertozzi-ftpserver', '0.1.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add jbertozzi-ftpserver
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install jbertozzi-ftpserver --version 0.1.2

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
Tags: ftp, vsftpd

Documentation

jbertozzi/ftpserver — version 0.1.2 Jun 7th 2016

Overview

This module manages FTP configuration at high level, it does not intend to be highly customizable.

Module Description

The module allow local users to login and chroot them into their home directory.

Three parameters can be customized:

  • FTP mode:
    • 'active'
    • 'passive'
  • SSL encryption:
    • 'explicit'
    • 'implicit'
    • 'none'
  • Anonymous enabled or not

Explicit SSL will encrypt both data and command on client demand while implicit SSL will start a SSL session right away. These modes are not compatible, and FTP client needs to be set accordingly.

If SSL is enabled ('explicit' or 'implicit'), a self signed certificate is genreated into /etc/pki/tls/certs/${::fqdn}.pem (unless overwritten with 'cert_file' parameter). If the file exists, it won't be changed.

Examples

FTP server in passive mode with explicit encryption, anonymous not allowed. In this configuation, client connect to tcp port 21 and explicitly ask for TLS during the FTP session. Firewall need to be opened for incomming connection to range port tcp/2121-2131 and tcp/21.

class { 'ftpserver':
  ssl           => 'explicit',
  mode          => 'passive',
  pasv_min_port => '2121',
  pasv_max_port => '2131',
  allow_anon    => false,
  cert_file     => '/custom/path/server.pem',
}

FTP server in passive mode, SSL set to implicit. Connection first establish a SSL handshake. FTP server listen on ftps tcp port (990). Firewall need to be opened for incomming connection to range port tcp/2121-2131 and tcp/990.

class { 'ftpserver':
  ssl           => 'implicit',
  mode          => 'passive',
  pasv_min_port => '2121',
  pasv_max_port => '2131',
}

FTP server in active mode, SSL disabled and anonymous user allowed:

class { 'ftpserver':
  ssl           => 'none',
  mode          => 'active',
  allow_anon    => true
}

Limitations

  • Work only on CentOS/RHEL distributions. Tested on RHEL 6 / 7 with Puppet 3.6
  • Does not manage firewall rules
  • Support only local user account