selinux_policy (42) Versions 1.0.1 Follow26

Manages SELinux policy components

Policyfile

Berkshelf

Knife

cookbook 'selinux_policy', '= 1.0.1', :supermarket

cookbook 'selinux_policy', '= 1.0.1'

knife supermarket install selinux_policy

knife supermarket download selinux_policy

README

Dependencies

Changelog

Quality 50%

SELinux Policy Cookbook

This cookbbok can be used to manage SELinux policies and components (rather than just enable / disable enforcing).

I made it because I needed some SELinux settings done, and the executes started to look annoying.

Requirements

Needs an SELinux policy active (so its values can be managed). Can work with a disabled SELinux system (see attribute allow_disabled), which will generate warnings and do nothing (but won't break the run).

Also requires SELinux's management tools, namely semanage, setsebool and getsebool.
Tools are installed by the selinux_policy::install recipe (for RHEL/Debian and the like).

Attributes

These attributes affect the way all of the LWRPs are behaving.

node['selinux_policy']['allow_disabled'] - Whether to allow runs when SELinux is disabled. Will generate warnings, but the run won't fail.
Defaults to true, set to false if you don't have any machines with disabled SELinux.

Usage

selinux_policy::install - Installs SELinux policy management tools

This cookbook's functionality is exposed via resources, so it should be called from a wrapper cookbook.
Remember to add depends 'selinux_policy' to your metadata.rb.

boolean

Represents an SELinux boolean.
You can either set it, meaning it will be changed without persistence (it will revert to default in the next reboot), or setpersist it (default action), so it'll keep it value after rebooting.

Using setpersist requires an active policy (so that the new value can be saved somewhere).

Attributes:

name: boolean's name. Defaults to resource name.
value: Its new value (true/false).
force: Use setsebool even if the current value agrees with the requested one.

Example usage:

include_recipe 'selinux_policy::install'

selinux_policy_boolean 'httpd_can_network_connect' do
    value true
    # Make sure nginx is started if this value was modified
    notifies :start,'service[nginx]', :immediate
end

Note: Due to ruby interperting 0 as true, using value 0 is unwise.

port

Allows assigning a network port to a certain SELinux context.

As explained here, it can be useful for running Apache on a non-standard port.

Actions:

addormodify (default): Assigns the port to the right context, whether it's already listed another context or not at all.
add: Assigns the port to the right context it's if not listed (only uses -a).
modify: Changes the port's context if it's already listed (only uses -m).
delete: Removes the port's context if it's listed (uses -d).

Attributes:

port: The port in question, defaults to resource name.
protocol: tcp/udp.
secontext: The SELinux context to assign the port to. Uneeded when using delete.

Example usage:

include_recipe 'selinux_policy::install'

# Allow nginx to bind to port 5678, by giving it the http_port_t context
selinux_policy_port '5678' do
    protocol 'tcp'
    secontext 'http_port_t'
end

module

Manages SEModules

Actions:

fetch: Prepares the module's files for compilation. Allow remote_directory-like behaviour
compile: Translates a module source directory into a NAME.pp file. Uses make logic for idempotence.
install: Adds a compiled module (pp) to the current policy. Only installs if the module was modified this run, force is enabled or it's missing from the current policy.
Note: I wish I could compare the existing module to the one generated, but the extract capability was only added in Aug 15. I'll be happy to see a better idea.
deploy (default): Runs fetch, compile, install in that order.
remove: Removes a module.

Attributes:

name: The module name. Defaults to resource name.
directory: Directory where module is stored. Defaults to a directory inside the Chef cache.
content: The module content, can be extracted from audit2allow -m NAME. This can be used to create simple modules without using external files.
directory_source: Copies files cookbook to the module directory (uses remote_directory). Allows keeping all of the module's source files in the cookbook.
Note: You can pre-create the module directory and populate it in any other way you'd choose.
cookbook: Modifies the source cookbook for the remote_directory.
force: Installs the module even if it seems fine. Ruins idempotence but should help solve some weird cases.

Example usage:

include_recipe 'selinux_policy::install'

# Allow openvpn to write/delete in '/etc/openvpn'
selinux_policy_module 'openvpn-googleauthenticator' do
  content <<-eos
    module dy-openvpn-googleauthenticator 1.0;

    require {
        type openvpn_t;
        type openvpn_etc_t;
        class file { write unlink };
    }


    #============= openvpn_t ==============
    allow openvpn_t openvpn_etc_t:file { write unlink };
  eos
  action :deploy
end

fcontext

Allows managing the SELinux context of files.
This can be used to grant SELinux-protected daemons access to additional / moved files.

Actions:

addormodify (default): Assigns the file regexp to the right context, whether it's already listed another context or not at all.
add: Assigns the file regexp to the right context it's if not listed (only uses -a).
modify: Changes the file regexp context if it's already listed (only uses -m).
delete: Removes the file regexp context if it's listed (uses -d).

Attributes:

file_spec: This is the file regexp in question, defaults to resource name.
secontext: The SELinux context to assign the file regexp to. Not required for :delete

Example usage (see mysql cookbook for example daemons ):

include_recipe 'selinux_policy::install'

# Allow http servers (nginx/apache) to modify moodle files
selinux_policy_fcontext '/var/www/moodle(/.*)?' do
  secontext 'httpd_sys_rw_content_t'
end

# Allow a custom mysql daemon to access its files.
{'mysqld_etc_t' => "/etc/mysql-#{service_name}(/.*)?",
'mysqld_etc_t' => "/etc/mysql-#{service_name}/my\.cnf",
'mysqld_log_t' => "/var/log/mysql-#{service_name}(/.*)?",
'mysqld_db_t' => "/opt/mysql_data_#{service_name}(/.*)?",
'mysqld_var_run_t' => "/var/run/mysql-#{service_name}(/.*)?",
'mysqld_initrc_exec_t' => "/etc/rc\.d/init\.d/mysql-#{service_name}"}.each do |sc, f|
  selinux_policy_fcontext f do
    secontext sc
  end
end

permissive

Allows some types to misbehave without stopping them.

Not as good as specific policies, but better than disabling SELinux entirely.

Actions:

add: Adds a permissive, unless it's already added
delete: Deletes a permissive if it's listed

Example usage:

include_recipe 'selinux_policy::install'

# Disable enforcement on Nginx
# As described on http://nginx.com/blog/nginx-se-linux-changes-upgrading-rhel-6-6/

selinux_policy_permissive 'nginx' do
  notifies :restart, 'service[nginx]'
end

Testing

We have a test kitchen that has some tests (at the time of writing this: Basic port ops)

We also have a ChefSpec suite for some things (again, currently only basic ports). To use it, run something like chef exec rspec.

We also only test against CentOS (because Ubuntu comes with SELinux disabled and restarting mid-test is hard).

Chef 11 Support

I don't use Chef 11, but stuff seems to work OK to other people.

Contributing

Fork the repository
Create a named feature branch (like add_component_x)
Write your change
Write tests for your change (if applicable):
If fixing a bug, please add regression tests for the RSpec (if possible) and the kitchen If adding a feature, please create basic tests for it, in both RSpec and kitchen
Run the tests, ensuring they all pass, using rake testing:user
Submit a Pull Request using Github
Please attach the test results using a gist

License and Authors

Licensed GPL v2

Author: Nitzan Raz (backslasher)

Contributors:
* Joerg Herzinger (http://www.bytesource.net)
* Wade Peacock (http://www.visioncritical.com)
* Kieren Evans (http://kle.me)
* Antek Baranski
* James Le Cuirot
* John Bartko
* Maksim Horbul

I'll be happy to accept contributions or to hear from you!

Dependent cookbooks

yum ~> 3.9

Contingent cookbooks

selinuxpolicy CHANGELOG

This file is used to list changes made in each version of the selinuxpolicy cookbook.

1.0.1

[backslasher] - Foodcritic and rubocop improvements

1.0.0

[equick] - Validating ports better
[backslasher] - FContext relabling for flies is now immediate. (Possibly breaking)
[backslasher] - testing made slightly more elegant

0.9.6

[jhmartin] - Updated README
[backslasher] - Major revision of testing

0.9.5

[backslasher] - Modified yum dependency

0.9.4

[mhorbul] - Fixed state detection in boolean resource

0.9.3

[backlsasher] - Fixed testing & kitchen
[jbartko] - Added Fedora support

0.9.2

[backslasher] - Ignoring nonexisting files in restorecon

0.9.1

[backslasher] - Fixed issue with module being partially executed on machines with SELinux disabled

0.9.0

[backslasher] - module overhaul: code refactoring, supporting new input, testing, new actions
[backslasher] - fcontext overhaul: code refactoring, testing, new action

Note: I don't think I have any breaking changes here. If there are, I apologise and request that you create an issue with a test recipe that fails on the problem (so I can reproduce)

0.8.1

[backslasher] - Added Travis CI harness
[backslasher] - Fixed typo in README

0.8.0

[backslasher] - Test overhaul. Now testing is somewhat reliable when using ports
[backslasher] - Port search is a function
[backslasher] - Port detection now supports ranges. No possibility to add ranges (yet)

0.7.2

[shortdudey123] - ChefSpec matchers, helps testing

0.7.1

[backslasher] - Forgot contributor

0.7.0

[chewi] - Fixed prereq packages
[backslasher] - Modified misleading comment
[chewi] - Move helpers into a cookbook-specific module
[chewi] - Prevent use_selinux from blowing up on systems without getenforce

0.6.5

[backslasher] - Ubuntu installation warning

0.6.4

[sauraus] - CentOS 7 support
[sauraus] - Typos

0.6.3

[backslasher] - Readme updates
[kevans] - Added kitchen testing

0.6.2

[kevans] - Support Chef 11.8.0 running shellout!()
[backslasher] - Simplified support info
[backslasher] - ASCIIed files

0.6.1

[backslasher] - Migrated to only_if instead of if
[backslasher] - README typos

0.6.0

[joerg] - Added fcontext resource for managing file contexts under SELinux

0.5.0

[backslasher] - Added RHEL5/derivatives support. Thanks to @knightorc. Cookbook will break on RHEL7. If anyone expiriences this, please check required packages and create an issue/PR
[backslasher] - Machines without SELinux are (opionally) supported. Thanks to @knightroc.

0.4.0

[backlasher] - Fixed foodcritic errors

0.3.0

[backlasher] - Fixed install.rb syntax. Now it actually works

0.2.0

[backlasher] - Added module resource. Currently supports deployment and removal (because that's what I need)
[backlasher] - Added permissive resource

0.1.0

[backlasher] - Initial release of selinuxpolicy

Collaborator Number Metric

1.0.1 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Foodcritic Metric

1.0.1 passed this metric

Adoptable Cookbooks List

Supermarket Belongs to the Community

View our collection of guides, documentation, and articles

Select Badges

Select Supported Platforms

Select Status

selinux_policy (42) Versions 1.0.1 3.0.0 2.4.3 2.4.2 2.4.1 2.4.0 2.3.6 2.3.4 2.3.3 2.3.2 2.3.1 2.3.0 2.2.0 2.1.0 2.0.1 2.0.0 1.1.1 1.1.0 1.0.1 1.0.0 0.9.6 0.9.5 0.9.4 0.9.3 0.9.2 0.9.1 0.9.0 0.8.1 0.8.0 0.7.2 0.7.1 0.7.0 0.6.5 0.6.4 0.6.3 0.6.2 0.6.1 0.6.0 0.5.0 0.4.0 0.3.0 0.2.0 0.1.0 Follow26

SELinux Policy Cookbook

Requirements

Attributes

Usage

boolean

port

module

fcontext

permissive

Testing

Chef 11 Support

Contributing

License and Authors

Dependent cookbooks

Contingent cookbooks

selinuxpolicy CHANGELOG

1.0.1

1.0.0

0.9.6

0.9.5

0.9.4

0.9.3

0.9.2

0.9.1

0.9.0

0.8.1

0.8.0

0.7.2

0.7.1

0.7.0

0.6.5

0.6.4

0.6.3

0.6.2

0.6.1

0.6.0

0.5.0

0.4.0

0.3.0

0.2.0

0.1.0

Collaborator Number Metric 1.0.1 failed this metric Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Foodcritic Metric 1.0.1 passed this metric

Details

Updated September 21, 2016 Created on December 9, 2014

Supported Platforms

License

selinux_policy (42) Versions 1.0.1 Follow26

Collaborator Number Metric

1.0.1 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Foodcritic Metric

1.0.1 passed this metric