https://shocksolution.com/tags/selinux/Recent content in Selinux on shocksolution.comHugoen-usSun, 26 Aug 2018 20:17:21 +0000https://shocksolution.com/posts/optimize-the-wordfence-firewall/Sun, 26 Aug 2018 20:17:21 +0000https://shocksolution.com/posts/optimize-the-wordfence-firewall/<p>I use Wordfence as a Wordpress security solution. Even the free version has a comprehensive set of features, and the premium version is even better. It&rsquo;s very easy to install and configure Wordfence as a regular plugin. However, the step to &ldquo;Optimize the Wordfence firewall&rdquo; fails for many people. This is not the fault of Wordfence, since different steps may be required depending on how your web server is configured. My solution is for those who are hosting their own Wordpress, but may be helpful to other situations. Please note that these instructions affect the security of your system, and are aimed at users with intermediate to advanced Linux knowledge.</p>https://shocksolution.com/posts/new-relic-apm-on-fedora-centos-redhat-with-selinux-enforcing-solved/Thu, 14 Jun 2018 03:27:28 +0000https://shocksolution.com/posts/new-relic-apm-on-fedora-centos-redhat-with-selinux-enforcing-solved/<p>I found the solution for getting the New Relic APM Agent to run on a CentOS 7 system with SELinux Enforcing. The only SELinux modification you have to make is to change the context of the log file directory <strong>/var/log/newrelic</strong>. You can temporarily make these changes with the chcon command: [code lang=&ldquo;bash&rdquo;] chcon -R -t httpd_log_t /var/log/newrelic/ [/code] Kill any running instances of newrelic-daemon. If you&rsquo;re using New Relic&rsquo;s recommended default setup, make sure that the file /etc/newrelic/newrelic.cfg does <strong>not</strong> exist. Verify that all required values in /etc/php.d/newrelic.ini are correct (especially the license key and the application name). Finally, restart httpd: [code lang=&ldquo;bash&rdquo;] systemctl restart httpd [/code] If that works, you should see output in both /var/log/newrelic/newrelic-daemon.log and /var/log/newrelic/php_agent.log. Now, make this file context change persistent, and verify the result: [code lang=&ldquo;bash&rdquo;] semanage fcontext &ndash;add &ndash;type httpd_log_t &ldquo;/var/log/newrelic(/.*)?&rdquo; restorecon -RF /var/log/newrelic/ ls -laZ /var/log/newrelic/ [/code] When you restart Apache, it spawns the newrelic-daemon processes, which communicate with APM via the socket file /tmp/.newrelic.sock. You really don&rsquo;t want to run the newrelic-daemon processes via systemd if you can avoid it. The resulting process tree should look like this:</p>