Forge Home

selinux

SELinux management

jordi prats

eyp

22,480 downloads

2,843 latest version

5.0 quality score

Version information

  • 0.1.15 (latest)
  • 0.1.14
  • 0.1.13
released May 27th 2020
This version is compatible with:
  • Puppet Enterprise 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
  • RedHat
    ,
    Ubuntu

Start using this module

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

Add this declaration to your Puppetfile:

mod 'eyp-selinux', '0.1.15'
Learn more about managing modules with a Puppetfile

Add this module to a Bolt project:

bolt module add eyp-selinux
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install eyp-selinux --version 0.1.15

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

eyp/selinux — version 0.1.15 May 27th 2020

selinux

PRs Welcome

Table of Contents

  1. Overview
  2. Module Description
  3. Setup
  4. Usage
  5. Reference
  6. Limitations
  7. Development

Overview

Disables SELinux, what else anyone would like to do anyway?

Module Description

  • If SELinux is disabled and you want to switch to permissive or enforcing you are required to reboot the system

Setup

What selinux affects

Manages /etc/selinux/config

Setup Requirements

This module requires pluginsync enabled

Beginning with selinux

Disable SELinux

class { 'selinux':
  mode => 'disabled',
}

Usage

There are three SELinux modes available:

  • disabled
  • permissive
  • enforcing

Reference

selinux

  • mode: (default: disabled)
    • disabled
    • permissive
    • enforcing

Limitations

Tested on:

  • CentOS 6

Development

We are pushing to have acceptance testing in place, so any new feature should have some tests to check both presence and absence of any feature

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request