<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Modsecurity on Daniel Pomfret</title>
    <link>https://pomfret.uk/tags/modsecurity/</link>
    <description>Recent content in Modsecurity on Daniel Pomfret</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>© Daniel Pomfret</copyright>
    <lastBuildDate>Tue, 06 Feb 2018 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://pomfret.uk/tags/modsecurity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>cPanel Error:The system experienced the following error when it attempted to install the “OWASP ModSecurity Core Rule Set V3.0” vendor</title>
      <link>https://pomfret.uk/posts/cpanel-errorthe-system-experienced-following-error-attempted-install-owasp-modsecurity-core-rule-set-v3-0-vendor/</link>
      <pubDate>Tue, 06 Feb 2018 00:00:00 +0000</pubDate>
      <guid>https://pomfret.uk/posts/cpanel-errorthe-system-experienced-following-error-attempted-install-owasp-modsecurity-core-rule-set-v3-0-vendor/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve noticed that since upgrading cPanel to v68.0.28 our ModSecurity Vendors have dropped off, and no longer available in the interface, and the rules are no longer available for Apache.&lt;/p&gt;&#xA;&lt;p&gt;When trying to add the OWASP Ruleset (Vendor) back, I get the following error message.&lt;/p&gt;&#xA;&lt;p&gt;Error:The system experienced the following error when it attempted to install the “OWASP ModSecurity Core Rule Set V3.0” vendor: API failure: The system could not validate the new Apache configuration because httpd exited with a nonzero value. Apache produced the following error: httpd: Syntax error on line 208 of /etc/apache2/conf/httpd.conf: Syntax error on line 32 of /etc/apache2/conf.d/modsec2.conf: Syntax error on line 29 of /etc/apache2/conf.d/modsec/modsec2.cpanel.conf: Could not open configuration file /etc/apache2/conf.d/modsec_vendor_configs/OWASP/modsecurity_crs_10_setup.conf: No such file or directory&lt;/p&gt;</description>
    </item>
    <item>
      <title>Comodo WAF: mod_security2: Failed to write to DBM file &#34;/var/cache/modsecurity/ip&#34;: Invalid argument</title>
      <link>https://pomfret.uk/posts/comodo-waf-mod_security2-failed-write-dbm-file-varcachemodsecurityip-invalid-argument/</link>
      <pubDate>Tue, 17 Oct 2017 00:00:00 +0000</pubDate>
      <guid>https://pomfret.uk/posts/comodo-waf-mod_security2-failed-write-dbm-file-varcachemodsecurityip-invalid-argument/</guid>
      <description>&lt;p&gt;After seeing apache using all it&amp;rsquo;s threads, and connections not timing out as they should, I looked at the apache error_log and found the following error.&lt;/p&gt;&#xA;&lt;p&gt;Message: collection_store: Failed to write to DBM file &amp;ldquo;/var/cache/modsecurity/ip&amp;rdquo;: Invalid argument&lt;/p&gt;&#xA;&lt;p&gt;I not only saw this on cPanel servers, but on Plesk and plain LAMP (with mod_security and comodo waf installed).&lt;/p&gt;&#xA;&lt;p&gt;It looks like Comodo somehow released a broken update, that caused the /var/cache/modsecurity/ip.pag to corrupt (that&amp;rsquo;s my guess).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
