<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Comment-Spam on Inliniac</title>
    <link>https://inliniac.net/blog/tag/comment-spam/</link>
    <description>Recent content in Comment-Spam on Inliniac</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 23 Apr 2010 10:23:20 +0000</lastBuildDate>
    <atom:link href="https://inliniac.net/blog/tag/comment-spam/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Removing Trac ticket comment spam in Debian Lenny</title>
      <link>https://inliniac.net/blog/2010/04/23/removing-trac-ticket-comment-spam-in-debian-lenny/</link>
      <pubDate>Fri, 23 Apr 2010 10:23:20 +0000</pubDate>
      <guid>https://inliniac.net/blog/2010/04/23/removing-trac-ticket-comment-spam-in-debian-lenny/</guid>
      <description>&lt;p&gt;The Vuurmuur website runs Trac and overall I&amp;rsquo;m pretty happy with it. The only thing that Trac doesn&amp;rsquo;t do well, is dealing with spammers. Spammers target Trac a lot, so that&amp;rsquo;s a real problem.&lt;/p&gt;&#xA;&lt;p&gt;To prevent spammers from making it through, I run &lt;a href=&#34;http://projects.otaku42.de/wiki/ScallyWhack&#34;&gt;Scallywhack&lt;/a&gt; and a number of custom ModSecurity rules. So far, spams only made it through as new tickets in the ticket tracker, so I installed the &lt;a href=&#34;http://trac-hacks.org/wiki/TicketDeletePlugin&#34;&gt;TicketDeletePlugin&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Yesterday, I saw the first spam as a comment to an existing and valid ticket. Like tickets themselves, ticket comments can not be removed by Trac by default. Luckily, upstream Trac seems to have fixed this. I&amp;rsquo;m running Debian&amp;rsquo;s version of Trac 0.11.1 however, so I decided to patch that. The patches in the Trac ticket &lt;a href=&#34;http://trac.edgewall.org/ticket/454&#34;&gt;#454&lt;/a&gt; didn&amp;rsquo;t apply cleanly, so I had to patch it manually. To save others the work, it&amp;rsquo;s available here: &lt;a href=&#34;http://www.inliniac.net/files/trac_0.11.1-debian-comment_edit.patch&#34;&gt;http://www.inliniac.net/files/trac_0.11.1-debian-comment_edit.patch&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Update on using realtime blacklists with ModSecurity</title>
      <link>https://inliniac.net/blog/2007/03/01/update-on-using-realtime-blacklists-with-modsecurity/</link>
      <pubDate>Thu, 01 Mar 2007 08:04:55 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/03/01/update-on-using-realtime-blacklists-with-modsecurity/</guid>
      <description>&lt;p&gt;A few days ago I posted a blog article about stopping comment spam with ModSecurity using realtime blacklists (rbl). While the approach was working, I noted having problems with rules when I tried to match on POST methods in HTTP requests.&lt;/p&gt;&#xA;&lt;p&gt;Luckily, ModSecurity creator Ivan Ristic was quick to point out where the problem is. I&amp;rsquo;m using the Core Ruleset for ModSecurity, and one thing that ruleset does is use the &amp;rsquo;lowercase&amp;rsquo; transformation. This converts all text from arguments to lowercase, so my ^POST$ match would never be able to match. So like Ivan suggested, using ^post$ solved this part.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Blocking comment spam using ModSecurity and realtime blacklists</title>
      <link>https://inliniac.net/blog/2007/02/23/blocking-comment-spam-using-modsecurity-and-realtime-blacklists/</link>
      <pubDate>Thu, 22 Feb 2007 22:25:45 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/02/23/blocking-comment-spam-using-modsecurity-and-realtime-blacklists/</guid>
      <description>Spammers are known to use compromised hosts from all over the world to send their messages. Many people are blocking or scoring email spam based on realtime blacklist (rbl), which contain ipaddresses of these known bad hosts. In my experience this works fairly well for email. A while ago I noticed in the ModSecurity documentation for version 2.0 that ModSecurity features an operator called &lt;a href=&#34;http://modsecurity.org/documentation/modsecurity-apache/2.1.0-rc6/html-multipage/08-operators.html#N11490&#34;&gt;rbl&lt;/a&gt;, that can be used to check the ipaddress of a visitor with a rbl. So I decided to see if I could use the realtime blacklists to prevent comment spam on my blog. Turns out this works great! In this post I&amp;rsquo;ll show how to get it working.</description>
    </item>
  </channel>
</rss>
