SELinux https://www.tag1consulting.com/ en Manage it with Puppet https://www.tag1consulting.com/blog/stop-disabling-selinux-manage-it-with-puppet <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"> Once upon a time, many years ago, I wrote a blog post titled Stop Disabling SELinux! as a response to seeing many users, hosting companies, and development shops disabling SELinux as a first resort without any consideration of the increased security it was bringing them. The post outlines -- in a few easy steps -- how to configure SELinux for a common Drupal setup. But it's applicable to any LAMP application (plus memcached). I'm still a big proponent of running SELinux, and continue to encourage its use. In that same vein, I'd like to share how we at Tag1 Consulting typically deploy SELinux configuration using Puppet. Levering a configuration management system such as Puppet enables us to deploy SELinux configuration across many hosts with minimal work, as well as ensuring nothing is ever missed by making configuration changes manually -- a must for any scalable (and stable!) infrastructure. Too Long; Didn't Read Version "Holy shit, I'm not going to read a multiple-page blog post just to see what this guy has to say about Puppet and SELinux, just show me the code!" OK, OK! I understand I can be long winded at times. If you just want to see Puppet... <div class="more-link"><a href="/blog/stop-disabling-selinux-manage-it-with-puppet" class="more-link" aria-label="Read more about Manage it with Puppet" hreflang="en">Read more</a></div> </div> <span><a title="View user profile." href="/user/jeff-sheltren">Jeff</a></span> <span><time datetime="2017-02-21T08:10:57-08:00" title="Tuesday, February 21, 2017 - 08:10">Tue, 02/21/2017 - 08:10</time> </span> Tue, 21 Feb 2017 16:10:57 +0000 Jeff 75 at https://www.tag1consulting.com Stop Disabling SELinux! https://www.tag1consulting.com/blog/stop-disabling-selinux <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"> I see a lot of people coming by #centos and similar channels asking for help when they’re experiencing a problem with their Linux system. It amazes me how many people describe their problem, and then say something along the lines of, “and I disabled SELinux...”. Most of the time SELinux has nothing to do with the problem, and if SELinux is the cause of the problem, why would you throw out the extra security by disabling it completely rather than configuring it to work with your application? <div class="more-link"><a href="/blog/stop-disabling-selinux" class="more-link" aria-label="Read more about Stop Disabling SELinux!" hreflang="en">Read more</a></div> </div> <span><a title="View user profile." href="/user/jeff-sheltren">Jeff</a></span> <span><time datetime="2011-12-22T07:48:37-08:00" title="Thursday, December 22, 2011 - 07:48">Thu, 12/22/2011 - 07:48</time> </span> Thu, 22 Dec 2011 15:48:37 +0000 Jeff 38 at https://www.tag1consulting.com