<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Snort on Inliniac</title>
    <link>https://inliniac.net/blog/category/snort/</link>
    <description>Recent content in Snort on Inliniac</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 24 Sep 2011 16:09:24 +0000</lastBuildDate>
    <atom:link href="https://inliniac.net/blog/category/snort/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>RAID 2011 Thoughts</title>
      <link>https://inliniac.net/blog/2011/09/24/raid-2011-thoughts/</link>
      <pubDate>Sat, 24 Sep 2011 16:09:24 +0000</pubDate>
      <guid>https://inliniac.net/blog/2011/09/24/raid-2011-thoughts/</guid>
      <description>&lt;p&gt;The last few days I&amp;rsquo;ve been at the Recent Advances in Intrusion Detection (RAID) conference in California. Overall it has been a very pleasant and interesting experience. The nice California weather was certainly helping a lot!&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen all talks and some were very interesting. However, being a Suricata IDS developer, I was not just interested in research for the hell of it, but I was actively scouting for ideas we could implement into Suricata. In this respect the conference was highly disappointing. Although with some of the talks I thought the idea was applicable in general security, like Erik Bosmans high speed memory tainting detection, I found nothing like that for NIDS.&lt;/p&gt;</description>
    </item>
    <item>
      <title>On Suricata performance</title>
      <link>https://inliniac.net/blog/2010/07/22/on-suricata-performance/</link>
      <pubDate>Thu, 22 Jul 2010 08:26:54 +0000</pubDate>
      <guid>https://inliniac.net/blog/2010/07/22/on-suricata-performance/</guid>
      <description>&lt;p&gt;Lots of fuzz in the media about Suricata&amp;rsquo;s performance versus Snort yesterday. Some claiming Suricata is much faster, others claiming Snort is much faster.&lt;/p&gt;&#xA;&lt;p&gt;At this point I really don&amp;rsquo;t care much. What the Suricata development by the OISF has shown in my opinion is that we&amp;rsquo;ve managed to create a very promising new Open Source project out here. In little over a year, funded for about $600k by the US government and with heavy (and growing) industry support, we&amp;rsquo;ve produced a new IDS/IPS engine mostly compatible with Snort but build on a all new code base an incorporating some very interesting fresh ideas. We&amp;rsquo;re already seeing a community form around our project with a lot of support from that new community.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ohloh</title>
      <link>https://inliniac.net/blog/2010/06/30/ohloh/</link>
      <pubDate>Wed, 30 Jun 2010 08:47:54 +0000</pubDate>
      <guid>https://inliniac.net/blog/2010/06/30/ohloh/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://www.ohloh.net/&#34;&gt;Ohloh&lt;/a&gt; is a pretty cool site for keeping track of projects and programmers. It&amp;rsquo;s an easy way to keep track of the development in a project and gives a nice indication of how actively it&amp;rsquo;s being developed. It has some social networkish features too, such as individual developers giving each other &amp;ldquo;kudos&amp;rdquo;.&lt;/p&gt;&#xA;&lt;p&gt;The code analysis is pretty nice: it gives statistics on code base size, growth, comment ratio, languages used, etc. Per developer it tracks quite a few stats as well.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Checking out SourceForge&#39;s Marketplace</title>
      <link>https://inliniac.net/blog/2009/01/06/checking-out-sourceforges-marketplace/</link>
      <pubDate>Tue, 06 Jan 2009 14:26:31 +0000</pubDate>
      <guid>https://inliniac.net/blog/2009/01/06/checking-out-sourceforges-marketplace/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve registered myself as a seller of services on SourceForge&amp;rsquo;s Open Source &lt;a href=&#34;http://sourceforge.net/services/buy/index.php&#34;&gt;Marketplace&lt;/a&gt;. I&amp;rsquo;ve done so offering software development services for the &lt;a href=&#34;http://www.snort.org/&#34;&gt;Snort&lt;/a&gt;, &lt;a href=&#34;http://snort-inline.sf.net/&#34;&gt;Snort_inline&lt;/a&gt; and &lt;a href=&#34;http://www.vuurmuur.org&#34;&gt;Vuurmuur&lt;/a&gt; projects. I was wondering if anyone has any experience (good or bad) with the Marketplace system, either as a buyer or seller of services. Let me know!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Available for contract work</title>
      <link>https://inliniac.net/blog/2009/01/05/available-for-contract-work/</link>
      <pubDate>Mon, 05 Jan 2009 13:26:06 +0000</pubDate>
      <guid>https://inliniac.net/blog/2009/01/05/available-for-contract-work/</guid>
      <description>&lt;p&gt;This year there will be a lot of work that needs to be done for the &lt;a href=&#34;http://www.openinfosecfoundation.org/&#34;&gt;Open Infosec Foundation&lt;/a&gt;. And like I wrote a few days ago, a lot of work is already being done. However, most of it is unpaid at this time as it will be some months before our funding comes in. So at least until then I&amp;rsquo;m available and looking for contract work.&lt;/p&gt;&#xA;&lt;p&gt;For the last two years I&amp;rsquo;ve been doing work as a contractor in the (open source) security field. My experience is mostly in coding in C and Perl, primarily on &lt;a href=&#34;http://www.snort.org/&#34;&gt;Snort&lt;/a&gt; and &lt;a href=&#34;http://snort-inline.sf.net/&#34;&gt;Snort_inline&lt;/a&gt;. Recently I created the (Perl language) &lt;a href=&#34;http://doc.emergingthreats.net/bin/view/Main/SidReporter&#34;&gt;SidReporter&lt;/a&gt; program for &lt;a href=&#34;http://www.emergingthreats.net/&#34;&gt;Emerging Threats&lt;/a&gt;. Areas I worked in: IPv6 IDS/IPS coding, signature writing, Web Application Firewalls, threading, bandwidth accounting, and more&amp;hellip;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Snort_inline updated to 2.8.2.1 in SVN</title>
      <link>https://inliniac.net/blog/2008/06/18/snort_inline-updated-to-2821-in-svn/</link>
      <pubDate>Wed, 18 Jun 2008 07:41:48 +0000</pubDate>
      <guid>https://inliniac.net/blog/2008/06/18/snort_inline-updated-to-2821-in-svn/</guid>
      <description>&lt;p&gt;This morning I updated our Snort_inline codebase with SourceFire&amp;rsquo;s just released 2.8.2.1 version. See the original changelogs here: &lt;a href=&#34;http://www.snort.org/docs/release_notes/release_notes_281.txt&#34;&gt;2.8.1&lt;/a&gt;, &lt;a href=&#34;http://www.snort.org/docs/release_notes/release_notes_282.txt&#34;&gt;2.8.2&lt;/a&gt;, &lt;a href=&#34;http://www.snort.org/docs/release_notes/release_notes_2821.txt&#34;&gt;2.8.2.1&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Also Richard Bejtlich and Nr have good posts about the improvements of the last versions. See Richards post about a fixed frag3 vulnerability &lt;a href=&#34;http://taosecurity.blogspot.com/2008/05/snort-evasion-vulnerability-in-frag3.html&#34;&gt;here&lt;/a&gt; and see Nr&amp;rsquo;s post &lt;a href=&#34;http://eatingsecurity.blogspot.com/2008/05/snort-281-changes-and-upgrading.html&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Please note that our SVN code has seen limited testing so far, so be careful! Please report any issues!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Snort_inline 2.8 status</title>
      <link>https://inliniac.net/blog/2008/02/26/snort_inline-28-status/</link>
      <pubDate>Tue, 26 Feb 2008 17:12:15 +0000</pubDate>
      <guid>https://inliniac.net/blog/2008/02/26/snort_inline-28-status/</guid>
      <description>&lt;p&gt;A while ago I wrote about porting Snort_inline to 2.8.0.1. That worked well, however we are still trying to resolve some issues. Especially in stickydrop, that is just broken right now. Also, SourceFire released 2.8.0.2 last week, so we need to update to that too.&lt;/p&gt;&#xA;&lt;p&gt;First however, I will be traveling to California this week. I will be meeting Will there, so I&amp;rsquo;ll try to get him to fix that damn code ;-)&lt;/p&gt;</description>
    </item>
    <item>
      <title>Snort_inline updated to 2.8.0.1 in SVN</title>
      <link>https://inliniac.net/blog/2008/01/09/snort_inline-updated-to-2801-in-svn/</link>
      <pubDate>Wed, 09 Jan 2008 15:41:19 +0000</pubDate>
      <guid>https://inliniac.net/blog/2008/01/09/snort_inline-updated-to-2801-in-svn/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve just committed an update to Snort_inline&amp;rsquo;s SVN. It brings it to the Snort 2.8.0.1 level. It supports both IPv4 and IPv6 on IPQ and NFQ. I have not been able to test IPFW on IPv6, so I don&amp;rsquo;t think that will work currently.&lt;/p&gt;&#xA;&lt;p&gt;This update removes the libdnet dependency and replaces it with libnet 1.1. To be able to send ICMPv6 unreachable packets you will need the libnet 1.1 patch I wrote a while ago. You can find that &lt;a href=&#34;http://www.inliniac.net/blog/2007/10/16/libnet-11-ipv6-fixes-and-additions.html&#34;&gt;here&lt;/a&gt;. Get the latest Snort_inline by checking out SVN:&lt;/p&gt;</description>
    </item>
    <item>
      <title>New Snortsam patch for Snort 2.8.0.1</title>
      <link>https://inliniac.net/blog/2008/01/08/new-snortsam-patch-for-snort-2801/</link>
      <pubDate>Tue, 08 Jan 2008 12:30:53 +0000</pubDate>
      <guid>https://inliniac.net/blog/2008/01/08/new-snortsam-patch-for-snort-2801/</guid>
      <description>&lt;p&gt;Matt Jonkman of &lt;a href=&#34;http://www.emergingthreats.net/&#34;&gt;Emerging Threats&lt;/a&gt; asked me to have a look at the existing Snortsam 2.8.0.1 patch as people were continuing to report problems with it. I updated it to compile without compiler warnings, build cleanly with debugging enabled, build cleanly with Snort&amp;rsquo;s IPv6 support enabled and added a check so it won&amp;rsquo;t act on alerts in IPv6 packets since the Snortsam framework does not support IPv6. Finally I removed the patch script so it&amp;rsquo;s provided as a &amp;rsquo;normal&amp;rsquo; diff. Here is the patch: &lt;a href=&#34;http://www.inliniac.net/files/snortsam-2.8.0.1.diff&#34;&gt;http://www.inliniac.net/files/snortsam-2.8.0.1.diff&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Working on Snort_inline 2.8.0.1</title>
      <link>https://inliniac.net/blog/2007/12/22/working-on-snort_inline-2801/</link>
      <pubDate>Sat, 22 Dec 2007 12:49:20 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/12/22/working-on-snort_inline-2801/</guid>
      <description>&lt;p&gt;The last week I&amp;rsquo;ve been working on bringing Snort_inline to the Snort 2.8.0.1 level, including it&amp;rsquo;s IPv6 support. I&amp;rsquo;m almost ready to commit it to SVN, there are just some issues I need to fix in the inline specific code. The code will get rid of libdnet and use libnet 1.1 for sending reset/reject packets for both IPv4 and IPv6. After committing I will start working on getting the IPv6 features I wrote for NitroSecurity into this tree. This includes more matches, tunnel decoding (including for example the freenet6 tunnel, etc). So stay tuned!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Matt Jonkman leaves Bleeding Edge</title>
      <link>https://inliniac.net/blog/2007/11/17/matt-jonkman-leaves-bleeding-edge/</link>
      <pubDate>Sat, 17 Nov 2007 12:05:56 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/11/17/matt-jonkman-leaves-bleeding-edge/</guid>
      <description>&lt;p&gt;Matt Jonkman is stepping out of the &lt;a href=&#34;http://www.bleedingthreats.net/&#34;&gt;Bleeding Edge project&lt;/a&gt;. He announced this &lt;a href=&#34;http://www.bleedingthreats.net/index.php/2007/11/17/im-leaving-bleeding-threats/&#34;&gt;here&lt;/a&gt;. Apparently &lt;a href=&#34;http://sensorynetworks.com/&#34;&gt;Sensory Networks&lt;/a&gt;, one of the sponsors of the project, now owns it. It will be interesting to see if they will continue it, and if so, how. Honestly, I&amp;rsquo;m a bit skeptical, since to my knowledge not many Sensory people are directly involved at this moment. Still I believe Sensory consists of good people. I did a contract job for them about a year ago, and enjoyed working with them.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Libnet 1.1 IPv6 fixes and additions</title>
      <link>https://inliniac.net/blog/2007/10/16/libnet-11-ipv6-fixes-and-additions/</link>
      <pubDate>Tue, 16 Oct 2007 21:35:11 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/10/16/libnet-11-ipv6-fixes-and-additions/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://www.packetfactory.net/libnet/&#34;&gt;Libnet&lt;/a&gt; is a cool packet crafting tool, used by &lt;a href=&#34;http://www.snort.org/&#34;&gt;Snort&lt;/a&gt; to send TCP reset packets and ICMP unreachable packets as part of active responses. Libnet 1.1 supports IPv6 which is what I needed for my work. After some reading and testing there were a few problems. First, while possible to send TCP reset packets, the packets didn&amp;rsquo;t have a correct checksum and debugging this with valgrind showed lots of memory errors. Second, ICMPv6 was only partly implemented. The libnet_build_* functions for it are missing. This is, by the way, quite a common picture. Many libraries and projects have some support for IPv6, but generally incomplete and less well tested.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using Modsec2sguil for HTTP transaction logging revisited</title>
      <link>https://inliniac.net/blog/2007/08/22/using-modsec2sguil-for-http-transaction-logging-revisited/</link>
      <pubDate>Wed, 22 Aug 2007 20:05:34 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/08/22/using-modsec2sguil-for-http-transaction-logging-revisited/</guid>
      <description>&lt;p&gt;Recently I wrote about the idea to log all HTTP transactions into Sguil using my Modsec2sguil agent. I&amp;rsquo;ve implemented this in the current &lt;a href=&#34;http://www.inliniac.net/modsec2sguil/&#34;&gt;0.8-dev5&lt;/a&gt; release and it works very well. All events go into Sguil smoothly and I&amp;rsquo;ve not experienced slowdowns on the webserver. I&amp;rsquo;ve been running it for almost a week now, like to share the first experiences here.&lt;/p&gt;&#xA;&lt;p&gt;I find it to be quite useful. When receiving an alert, it is perhaps more interesting to see what else was done from that ipaddress than to see what was blocked (unless you are suspecting a false positive of course). One area I find to be useful is when I&amp;rsquo;m creating rules against comment spam on this blog. By seeing all properties of a spam message I can create better rules. For example on broken user-agents or weird codes inserted into the comment field of Wordpress.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Snort license changes revisited</title>
      <link>https://inliniac.net/blog/2007/07/16/snort-license-changes-revisited/</link>
      <pubDate>Mon, 16 Jul 2007 21:40:29 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/07/16/snort-license-changes-revisited/</guid>
      <description>&lt;p&gt;Today I noticed that Snort 2.7.0 was quietly released on July 12th. I have a problem with this release, a licensing problem. I have written about my issues with Sourcefires Snort licensing before &lt;a href=&#34;http://www.inliniac.net/blog/2007/06/29/snort-and-the-gpl-version-3.html&#34;&gt;here&lt;/a&gt; and on the mailinglist as well, &lt;a href=&#34;http://article.gmane.org/gmane.comp.security.ids.snort.general/26768/&#34;&gt;here&lt;/a&gt;. They seem to have listened a little bit, since they are no longer claiming copyright of Todd C. Millers BSD licensed strlcpy and strlcat implementation. Sadly, our other complaints are completely ignored.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Snort and the GPL version 3</title>
      <link>https://inliniac.net/blog/2007/06/29/snort-and-the-gpl-version-3/</link>
      <pubDate>Fri, 29 Jun 2007 20:21:24 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/06/29/snort-and-the-gpl-version-3/</guid>
      <description>&lt;p&gt;Today the final version of the &lt;a href=&#34;http://www.gnu.org/licenses/gpl.html&#34;&gt;GPL version 3&lt;/a&gt; was released. This is interesting from many perspectives, and one of them is Snort licensing. Much has been written about Snort and the GPL lately, but that was all about new license language introduced with Snort 3.0 alpha and not about the currently maintained and developed 2.6 and 2.7 branches. When I&amp;rsquo;m talking about Snort here and now, I mean those versions prior to 3.0.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Debian should update their Snort package</title>
      <link>https://inliniac.net/blog/2007/06/16/debian-should-update-their-snort-package/</link>
      <pubDate>Sat, 16 Jun 2007 12:37:13 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/06/16/debian-should-update-their-snort-package/</guid>
      <description>&lt;p&gt;Last week there was some discussion in the #snort IRC channel about why Debian distributes such an ancient version of Snort, namely version 2.3.3. This release is more than 2 years old and no longer supported by &lt;a href=&#34;http://www.sourcefire.com&#34;&gt;SourceFire&lt;/a&gt;. The snort.org website says about the old versions:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;You should not use these unless you &lt;strong&gt;really&lt;/strong&gt; know what you are doing. Many bugs may have been fixed, including remote vulnerabilities&lt;/p&gt;&lt;/blockquote&gt;&#xA;&lt;p&gt;Even though Debian is able to fix any security bugs themselves, and they don&amp;rsquo;t need to rely on SourceFire for this, Snort 2.3.3 is still going to be inferior to the recent 2.6.1.5. Why? Well recent Snort versions have many more and improved detection options, such as a better pattern matcher, defragmentation preprocessor, improved stream preprocessor, smtp plugin, etc, etc.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Snort_inline updated to 2.6.1.5 in SVN</title>
      <link>https://inliniac.net/blog/2007/05/14/snort_inline-updated-to-2615-in-svn/</link>
      <pubDate>Mon, 14 May 2007 20:02:12 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/05/14/snort_inline-updated-to-2615-in-svn/</guid>
      <description>&lt;p&gt;SourceFire just released Snort 2.6.1.5 so I have updated our patch to that. You can get it by checking out SVN with the following command:&lt;/p&gt;&#xA;&lt;p&gt;svn co &lt;a href=&#34;https://snort-inline.svn.sourceforge.net/svnroot/snort-inline/trunk&#34;&gt;https://snort-inline.svn.sourceforge.net/svnroot/snort-inline/trunk&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Check it out! :)&lt;/p&gt;</description>
    </item>
    <item>
      <title>Differences between Snort and Snort_inline</title>
      <link>https://inliniac.net/blog/2007/05/14/differences-between-snort-and-snort_inline/</link>
      <pubDate>Mon, 14 May 2007 17:05:41 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/05/14/differences-between-snort-and-snort_inline/</guid>
      <description>&lt;p&gt;Every few weeks the same question comes up: what is the difference between Snort in inline mode and Snort_inline. This makes sense, because the Snort_inline documentation and website fail to explain it. In this post I will try to highlight the main differences. In general I can say that we try to develop Snort_inline as a patchset on top of Snort. Snort_inline is focused at improving the &lt;em&gt;inline&lt;/em&gt; part of Snort. Originally of course, Snort&amp;rsquo;s &lt;em&gt;inline&lt;/em&gt; capabilities were developed in the Snort_inline project. With Snort 2.3.0RC1 they were merged into mainline Snort.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Snort_inline updated to 2.6.1.4 in SVN</title>
      <link>https://inliniac.net/blog/2007/04/20/snort_inline-updated-to-2614-in-svn/</link>
      <pubDate>Fri, 20 Apr 2007 16:47:33 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/04/20/snort_inline-updated-to-2614-in-svn/</guid>
      <description>&lt;p&gt;After moving, which went fine, I now finally have some real coding time again. The last week I have been updating and fixing various parts of Snort_inline. The most important change was the update to Snort version 2.6.1.4, which contains security fixes. William also found an issue with the Stream4inline code. The issue was that the memcap that the admin sets to limit the amount of memory used by stream4 wasn&amp;rsquo;t properly enforced.&lt;/p&gt;</description>
    </item>
    <item>
      <title>New WordPress issue &#43; Snort and ModSecurity rules</title>
      <link>https://inliniac.net/blog/2007/03/20/new-wordpress-issue-modsecurity-rule/</link>
      <pubDate>Tue, 20 Mar 2007 18:03:21 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/03/20/new-wordpress-issue-modsecurity-rule/</guid>
      <description>&lt;p&gt;I just read about a new issue with &lt;a href=&#34;http://www.wordpress.org/&#34;&gt;WordPress&lt;/a&gt; &lt;a href=&#34;http://www.securityfocus.com/archive/1/463291&#34;&gt;here&lt;/a&gt; at SecurityFocus. It&amp;rsquo;s a potential credential stealing vulnerability, so I quickly created these &lt;a href=&#34;http://www.modsecurity.org&#34;&gt;ModSecurity&lt;/a&gt; 2 rules:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;SecDefaultAction &amp;ldquo;log,deny,status:403,phase:2,t:lowercase,t:escapeSeqDecode&amp;rdquo;&lt;/strong&gt;&#xA;&lt;strong&gt;SecRule REQUEST_FILENAME &amp;ldquo;/wp-login.php$&amp;rdquo; &amp;ldquo;chain,msg:&amp;lsquo;WORDPRESS wp-login.php redirect_to credentials stealing attempt&amp;rsquo;,severity:2,t:normalisePath&amp;rdquo;&lt;/strong&gt;&#xA;&lt;strong&gt;SecRule ARGS_NAMES &amp;ldquo;^redirect_to$&amp;rdquo; &amp;ldquo;chain&amp;rdquo;&lt;/strong&gt;&#xA;&lt;strong&gt;SecRule ARGS:redirect_to &amp;ldquo;(ht|f)tps?://&amp;rdquo;&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;I can still login to my WordPress install, so it seems that the rule does no harm. Use at your own risk!&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Update&lt;/strong&gt;: I&amp;rsquo;ve created a Snort rule as well:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Experimenting with IPv6</title>
      <link>https://inliniac.net/blog/2007/03/13/experimenting-with-ipv6/</link>
      <pubDate>Tue, 13 Mar 2007 19:04:51 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/03/13/experimenting-with-ipv6/</guid>
      <description>&lt;p&gt;My &lt;a href=&#34;http://www.xs4all.nl/&#34;&gt;ISP&lt;/a&gt; is one of the few here in the Netherlands that provides a IPv6 tunnel broker. I have played with it some during the last year or so, but now decided to get a little more serious with it. So I&amp;rsquo;ve decided to enable it for my blog. When opening up my site to IPv6 one thing that is important is security. I will describe the status of IPv6 support of my current setup:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Setting up Subversion for Snort_inline</title>
      <link>https://inliniac.net/blog/2007/01/17/setting-up-subversion-for-snort_inline/</link>
      <pubDate>Wed, 17 Jan 2007 11:02:31 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/01/17/setting-up-subversion-for-snort_inline/</guid>
      <description>&lt;p&gt;A reason for the slow development of Snort_inline is that we still weren&amp;rsquo;t using a version control system. Being sick of this, I decided to setup a private Subversion server to see how we could best use it. One thing that complicates the use of such a system is the fact that we maintain a patch on top of source code not maintained by ourselves. So the system must be able to deal with upstream sourcecode updates.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Detecting and blocking Phishing with Snort and ClamAV</title>
      <link>https://inliniac.net/blog/2006/11/12/detecting-and-blocking-phishing-with-snort-and-clamav/</link>
      <pubDate>Sun, 12 Nov 2006 18:12:31 +0000</pubDate>
      <guid>https://inliniac.net/blog/2006/11/12/detecting-and-blocking-phishing-with-snort-and-clamav/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://www.clamav.net/&#34;&gt;ClamAV&lt;/a&gt; is a great Open Source virusscanner that can be used for detecting virusses from &lt;a href=&#34;http://www.snort.org/&#34;&gt;Snort&lt;/a&gt; or &lt;a href=&#34;http://snort-inline.sf.net/&#34;&gt;Snort_inline&lt;/a&gt; using the &lt;a href=&#34;http://www.bleedingthreats.net/staticpages/index.php?page=snort-clamav&#34;&gt;ClamAV preprocessor&lt;/a&gt;. However, by using the anti-phishing and anti-scam signatures by &lt;a href=&#34;http://www.sanesecurity.com/clamav/&#34;&gt;SaneSecurity&lt;/a&gt;, this combination can also be used to detect and block phishing and scam attempts. Here is how to set it up.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve decided to run this on my gateway, which is a slow machine. Because I don&amp;rsquo;t want all my traffic to slow down to much, I&amp;rsquo;m not going to run the ClamAV defs, only the anti-phishing ones. The default location of the defs on my Debian Sarge system is /var/lib/clamav, so I&amp;rsquo;ve created a new directory called &amp;lsquo;/var/lib/clamav-phish&amp;rsquo;. Next I&amp;rsquo;ve downloaded the defs from &lt;a href=&#34;http://www.sanesecurity.com/clamav/downloads.htm&#34;&gt;SaneSecurity&lt;/a&gt;. After unzipping them and the defs were ready.&lt;/p&gt;</description>
    </item>
    <item>
      <title>New ClamAV patch for Snort 2.6.0.2</title>
      <link>https://inliniac.net/blog/2006/11/06/new-clamav-patch-for-snort-2602/</link>
      <pubDate>Mon, 06 Nov 2006 08:11:50 +0000</pubDate>
      <guid>https://inliniac.net/blog/2006/11/06/new-clamav-patch-for-snort-2602/</guid>
      <description>&lt;p&gt;Okay, so i&amp;rsquo;m &lt;a href=&#34;http://marc.theaimsgroup.com/?l=snort-users&amp;amp;m=116278345729435&amp;amp;w=2&#34;&gt;fired at patch making&lt;/a&gt; because I screwed up the last patch. I never bothered to test it with Snort in inline-mode. This didn&amp;rsquo;t work because we included all kinds of specific features for Snort_inline into the preprocessor. I have updated the patch.&lt;/p&gt;&#xA;&lt;p&gt;Get it here: &lt;a href=&#34;http://www.inliniac.net/files/061106-snort-2.6.0.2-clamav.diff.gz&#34;&gt;http://www.inliniac.net/files/061106-snort-2.6.0.2-clamav.diff.gz&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Will, am I re-hired now? Pretty please??? ;-)&lt;/p&gt;</description>
    </item>
    <item>
      <title>Rules for reported Tikiwiki vulnerabilities</title>
      <link>https://inliniac.net/blog/2006/11/02/rules-for-reported-tikiwiki-vulnerabilities/</link>
      <pubDate>Thu, 02 Nov 2006 11:02:52 +0000</pubDate>
      <guid>https://inliniac.net/blog/2006/11/02/rules-for-reported-tikiwiki-vulnerabilities/</guid>
      <description>&lt;p&gt;Yesterday there was a mail to the bugtraq mailinglist about two types of vulnerabilties in Tikiwiki 1.9.5. The most serious is a claimed MySQL password disclosure through a special URI. The second is an XSS, also through an special URI. The message can be found &lt;a href=&#34;http://www.securityfocus.com/archive/1/450268/30/0&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;I wrote &amp;lsquo;claimed password disclosure&amp;rsquo;, because on the Tikiwiki server I run, I could not reproduce it. With that I mean the password disclosure, since I do see that Tikiwiki gives an error that reveals other information, most notably the location of the website on the local filesystem.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ClamAV preprocessor patch for Snort 2.6.0.2</title>
      <link>https://inliniac.net/blog/2006/10/07/clamav-preprocessor-patch-for-snort-2602/</link>
      <pubDate>Sat, 07 Oct 2006 19:21:21 +0000</pubDate>
      <guid>https://inliniac.net/blog/2006/10/07/clamav-preprocessor-patch-for-snort-2602/</guid>
      <description>&lt;p&gt;Since William and I are working on Snort Inline 2.6.0.2 this weekend we also have a working ClamAV for 2.6.0.2. So I took a few minutes to patch it against Snort 2.6.0.2 as well. Nothing changed in it, it is just a port to 2.6.0.2.&lt;/p&gt;&#xA;&lt;p&gt;Get it here: &lt;a href=&#34;http://www.inliniac.net/files/061007-snort-2.6.0.2-clamav.diff.gz&#34;&gt;http://www.inliniac.net/files/061007-snort-2.6.0.2-clamav.diff.gz&lt;/a&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
