Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

sigul

A module to manage Sigul servers, bridges and clients
Project URLRSS FeedReport issues

6,584 downloads

6,584 latest version

4.6 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.

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

  • 2.0.0 (latest)
released Aug 18th 2017
This version is compatible with:

Start using this module

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

Add this module to your Puppetfile:

mod 'mricon-sigul', '2.0.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add mricon-sigul
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install mricon-sigul --version 2.0.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

mricon/sigul — version 2.0.0 Aug 18th 2017

Sigul

[Build Status] (https://travis-ci.org/mricon/puppet-sigul)

Table of Contents

  1. Overview
  2. Module Description - What the module does and why it is useful
  3. Setup
  4. Reference
  5. Limitations - OS compatibility, etc.

Overview

Puppet module to manage sigul secure signing server infrastructure setup, including server, bridge and client configurations.

Module Description

Sigul is a multi-tier implementation of a service that would offer a secure mechanism for automated PGP-signing of binary and other artifacts without exposing the PGP keys themselves to untrusted processes (for example, during automated builds).

See https://pagure.io/sigul for more info about Sigul.

This module was forked from https://github.com/jflorian/puppet-sigul and pretty much fully rewritten from scratch while preserving some of the existing logic.

Some of the previous functionality was removed and may be added later as optional functionality:

  • firewall management (best to use profile modules for that)
  • certificate management (best to use profile modules for that)
  • gnupg1 kludges (the upcoming version of sigul should work with gnupg2)

Setup

It's expected that this module will be used with hiera, so the quickest way to configure it for your environment is to add it to your Puppetfile:

mod 'mricon-sigul'

NSS database/certificate management

Please note that while NSS certificate management is a critical aspect of sigul operation, this module does NOT attempt to manage NSS, because there are too many possible ways of doing that (e.g. via certutil directly, or via certmonger+freeipa integration). You will need to decide how you are going to do that as part of your sigul deployment and use your profile manifests to properly set it up.

All three subcomponents of sigul (server, bridge, client) allow specifying the location of the NSS directory and the password:

# The following needs to correspond to the location and password
# you used when setting up your nss certificate store. The value for
# nss_password can be set to '' if there is no password on the store
# (e.g. if it is automatically managed by certmonger).
sigul::nss_dir: '/etc/pki/sigul'
sigul::nss_password: 'somepass'

Firewall management

The same limitation goes for opening firewall ports, since it can either be done via the puppetlabs firewall module or via shorewall. You should be able to find out the ports that you will need to open via corresponding $::sigul::server::config:: or $::sigul::bridge::config:: variables.

Reference

sigul

manage_package

Whether to manage the sigul package. See note at the end on where to get the packages for CentOS7 systems.

Default: true

package_name

Package name (OS-specific).

Default: sigul

manage_nss_dir

Whether to manage the nssdb dir. If you're managing it using some other mechanism, set it to false.

Default: true

nss_dir

You can override it in each submodule, but usually you want to keep it in one place. Note that this module departs from keeping it in /var/lib/sigul due to better SELinux support when keeping it in /etc/pki.

Default: /etc/pki/sigul

nss_dir_seltype

Default: cert_t

nss_password

A convenient place to set toplevel nss password. You can override it in every submodule.

Default: undef

manage_var_dir

Whether to create the var dir. Off by default because this is normally done by packages themselves.

Default: false

var_dir

Where persistent data is going to be stored.

Default: /var/lib/sigul

var_dir_seltype

What SELinux type should be on the vardir. Note that only recent versions of sigul packages install their own SELinux policy, so if you are getting errors due to the default settings here, change it to var_lib_t.

Default: sigul_var_lib_t

manage_conf_dir

Whether to create the configuration dir. Off by default because this is normally done by packages themselves.

Default: false

conf_dir

The location of config files. You can override specific configuration file locations for server, bridge, and client in their own module declarations.

Default: /etc/sigul

conf_dir_seltype

What SELinux type should be on the config file dir. Note that only recent versions of sigul packages install their own SELinux policy, so if you are getting errors due to the default settings here, change it to etc_t.

Default: sigul_conf_t

manage_user

Whether to create the user record. Off by default, because usually done by the package.

Default: false

user

What users should the daemons run as. Also sets ownership of all writable and readable locations.

Default: sigul

user_uid

If you want to force the UID to a specific numeric value, do it here.

Default: undef

manage_group

Whether to create the group record. Off by default, because usually done by the package.

Default: false

group

What group should various files be owned as.

Default: sigul

group_gid

You can force the sigul group to be a specific gid.

Default: undef

sigul::server

This module supports running multiple server instances, which is handy when connecting to multiple bridges running in different availability/security zones. By default, they share the same gnupg and nss databases, but they don't have to.

You don't have to specify instances if you don't need to, the server module will automatically create a default location config for you, e.g.:

sigul::nss_password: 'testpass'
sigul::server::config:
  bridge_hostname: 'bridge.example.com'
  bridge_port: 44433

To specify multiple instances:

sigul::nss_password: 'testpass'
sigul::server::instances:
  devnodes:
    bridge_hostname: 'devnodes-bridge.example.com'
  dmznodes:
    bridge_hostname: 'dmznodes-bridge.example.com'

Refer to manifests/server/instance.pp to see all available configuration options and default values. Generally, they correspond to the config file variables, except with underscores instead of dashes.

sigul::bridge

The bridge module doesn't support multiple instances, because you wouldn't run more than one per individual VM instance. Here's an example hiera configuration (the default values should be good for most things):

sigul::nss_password: 'testpass'
sigul::bridge::config:
  client_listen_port: 44434
  server_listen_port: 44433

Refer to manifests/bridge/config.pp to see all available configuration options and default values. Generally, they correspond to the config file variables, except with underscores instead of dashes.

sigul::client

Client also supports multiple instances, especially since it's mostly setting up config files.

Refer to manifests/client/config.pp to see all available configuration options and default values. Generally, they correspond to the config file variables, except with underscores instead of dashes.

Limitations

The module was written for CentOS7 but should work on other architectures with minimal changes.

For CentOS7 packages of sigul, you can use the repositories published by Fedora-Infrastructure. Here are the example entries to add to your profile manifests:

# Grab sigul packages from this Fedora infra repo
yumrepo {'fedora-infra-sigul':
  descr       => 'Fedora-Infrastructure packages for sigul',
  baseurl     => 'https://infrastructure.fedoraproject.org/repo/infra/epel$releasever-infra/$basearch/',
  gpgkey      => 'https://infrastructure.fedoraproject.org/repo/infra/RPM-GPG-KEY-INFRA-TAGS',
  enabled     => 1,
  gpgcheck    => 1,
  includepkgs => 'sigul*',
}

Until sigul works with gnupg2, you will need the gnupg1 package as well, but only for sigul::server. Note that it's a different repository from above.

yumrepo {'fedora-infra-gnupg1':
  descr       => 'Fedora-Infrastructrure packages for gnupg1',
  baseurl     => 'https://infrastructure.fedoraproject.org/repo/$releasever/$basearch/',
  gpgkey      => 'https://infrastructure.fedoraproject.org/repo/RPM-GPG-KEY-INFRASTRUCTURE',
  enabled     => 1,
  gpgcheck    => 1,
  includepkgs => 'gnupg1*',
}