<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Debian on Inliniac</title>
    <link>https://inliniac.net/blog/category/debian/</link>
    <description>Recent content in Debian on Inliniac</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Jan 2015 00:34:50 +0000</lastBuildDate>
    <atom:link href="https://inliniac.net/blog/category/debian/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Suricata has been added to Debian Backports</title>
      <link>https://inliniac.net/blog/2015/01/08/suricata-has-been-added-to-debian-backports/</link>
      <pubDate>Thu, 08 Jan 2015 00:34:50 +0000</pubDate>
      <guid>https://inliniac.net/blog/2015/01/08/suricata-has-been-added-to-debian-backports/</guid>
      <description>&lt;p&gt;Thanks to the hard work of Arturo Borrero Gonzalez, Suricata has just been added to the &lt;img src=&#34;https://inliniac.net/blog/blog/wp-content/uploads/2015/01/openlogo-100.png&#34; alt=&#34;openlogo-100&#34;&gt;Debian &amp;lsquo;backports&amp;rsquo; repository. This allows users of Debian stable to run up to date versions of Suricata.&lt;/p&gt;&#xA;&lt;p&gt;The &amp;lsquo;Backports&amp;rsquo; repository makes the Suricata and libhtp packages from Debian Testing available to &amp;lsquo;stable&amp;rsquo; users. As &amp;rsquo;testing&amp;rsquo; is currently in a freeze, it may take a bit of time before 2.0.5 and libhtp 0.5.16 appear.&lt;/p&gt;&#xA;&lt;p&gt;Anyway, here is how to use it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Video: Suricata 2.0 installation and quick setup</title>
      <link>https://inliniac.net/blog/2014/03/30/video-suricata-2-0-installation-and-quick-setup/</link>
      <pubDate>Sat, 29 Mar 2014 22:01:56 +0000</pubDate>
      <guid>https://inliniac.net/blog/2014/03/30/video-suricata-2-0-installation-and-quick-setup/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve made a video on installing Suricata 2.0 on Debian Wheezy. The video does the installation, quick setup, ethtool config and shows a simple way to test the IDS.&lt;/p&gt;&#xA;&lt;div style=&#34;position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;&#34;&gt;&#xA;      &lt;iframe allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34; allowfullscreen=&#34;allowfullscreen&#34; loading=&#34;eager&#34; referrerpolicy=&#34;strict-origin-when-cross-origin&#34; src=&#34;https://www.youtube.com/embed/rodY7A14L2g?autoplay=0&amp;amp;controls=1&amp;amp;end=0&amp;amp;loop=0&amp;amp;mute=0&amp;amp;start=0&#34; style=&#34;position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;&#34; title=&#34;YouTube video&#34;&gt;&lt;/iframe&gt;&#xA;    &lt;/div&gt;&#xA;&#xA;&lt;p&gt;It&amp;rsquo;s the first time I&amp;rsquo;ve made such a video. Feedback is welcome.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Disabling Threading in Tcl8.5 in Debian</title>
      <link>https://inliniac.net/blog/2013/12/30/disabling-threading-in-tcl8-5-in-debian/</link>
      <pubDate>Mon, 30 Dec 2013 13:22:57 +0000</pubDate>
      <guid>https://inliniac.net/blog/2013/12/30/disabling-threading-in-tcl8-5-in-debian/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://inliniac.net/blog/blog/wp-content/uploads/2013/12/sguil_logo_h.gif?w=300&#34; alt=&#34;sguil_logo_h&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been spending the holidays to upgrade some of my own servers. One of them is the Sguil server I use. Until now it ran Debian Squeeze. On Debian Squeeze you could use tcl8.3, which has threading disabled. For Sguil tcl threading needs to be disabled:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-fallback&#34; data-lang=&#34;fallback&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;ERROR: This version of tcl was compile with threading enabled. Sguil is NOT compatible with threading.&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This is a compile time option in TCL, and the Debian Wheezy packages have it enabled by default. Here are the steps to create your own tcl deb with threading disabled:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Vuurmuur 0.8rc1 released</title>
      <link>https://inliniac.net/blog/2013/01/25/vuurmuur-0-8rc1-released/</link>
      <pubDate>Fri, 25 Jan 2013 16:45:34 +0000</pubDate>
      <guid>https://inliniac.net/blog/2013/01/25/vuurmuur-0-8rc1-released/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://inliniac.net/blog/blog/wp-content/uploads/2012/08/vuurmuur-connview-small.png&#34; alt=&#34;&#34;&gt;I just released a new &lt;a href=&#34;http://www.vuurmuur.org&#34;&gt;Vuurmuur&lt;/a&gt; version: 0.8rc1. The first release candidate for the 0.8 series. This release improves IPv6 support a lot. The wizard is now also fully functional. Try &amp;ldquo;vuurmuur_conf &amp;ndash;wizard&amp;rdquo;.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Improved IPv6 support: #115&lt;/li&gt;&#xA;&lt;li&gt;Improved Debian packages, switching to nflog as default for logging.&lt;/li&gt;&#xA;&lt;li&gt;Fix connection viewer not showing accounting on newer systems. #141&lt;/li&gt;&#xA;&lt;li&gt;Amd64 packages for Debian and Ubuntu are now available through the apt server. #83&lt;/li&gt;&#xA;&lt;li&gt;Switch from &amp;ldquo;state&amp;rdquo; match to &amp;ldquo;conntrack&amp;rdquo; match for connection tracking.&lt;/li&gt;&#xA;&lt;li&gt;Services now support possible protocols. #63&lt;/li&gt;&#xA;&lt;li&gt;Add support for rpfilter match. #137&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Get this release from the ftp server:&#xA;&lt;a href=&#34;ftp://ftp.vuurmuur.org/releases/0.8rc1/Vuurmuur-0.8rc1.tar.gz&#34;&gt;ftp://ftp.vuurmuur.org/releases/0.8rc1/Vuurmuur-0.8rc1.tar.gz&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>IPv6 Evasions, Scanners and the importance of staying current</title>
      <link>https://inliniac.net/blog/2012/12/11/ipv6-evasions-scanners-and-the-importance-of-staying-current/</link>
      <pubDate>Tue, 11 Dec 2012 16:13:49 +0000</pubDate>
      <guid>https://inliniac.net/blog/2012/12/11/ipv6-evasions-scanners-and-the-importance-of-staying-current/</guid>
      <description>&lt;p&gt;Lots of activity on the IPv6 front lately. There was a talk on a conference on bypassing IDS using IPv6 tricks. Also a new scan tool (Topera) claimed to scan a host while staying below the radar of an IDS was released. To start with the latter, even though Suricata doesn&amp;rsquo;t have a dedicated port scan detector, the tool&amp;rsquo;s traffic lights up like a Christmas tree. The trick it pulls is to pack a lot of duplicate DST OPTS extension headers in the IPv6 packets. These options are just fillers, the only options they use are the &amp;ldquo;pad&amp;rdquo; option. In Suricata we&amp;rsquo;ve had an event for duplicate DST OPTS headers since 1.3 and the padding only headers generate an event in 1.4. Both alerts will be very noisy, so calling this a stealth attack rather dubious.&lt;/p&gt;</description>
    </item>
    <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>Vuurmuur makes it into Debian (Sid)</title>
      <link>https://inliniac.net/blog/2008/12/09/vuurmuur-makes-it-into-debian-sid/</link>
      <pubDate>Tue, 09 Dec 2008 14:08:57 +0000</pubDate>
      <guid>https://inliniac.net/blog/2008/12/09/vuurmuur-makes-it-into-debian-sid/</guid>
      <description>&lt;p&gt;Thanks to the hard work of Debian&amp;rsquo;s Daniel Baumann Vuurmuur has been included in Debian unstable/Sid. This hopefully means that Vuurmuur will be getting a lot more users. Eventually it should get into testing and even stable, although the next release &amp;ldquo;lenny&amp;rdquo; will come too soon for that. The &amp;ldquo;lenny&amp;rdquo; feature freeze was already in place before Vuurmuur got included in Sid. Anyway, for me this is big news!&lt;/p&gt;&#xA;&lt;p&gt;See here for the packages:&#xA;&lt;a href=&#34;http://packages.debian.org/sid/libvuurmuur0&#34;&gt;http://packages.debian.org/sid/libvuurmuur0&lt;/a&gt; &lt;a href=&#34;http://packages.debian.org/sid/vuurmuur&#34;&gt;http://packages.debian.org/sid/vuurmuur&lt;/a&gt; &lt;a href=&#34;http://packages.debian.org/sid/vuurmuur-conf&#34;&gt;http://packages.debian.org/sid/vuurmuur-conf&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Compiling Snort_inline with NFQUEUE support on Ubuntu</title>
      <link>https://inliniac.net/blog/2007/06/26/compiling-snort_inline-with-nfqueue-support-on-ubuntu/</link>
      <pubDate>Tue, 26 Jun 2007 15:59:21 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/06/26/compiling-snort_inline-with-nfqueue-support-on-ubuntu/</guid>
      <description>&lt;p&gt;I needed to setup the right libraries for Snort_inline development on my fresh Ubuntu Feisty installation, so I decided to write down the procedure for those who think compiling Snort_inline from source is hard. :)&lt;/p&gt;&#xA;&lt;p&gt;Make sure you have build-essential package installed. This makes sure you have a compiler and development packages for glibc and other important libraries. I&amp;rsquo;m installing the libraries from source to get the latest versions because the latest versions are more stable and perform better than the versions included in Feisty. I&amp;rsquo;m installing them into /usr because some programs like them there best.&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>Sguil 0.7 CVS installation on Debian Etch</title>
      <link>https://inliniac.net/blog/2007/06/12/sguil-07-cvs-installation-on-debian-etch/</link>
      <pubDate>Tue, 12 Jun 2007 21:58:51 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/06/12/sguil-07-cvs-installation-on-debian-etch/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://sguil.sourceforge.net/&#34;&gt;Sguil&lt;/a&gt; 0.7 is getting shape quite nicely. One of the most interesting new features is the splitting up of different types of agents and the option to create &amp;rsquo;net groups&amp;rsquo;. This are groups of agents that Sguil considers part of the same network. You can use this to spread the agents over multiple servers, but still use it from Sguil as if it was one single sensor. For example, this way you can easily create a Snort sensor and a separate full content logging capture server. When you request the full content for a Snort event in Sguil, it will know that it needs to request the packet data from the capture server. This way you can also have multiple Snort agents without the need for capturing the same sancp and full content data over and over again.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
