Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix several markdown lint issues #319

Merged
merged 1 commit into from
Apr 25, 2020
Merged

Fix several markdown lint issues #319

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 10 additions & 9 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
[![Puppet Forge - endorsement](https://img.shields.io/puppetforge/e/puppet/selinux.svg)](https://forge.puppetlabs.com/puppet/selinux)
[![Puppet Forge - scores](https://img.shields.io/puppetforge/f/puppet/selinux.svg)](https://forge.puppetlabs.com/puppet/selinux)

#### Table of Contents
## Table of Contents

1. [Overview](#overview)
1. [Module Description - What the module does and why it is useful](#module-description)
Expand Down Expand Up @@ -72,7 +72,8 @@ running system.
* The `selinux_port` provider may misbehave if the title does not correspond to
the format it expects. Users should use the `selinux::port` define instead except
when purging resources
* Defining port ranges that overlap with existing ranges is currently not detected, and will
* Defining port ranges that overlap with existing ranges is currently not
detected, and will
cause semanage to error when the resource is applied.
* On Debian systems, the defined types fcontext, permissive, and port do not
work because of [PA-2985](https://tickets.puppetlabs.com/browse/PA-2985).
Expand Down Expand Up @@ -152,9 +153,9 @@ selinux::boolean { 'puppetagent_manage_all_files': }
### Things to remember

* The SELinux tools behave odd when SELinux is disabled
* `semanage` requires `--noreload` while in disabled mode when
* `semanage` requires `--noreload` while in disabled mode when
adding or changing something
* Only few `--list` operations work
* Only few `--list` operations work
* run acceptance tests: `./test-acceptance-with-vagrant`

### Facter facts
Expand All @@ -164,11 +165,11 @@ the config\_mode to be set, but only the boolean `enabled` is set.

The most important facts:

| Fact | Fact (old) | Mode: disabled | Mode: permissive | Mode: enforcing |
|-------------------------------------------|---------------------------|----------------|-----------------------------------------|-----------------------------------------|
| `$facts['os']['selinux']['enabled']` | `$::selinux` | false | true | true |
| `$facts['os']['selinux']['config_mode']` | `$::selinux_config_mode` | undef | Value of SELINUX in /etc/selinux/config | Value of SELINUX in /etc/selinux/config |
| `$facts['os']['selinux']['current_mode']` | `$::selinux_current_mode` | undef | Value of `getenforce` downcased | Value of `getenforce` downcased |
| Fact | Fact (old) | Mode: disabled | Mode: permissive | Mode: enforcing |
|---|---|---|---|---|
| `$facts['os']['selinux']['enabled']` | `$::selinux` | false | true | true |
| `$facts['os']['selinux']['config_mode']` | `$::selinux_config_mode` | undef | Value of SELINUX in /etc/selinux/config | Value of SELINUX in /etc/selinux/config |
| `$facts['os']['selinux']['current_mode']` | `$::selinux_current_mode` | undef | Value of `getenforce` downcased | Value of `getenforce` downcased |

## Authors

Expand Down