Forge Home

ecryptfs

Manage ecryptfs mounts

12,082 downloads

8,068 latest version

3.8 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.4 (latest)
  • 0.1.3
  • 0.1.2
  • 0.1.0
released Oct 15th 2015

Start using this module

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

Add this module to your Puppetfile:

mod 'ignis-ecryptfs', '0.1.4'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add ignis-ecryptfs
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install ignis-ecryptfs --version 0.1.4

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

ignis/ecryptfs — version 0.1.4 Oct 15th 2015

ecryptfs

Table of Contents

  1. Overview
  2. Usage - Configuration options and additional functionality
  3. Limitations - OS compatibility, etc.

Overview

This module allows to manage ecryptfs mounts as puppet types. Passphrase for encryption should be stored in a file and secured separately.

Mounts are NOT persisted across reboots.

Usage

Use ecryptfs::mount type to define encrypted mounts:

ecryptfs::mount { 'encrypted JENKINS_HOME':
  source_dir      => '/mnt/ebs/jenkins',
  dest_dir        => '/var/lib/jenkins',
  passphrase_file => '/dev/shm/.jenkins_home_ecryptfs'
}

This will install ecryptfs-utils and try to mount /mnt/ebs/jenkins to /var/lib/jenkins using a passphrase stored in plaintext in a file /dev/shm/.jenkins_home_ecryptfs. Please note that a passphrase file should be created by you -- either by puppet or by any other means. Same goes for a source and destination directory. Please see an example in manifests/vagrant.pp.

If you need to define a resource which makes sure that an encrypted mount is UNMOUNTED upon puppet run, set ensure => unmounted leaving all the other parameters in place.

Limitations

This module was tested on CentOS 6.x so far.