<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Security on To Linux and beyond !</title>
    <link>https://home.regit.org/tags/security/</link>
    <description>Recent content in Security on To Linux and beyond !</description>
    <generator>Hugo</generator>
    <language>fr</language>
    <lastBuildDate>Thu, 26 Jun 2014 08:41:02 +0000</lastBuildDate>
    <atom:link href="https://home.regit.org/feed/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>pshitt: collect passwords used in SSH bruteforce</title>
      <link>https://home.regit.org/2014/06/pshitt-collect-passwords-used-in-ssh-bruteforce/</link>
      <pubDate>Thu, 26 Jun 2014 08:41:02 +0000</pubDate>
      <guid>https://home.regit.org/2014/06/pshitt-collect-passwords-used-in-ssh-bruteforce/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;I’ve been playing lately on &lt;a href=&#34;https://home.regit.org/2014/02/chinese-scanner/&#34;&gt;analysis SSH bruteforce caracterization&lt;/a&gt;. I was a bit frustrated of just getting partial information:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;ulogd can give information about scanner settings&lt;/li&gt;
&lt;li&gt;suricata can give me information about software version&lt;/li&gt;
&lt;li&gt;sshd server logs shows username&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;But having username without having the password is really frustrating.&lt;/p&gt;&lt;/p&gt;
&lt;p&gt;So I decided to try to get them. Looking for a SSH server honeypot, I did find &lt;a href=&#34;https://github.com/desaster/kippo&#34;&gt;kippo&lt;/a&gt; but it was going too far for me&lt;br&gt;
by providing a fake shell access. So I’ve decided to build my own based on &lt;a href=&#34;https://github.com/paramiko/paramiko&#34;&gt;paramiko&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Logging connection tracking event with ulogd</title>
      <link>https://home.regit.org/2014/02/logging-connection-tracking-event-with-ulogd/</link>
      <pubDate>Sun, 23 Feb 2014 17:11:30 +0000</pubDate>
      <guid>https://home.regit.org/2014/02/logging-connection-tracking-event-with-ulogd/</guid>
      <description>&lt;h4 id=&#34;motivation&#34;&gt;Motivation&lt;/h4&gt;
&lt;p&gt;I’ve recently met &lt;a href=&#34;https://twitter.com/aurelsec&#34;&gt;@aurelsec&lt;/a&gt; and we’ve discussed about the interest of logging connection tracking entries. This is indeed a undervalued information source in a network.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;http://en.wikipedia.org/wiki/Netfilter#Connection_tracking&#34;&gt;Quoting Wikipedia&lt;/a&gt;: “Connection tracking allows the kernel to keep track of all logical network connections or sessions, and thereby relate all of the packets which may make up that connection. NAT relies on this information to translate all related packets in the same way, and iptables can use this information to act as a stateful firewall.”&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using ulogd and JSON output</title>
      <link>https://home.regit.org/2014/02/using-ulogd-and-json-output/</link>
      <pubDate>Sun, 02 Feb 2014 16:39:34 +0000</pubDate>
      <guid>https://home.regit.org/2014/02/using-ulogd-and-json-output/</guid>
      <description>&lt;h4 id=&#34;ulogd-and-json-output&#34;&gt;Ulogd and JSON output&lt;/h4&gt;
&lt;p&gt;In February 2014, I’ve &lt;a href=&#34;http://git.netfilter.org/ulogd2/commit/?id=e0ae1870e5b15138c12071d9d96522a2720bf44a&#34;&gt;commited a new output plugin&lt;/a&gt; to &lt;a href=&#34;http://www.netfilter.org/projects/ulogd/index.html&#34;&gt;ulogd&lt;/a&gt;, the userspace logging daemon for Netfilter. This is a &lt;a href=&#34;http://en.wikipedia.org/wiki/JSON&#34;&gt;JSON&lt;/a&gt; output plugin which output logs into a file in JSON format. The interest of the JSON format is that it is easily parsed by software just as logstash. And once data are understood by &lt;a href=&#34;http://logstash.net/&#34;&gt;logstash&lt;/a&gt;, you can get some nice and useful dashboard in &lt;a href=&#34;http://www.elasticsearch.org/overview/kibana/&#34;&gt;Kibana&lt;/a&gt;:&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234.png&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-1024x486.png&#34; alt=&#34;Screenshot from 2014-02-02 13:22:34&#34; width=&#34;695&#34; height=&#34;329&#34; class=&#34;aligncenter size-large wp-image-1896&#34; srcset=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-1024x486.png 1024w, https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-300x142.png 300w, https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234.png 1898w&#34; sizes=&#34;auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Investigation on an attack tool used in China</title>
      <link>https://home.regit.org/2014/02/chinese-scanner/</link>
      <pubDate>Sun, 02 Feb 2014 15:28:32 +0000</pubDate>
      <guid>https://home.regit.org/2014/02/chinese-scanner/</guid>
      <description>&lt;h4 id=&#34;log-analysis-experiment&#34;&gt;Log analysis experiment&lt;/h4&gt;
&lt;p&gt;I’ve been playing lately with &lt;a href=&#34;http://logstash.net/&#34;&gt;logstash&lt;/a&gt; using data from the &lt;a href=&#34;http://git.netfilter.org/ulogd2/commit/?id=e0ae1870e5b15138c12071d9d96522a2720bf44a&#34;&gt;ulogd JSON output plugin&lt;/a&gt; and the &lt;a href=&#34;http://pevma.blogspot.fr/2014/02/suricata-idps-and-common-information.html&#34;&gt;Suricata full JSON output&lt;/a&gt; as well as standard system logs.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234.png&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-1024x486.png&#34; alt=&#34;Screenshot from 2014-02-02 13:22:34&#34; width=&#34;695&#34; height=&#34;329&#34; class=&#34;aligncenter size-large wp-image-1896&#34; srcset=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-1024x486.png 1024w, https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-300x142.png 300w, https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234.png 1898w&#34; sizes=&#34;auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Ulogd is getting Netfilter firewall logs from Linux kernel and is writing them in JSON format. Suricata is doing the same with alert and other traces. Logstash is getting both log as well as sytem log. This allows to create some dashboard with information coming from multiple sources. If you want to know how to configure ulogd for JSON output check &lt;a href=&#34;https://home.regit.org/2014/02/using-ulogd-and-json-output/&#34;&gt;this post&lt;/a&gt;. For suricata, you can have a look at &lt;a href=&#34;https://home.regit.org/2014/01/a-bit-of-logstash-cooking/&#34;&gt;this one&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Logstash and Suricata for the old guys</title>
      <link>https://home.regit.org/2013/10/logstash-and-suricata-for-the-old-guys/</link>
      <pubDate>Mon, 28 Oct 2013 10:47:31 +0000</pubDate>
      <guid>https://home.regit.org/2013/10/logstash-and-suricata-for-the-old-guys/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;http://logstash.net/&#34;&gt;logstash&lt;/a&gt; an opensource tool for managing events and logs. It is using &lt;a href=&#34;http://www.elasticsearch.org/&#34;&gt;elasticsearch&lt;/a&gt; for the storage and has a really nice interface named &lt;a href=&#34;http://www.elasticsearch.org/overview/kibana/&#34;&gt;Kibana&lt;/a&gt;. One of the easiest to use entry format is JSON.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;http://www.suricata-ids.org&#34;&gt;Suricata&lt;/a&gt; is an IDS/IPS which has some interesting logging features. Version 2.0 will feature a JSON export for all logging subsystem. It will then be possible to output in JSON format:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;HTTP log&lt;/li&gt;
&lt;li&gt;DNS log&lt;/li&gt;
&lt;li&gt;TLS log&lt;/li&gt;
&lt;li&gt;File log&lt;/li&gt;
&lt;li&gt;IDS Alerts&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For now, only File log is available in JSON format. This extract meta data from files transferred over HTTP.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Netfilter and the NAT of ICMP error messages</title>
      <link>https://home.regit.org/2013/04/netfilter-and-icmp-error-messages/</link>
      <pubDate>Wed, 24 Apr 2013 22:30:00 +0000</pubDate>
      <guid>https://home.regit.org/2013/04/netfilter-and-icmp-error-messages/</guid>
      <description>&lt;h4 id=&#34;the-problem&#34;&gt;The problem&lt;/h4&gt;
&lt;p&gt;I’ve been recently working for a customer which needed consultancy because of some unexplained &lt;a href=&#34;http://www.netfilter.org&#34;&gt;Netfilter&lt;/a&gt; behaviors related to ICMP error messages. He authorizes me to share the result of my study and I thank him for making this blog entry possible.&lt;br&gt;
His problem was that one of his firewalls is using a private interconnexion with their border router and the customer did not manage to NAT all outgoing ICMP error messages.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Martin Topholm: DDoS experiences with Linux and Netfilter</title>
      <link>https://home.regit.org/2013/03/martin-topholm-ddos-experiences-with-linux-and-netfilter/</link>
      <pubDate>Mon, 11 Mar 2013 10:54:17 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/martin-topholm-ddos-experiences-with-linux-and-netfilter/</guid>
      <description>&lt;p&gt;Martin is working for one.com a local ISP and is facing some DDoS. SYN cookie was implemented but the performance were too low with performance below 300kpps which is not what was expected. In fact SYN is on a slow path with a single spin lock protecting the SYN backtrack queue. So the system behave like a single core system relatively to SYN attacks.&lt;/p&gt;
&lt;p&gt;Jesper Dangaard Brouer has proposed a patch to move the syn cookie out of the lock but it has some downside and could not be accepted. In particular, the syncookie system needs to check every type of packet to see if they belong to a previous syn cookie response and thus a central point is needed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Eric Leblond: ulogd2, Netfilter logging reloaded</title>
      <link>https://home.regit.org/2013/03/eric-leblond-ulogd2-netfilter-logging-reloaded/</link>
      <pubDate>Mon, 11 Mar 2013 07:30:30 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/eric-leblond-ulogd2-netfilter-logging-reloaded/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;I’ve made yesterday a presentation of ulogd2 at &lt;a href=&#34;http://opensourcedays.org/2013/&#34;&gt;Open Source Days&lt;/a&gt; in Copenhagen. After a brief history of Netfilter logging, I’ve described the key features of ulogd2 and demonstrate two interfaces, &lt;a href=&#34;https://home.regit.org/software/nf3d/&#34;&gt;nf3d&lt;/a&gt; and &lt;a href=&#34;https://www.wzdftpd.net/redmine/projects/djedi/wiki&#34;&gt;djedi&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The slides are available:&lt;br&gt;
&lt;a href=&#34;https://home.regit.org/uploads/2013/03/ulogd2.pdf&#34;&gt;Ulogd2, Netfilter logging reloaded&lt;/a&gt;.&lt;/p&gt;
&lt;h4 id=&#34;screencasts&#34;&gt;Screencasts&lt;/h4&gt;
&lt;p&gt;This video demonstrates some features of nf3d:&lt;/p&gt;
&lt;p&gt;This screencast is showing some of the capabilities of djedi:&lt;/p&gt;
&lt;p&gt;Thanks a lot to the organizers for this cool event.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tomasz Bursztyka, ConnMan usage of Netfilter: a close overview</title>
      <link>https://home.regit.org/2013/03/tomasz-bursztyka-connman-usage-of-netfilter-a-close-overview/</link>
      <pubDate>Sun, 10 Mar 2013 15:36:08 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/tomasz-bursztyka-connman-usage-of-netfilter-a-close-overview/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;http://connman.net/&#34;&gt;ConnMan&lt;/a&gt; is a connection manager which integrate all critical networking components. It provides a smart D-Bus API to develop an User Interface. It is plugin oriented and all different network stacks are implemented in different modules.&lt;br&gt;
Connection sharing (aka tethering) is using Netfilter to setup NAT masquerading. So it is a simple usage.&lt;/p&gt;
&lt;h4 id=&#34;switching-to-nftables&#34;&gt;Switching to nftables&lt;/h4&gt;
&lt;p&gt;Application connectivity is a more advanced part involving Netfilter as it makes a use of statistics and differenciated routing. For example, in a car, service data must be sent to manufacturer operator and not on the owner network.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Julien Vehent, AFW: Automating host-based firewalls with Chef</title>
      <link>https://home.regit.org/2013/03/julien-vehent-afw-automating-host-based-firewalls-with-chef/</link>
      <pubDate>Sun, 10 Mar 2013 15:12:52 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/julien-vehent-afw-automating-host-based-firewalls-with-chef/</guid>
      <description>&lt;h4 id=&#34;the-problem&#34;&gt;The problem&lt;/h4&gt;
&lt;p&gt;Centralized firewall design does not scale well when dealing with a lot of servers. It begins to collapse after a few thousands rules.&lt;br&gt;
Furthermore, to be able to have an application A to connect to server B, it would take a workflow and possibly 3 weeks to get the opening.&lt;/p&gt;
&lt;h4 id=&#34;from-service-oriented-architecture-to-service-oriented-security&#34;&gt;From Service Oriented Architecture to Service Oriented Security&lt;/h4&gt;
&lt;p&gt;Service are autonomous. They call each other using a standard protocol. The architecture is described by a list of dependencies between services.&lt;br&gt;
You can then specify security via things like &lt;em&gt;ACCEPT Caching TO Frontend ON PORT 80&lt;/em&gt;.&lt;br&gt;
But this force you to do provisioning each time a server start.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Jozsef Kadlecsik, Faster firewalling with ipset</title>
      <link>https://home.regit.org/2013/03/jozsef-kadlecsik-faster-firewalling-with-ipset/</link>
      <pubDate>Sun, 10 Mar 2013 13:51:19 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/jozsef-kadlecsik-faster-firewalling-with-ipset/</guid>
      <description>&lt;h4 id=&#34;why-ipset-&#34;&gt;Why ipset ?&lt;/h4&gt;
&lt;p&gt;iptables is enough sufficient but in some cases limit are found:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;High number of rules: iptables is linear&lt;/li&gt;
&lt;li&gt;Need to change the rules often&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Independant study available at &lt;a href=&#34;http://daemonkeeper.net/781/mass-blocking-ip-addresses-with-ipset/&#34;&gt;d(a)emonkeeper’s purgatory&lt;/a&gt; has shown that the performance of ipset are almost constant with respect to the number of filtered hosts:&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;http://daemonkeeper.net/781/mass-blocking-ip-addresses-with-ipset/&#34;&gt;&lt;img decoding=&#34;async&#34; src=&#34;http://daemonkeeper.net/uploads/2012/05/ipset3.png&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4 id=&#34;history&#34;&gt;History&lt;/h4&gt;
&lt;p&gt;The originating project was ippool featuring a a basic set and after some time it has been taken over by Jozsef and renamed &lt;a href=&#34;http://ipset.netfilter.org/&#34;&gt;ipset&lt;/a&gt;. A lot of type of sets are now handled.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Patrick McHardy: Oops, I did it: IPv6 NAT</title>
      <link>https://home.regit.org/2013/03/patrick-mchardy-oops-i-did-it-ipv6-nat/</link>
      <pubDate>Sun, 10 Mar 2013 13:01:41 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/patrick-mchardy-oops-i-did-it-ipv6-nat/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;Harald Welte when asked about IPv6 NAT was answering: “it will be over my dead body”. It is now available in official kernel.&lt;/p&gt;
&lt;h4 id=&#34;reasons-for-adding-ipv6-nat&#34;&gt;Reasons for adding IPv6 NAT&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Dynamic IPv6 Prefixes : ISP assigning dynamic IPv6 prefixes so Internal network address change. NAT can bring you stability.&lt;/li&gt;
&lt;li&gt;Easier test setup.&lt;/li&gt;
&lt;li&gt;Users are asking and most operating systems have it.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To resume the arguments of NAT, Patrick McHardy used this video:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Pablo Neira Ayuso: nftables, a new packet filtering framework for Netfilter</title>
      <link>https://home.regit.org/2013/03/pablo-neira-ayuso-nftables-a-new-packet-filtering-framework-for-netfilter/</link>
      <pubDate>Sun, 10 Mar 2013 12:37:15 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/pablo-neira-ayuso-nftables-a-new-packet-filtering-framework-for-netfilter/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;nftable is a kernel packet filtering framework to replaces iptables. It brings no changes in the core (conntrack, hooks).&lt;/p&gt;
&lt;p&gt;Match logic is changed: you fetch keys and once you have your key set, you make operation on them. Advanced and specialized matchs are built upon this system.&lt;/p&gt;
&lt;h4 id=&#34;nftables-vs-iptables&#34;&gt;nftables vs iptables&lt;/h4&gt;
&lt;p&gt;In iptables, extension were coded in separate files and they must be put in iptables source tree. To act, they must modify on a binary array storing the ruleset and injecting it back to the kernel. So every update involve a full download and upload of the whole ruleset.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ulogd 2.0.2, my first release as maintainer</title>
      <link>https://home.regit.org/2013/03/ulogd-2-0-2-my-first-release-as-maintainer/</link>
      <pubDate>Mon, 04 Mar 2013 00:13:13 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/ulogd-2-0-2-my-first-release-as-maintainer/</guid>
      <description>&lt;h4 id=&#34;objectives-of-this-release&#34;&gt;Objectives of this release&lt;/h4&gt;
&lt;p&gt;So it is my first ulogd2 release as maintainer. I’ve been in charge of the project since 2012 October 30th and this was an opportunity for me to increase my developments on the project. Roadmap was almost empty so I’ve decided to work on issues that were bothering me as a user of the project. I’ve also included two features which are connection tracking event filtering and a Graphite output module. Ulogd is available on &lt;a href=&#34;http://netfilter.org/projects/ulogd/downloads.html&#34;&gt;Netfilter web site&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Some statistics about Suricata 1.4</title>
      <link>https://home.regit.org/2012/12/some-statistics-about-suricata-1-4/</link>
      <pubDate>Thu, 13 Dec 2012 16:11:00 +0000</pubDate>
      <guid>https://home.regit.org/2012/12/some-statistics-about-suricata-1-4/</guid>
      <description>&lt;h4 id=&#34;a-huge-work&#34;&gt;A huge work&lt;/h4&gt;
&lt;p&gt;&lt;a href=&#34;http://suricata-ids.org/2012/12/13/suricata-1-4-released/&#34;&gt;Suricata 1.4&lt;/a&gt; has been released December 13th 2012 and it has been a huge work. The number of modifications is just impressing:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;390 files changed, 25299 insertions(+), 11982 deletions(-)&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The following video is using &lt;a href=&#34;http://code.google.com/p/gource/&#34;&gt;gource&lt;/a&gt; to display the evolution of Suricata IDS/IPS source code between version 1.3 and version 1.4. It only displays the modified files and do not show the files existing at start.&lt;/p&gt;
&lt;h5 id=&#34;a-collaborative-work&#34;&gt;A collaborative work&lt;/h5&gt;
&lt;p&gt;A total of 11 different authors have participated to this release. The following graph generated by &lt;a href=&#34;http://gitstats.sourceforge.net/&#34;&gt;gitstats&lt;/a&gt; shows the number of lines of code by author:&lt;/p&gt;</description>
    </item>
    <item>
      <title>The defense blues</title>
      <link>https://home.regit.org/2012/12/the-defene-blues/</link>
      <pubDate>Thu, 06 Dec 2012 13:02:39 +0000</pubDate>
      <guid>https://home.regit.org/2012/12/the-defene-blues/</guid>
      <description>&lt;p&gt;Mother Nature has been really unfair with me. It has given me two strong interests in life: building things and information security. Once that was done, my doom was sealed and I’ve become a infosec defense guy. Nowadays this is one of the worst fate possible in computer science.&lt;/p&gt;
&lt;p&gt;Today, this burden is really hard to wear. I know some of you will try to encourage me by saying this like:&lt;/p&gt;</description>
    </item>
    <item>
      <title>A new unix command mode in Suricata</title>
      <link>https://home.regit.org/2012/09/a-new-unix-command-mode-in-suricata/</link>
      <pubDate>Tue, 18 Sep 2012 22:21:05 +0000</pubDate>
      <guid>https://home.regit.org/2012/09/a-new-unix-command-mode-in-suricata/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;I’ve been working for the past few days on a new Suricata feature. It is available in &lt;a href=&#34;http://suricata-ids.org/2012/11/29/suricata-1-4rc1-available/&#34;&gt;Suricata 1.4rc1&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Suricata can now listen to a unix socket and accept commands from the user. The exchange protocol is JSON-based and the format of the message has been done to be generic and it is described in this &lt;a href=&#34;https://github.com/regit/suricata/commit/1a58eec318a842834a9252fbf4961a392cbad8a8&#34;&gt;commit message&lt;/a&gt;. An example script called &lt;em&gt;suricatasc&lt;/em&gt; is provided in the source and installed automatically when updating Suricata.&lt;/p&gt;</description>
    </item>
    <item>
      <title>New AF_PACKET IPS mode in Suricata</title>
      <link>https://home.regit.org/2012/09/new-af_packet-ips-mode-in-suricata/</link>
      <pubDate>Tue, 04 Sep 2012 20:53:53 +0000</pubDate>
      <guid>https://home.regit.org/2012/09/new-af_packet-ips-mode-in-suricata/</guid>
      <description>&lt;h4 id=&#34;a-new-suricata-ips-mode&#34;&gt;A new Suricata IPS mode&lt;/h4&gt;
&lt;p&gt;Suricata IPS capabilities are not new. It is possible to use Suricata with Netfilter or ipfw to build a state-of-the-art IPS. On Linux, this system has not the best throughput performance. Patrick McHardy’s work on &lt;a href=&#34;https://lwn.net/Articles/512442/&#34;&gt;netlink: memory mapped I/O&lt;/a&gt; should bring some real improvement but this is not yet available.&lt;/p&gt;
&lt;p&gt;I’ve thus decided to do an implementation of IPS based on AF_PACKET (read raw socket). The idea is based on one of the snort’s running mode. It peers two network interfaces and all packets received from one interface are sent to the other interface (if a signature with drop keyword does not fired on the packet). This requires to dedicate two network interfaces for Suricata but this provide a simple bridge system. As suricata is using latest AF_PACKET features (read load balancing), it was possible to build something really promising.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suricata new TLS fingerprint and TLS store keywords.</title>
      <link>https://home.regit.org/2012/08/tls-fingerprint-store/</link>
      <pubDate>Mon, 27 Aug 2012 17:10:49 +0000</pubDate>
      <guid>https://home.regit.org/2012/08/tls-fingerprint-store/</guid>
      <description>&lt;h4 id=&#34;suricata-tls-support&#34;&gt;Suricata TLS support&lt;/h4&gt;
&lt;p&gt;Victor Julien has just &lt;a href=&#34;https://github.com/inliniac/suricata/pull/34&#34;&gt;merged to main tree&lt;/a&gt; a branch containing some interesting new TLS related features. They have been contributed by me and Jean-Paul Roliers.&lt;/p&gt;
&lt;p&gt;This patchset introduces TLS logging and brings some new keywords to Suricata engine.&lt;br&gt;
Here’s the list of all TLS related keywords that are available in latest Suricata git:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;tls.version: match on version of protocol&lt;/li&gt;
&lt;li&gt;tls.subject: match on subject of certificate&lt;/li&gt;
&lt;li&gt;tls.issuerdn: match on issuer DN of certificate&lt;/li&gt;
&lt;li&gt;tls.fingerprint: match on SHA1 fingerprint of certificate&lt;/li&gt;
&lt;li&gt;tls.store: store the certificate on disk&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You will find detailed explanation below.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Flow accounting with Netfilter and ulogd2</title>
      <link>https://home.regit.org/2012/07/flow-accounting-with-netfilter-and-ulogd2/</link>
      <pubDate>Sat, 14 Jul 2012 21:11:44 +0000</pubDate>
      <guid>https://home.regit.org/2012/07/flow-accounting-with-netfilter-and-ulogd2/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Starting with Linux kernel 3.3, there’s a new module called &lt;em&gt;nfnetlink_acct&lt;/em&gt;.&lt;br&gt;
This new feature added by Pablo Neira brings interesting accountig capabilities to Netfilter.&lt;br&gt;
Pablo has made an extensive &lt;a href=&#34;http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=9413902796f56f6209e19dd54e840ed46950612c&#34;&gt;description of the feature in the commit&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&#34;system-setup&#34;&gt;System setup&lt;/h2&gt;
&lt;p&gt;We need to build a set of tools to get all that’s necessary:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;libmnl&lt;/li&gt;
&lt;li&gt;libnetfilter_acct&lt;/li&gt;
&lt;li&gt;nfacct&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The build is the same for all projects:&lt;/p&gt;
&lt;pre&gt;git clone git://git.netfilter.org/PROJECT
cd PROJECT
autoreconf -i
./configure
make
sudo make install
&lt;/pre&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Opensvp, a new tool to analyse the security of firewalls using ALGs</title>
      <link>https://home.regit.org/2012/06/opensvp-a-new-tool-to-analyse-the-security-of-firewalls-using-algs/</link>
      <pubDate>Fri, 08 Jun 2012 13:34:07 +0000</pubDate>
      <guid>https://home.regit.org/2012/06/opensvp-a-new-tool-to-analyse-the-security-of-firewalls-using-algs/</guid>
      <description>&lt;p&gt;Following my talk at &lt;a href=&#34;http://www.sstic.org&#34;&gt;SSTIC&lt;/a&gt;, I’ve released a new tool called &lt;a href=&#34;https://home.regit.org/software/opensvp/&#34;&gt;opensvp&lt;/a&gt;. Its aim is to cover the attacks described in this talk. It has been published to be able to determine if the firewall policy related to &lt;a href=&#34;http://en.wikipedia.org/wiki/Application-level_gateway&#34;&gt;Application Layer Gateways&lt;/a&gt; is correctly implemented.&lt;/p&gt;
&lt;p&gt;Opensvp implements two type of attacks:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Abusive usage of protocol commands: an protocol message can be forged to open pinhole into firewall. Opensvp currently implements message sending for IRC and FTP ALGs.&lt;/li&gt;
&lt;li&gt;Spoofing attack: if anti-spooofing is not correctly setup, an attacker can send command which result in arbitrary pinhole being opened to a server.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It has been developed in &lt;a href=&#34;http://www.python.org/&#34;&gt;Python&lt;/a&gt; and uses &lt;a href=&#34;http://www.secdev.org/projects/scapy/&#34;&gt;scapy&lt;/a&gt; to implement the spoofing attack on ALGs.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Transparents de ma prÃ©sentation au SSTIC</title>
      <link>https://home.regit.org/2012/06/transparents-de-ma-presentation-au-sstic/</link>
      <pubDate>Fri, 08 Jun 2012 10:26:13 +0000</pubDate>
      <guid>https://home.regit.org/2012/06/transparents-de-ma-presentation-au-sstic/</guid>
      <description>&lt;p&gt;Les transparents de ma prÃ©sentation du SSTIC sont disponibles : &lt;a href=&#34;https://home.regit.org/uploads/2012/06/conntrack-attack.pdf&#34;&gt;Utilisation malveillante des suivis de connexions&lt;/a&gt;. Merci aux organisateurs du SSTIC d’avoir acceptÃ© mon papier!&lt;/p&gt;
&lt;p&gt;Des vidÃ©os de dÃ©monstration sont disponibles sur ce post: &lt;a href=&#34;https://home.regit.org/2012/03/playing-with-network-layers-to-bypass-firewalls-filtering-policy/&#34;&gt;Playing with Network Layers to Bypass Firewalls’ Filtering Policy&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;L’outil de test &lt;a href=&#34;https://home.regit.org/software/opensvp/&#34;&gt;openvsp&lt;/a&gt; est disponible sur &lt;a href=&#34;https://home.regit.org/software/opensvp/&#34;&gt;cette page&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Playing with Network Layers to Bypass Firewalls’ Filtering Policy</title>
      <link>https://home.regit.org/2012/03/playing-with-network-layers-to-bypass-firewalls-filtering-policy/</link>
      <pubDate>Fri, 09 Mar 2012 22:02:38 +0000</pubDate>
      <guid>https://home.regit.org/2012/03/playing-with-network-layers-to-bypass-firewalls-filtering-policy/</guid>
      <description>&lt;p&gt;The slides of my CansecWest talk can now be downloaded: &lt;a href=&#34;http://home.regit.org/uploads/2012/03/conntrack-attack.pdf&#34;&gt;Playing with Network Layers to Bypass Firewalls’ Filtering Policy&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The required counter-measures are described in the &lt;a href=&#34;http://home.regit.org/netfilter-en/secure-use-of-helpers/&#34;&gt;Secure use of iptables and connection tracking helpers&lt;/a&gt; document&lt;/p&gt;
&lt;p&gt;The associated video demonstrations are available:&lt;/p&gt;
&lt;div&gt;
  &lt;p&gt;
    First video demonstrates how to use forged IRC protocol command (DCC request) to be able to open connection to a NATed client from internet.
  &lt;/p&gt;
  &lt;p&gt;
    &lt;/div&gt; 
&lt;pre&gt;&lt;code&gt;&amp;lt;div&amp;gt;
  &amp;lt;p&amp;gt;
    Second video demonstrates the effect of the attack on helpers on a non protected Netfilter Firewall.
  &amp;lt;/p&amp;gt;
  
  &amp;lt;p&amp;gt;
    &amp;lt;/div&amp;gt; 
    
    &amp;lt;div&amp;gt;
      &amp;lt;p&amp;gt;
        Third video demonstrates the effect of the attack on helpers on a badly configured Checkpoint firewall.
      &amp;lt;/p&amp;gt;
      
      &amp;lt;p&amp;gt;
        &amp;lt;/div&amp;gt; 
        
        &amp;lt;p&amp;gt;
          More information will come in upcoming posts.
        &amp;lt;/p&amp;gt;
&lt;/code&gt;&lt;/pre&gt;</description>
    </item>
    <item>
      <title>Using AF_PACKET zero copy mode in Suricata</title>
      <link>https://home.regit.org/2012/02/using-af_packet-zero-copy-mode-in-suricata/</link>
      <pubDate>Thu, 23 Feb 2012 18:25:15 +0000</pubDate>
      <guid>https://home.regit.org/2012/02/using-af_packet-zero-copy-mode-in-suricata/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://www.inliniac.net/blog/&#34;&gt;Victor Julien&lt;/a&gt; has &lt;a href=&#34;http://lists.openinfosecfoundation.org/pipermail/oisf-devel/2012-February/001283.html&#34;&gt;just pushed&lt;/a&gt; a new feature to &lt;a href=&#34;https://redmine.openinfosecfoundation.org/projects/suricata/repository&#34;&gt;suricata’s git tree&lt;/a&gt;. It brings improvements to the AF_PACKET capture mode.&lt;/p&gt;
&lt;p&gt;This capture mode can be used on Linux. It is the native way to capture packet. Suricata is able to use the interesting new multithreading feature provided by AF_PACKET on recent kernels: it is possible to have multiple capture threads receiving the packet of a single interface.&lt;/p&gt;
&lt;p&gt;The commits add mmaped ring buffer support to AF_PACKET capture and also provide a zero copy mode. Mmaped ring buffer is mechanism similar to the one used by PF_RING. The kernel allocates some memory to store the packets and share this memory with the capture process. Instead of sending messages, the kernel just write to the shared memory and the process capture reads it. This is less consuming in term of CPU ressource and helps to increase the capture rate. But the main avantage of this technique is that the capture process can treat the packets without making a copy and this saves a lot of time&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ecosystem of Suricata</title>
      <link>https://home.regit.org/2012/02/ecosystem-of-suricata/</link>
      <pubDate>Mon, 13 Feb 2012 16:46:32 +0000</pubDate>
      <guid>https://home.regit.org/2012/02/ecosystem-of-suricata/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://www.openinfosecfoundation.org/index.php/downloads&#34;&gt;Suricata&lt;/a&gt; is an IDS/IPS engine. To build a complete solution, you will need to use other tools.&lt;/p&gt;
&lt;p&gt;The following schema is a representation of a possible software setup in the case Suricata is used as IDS or IPS on the network. It only uses opensource components:&lt;br&gt;
&lt;a href=&#34;https://home.regit.org/uploads/2012/02/suricata-ecosystem1.png&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2012/02/suricata-ecosystem1.png&#34; alt=&#34;&#34; title=&#34;Suricata&amp;#039;s ecosystem&#34; width=&#34;450&#34; height=&#34;484&#34; class=&#34;aligncenter size-full wp-image-914&#34; srcset=&#34;https://home.regit.org/uploads/2012/02/suricata-ecosystem1.png 450w, https://home.regit.org/uploads/2012/02/suricata-ecosystem1-278x300.png 278w&#34; sizes=&#34;auto, (max-width: 450px) 85vw, 450px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Suricata is used to sniff and analyse the traffic. To detect malicious traffic, it uses signatures (or rules). You can download a set of specialised rules from &lt;a href=&#34;http://www.emergingthreats.net/&#34;&gt;EmergingThreats&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ã€ propos de la publication de code d’EdenWall</title>
      <link>https://home.regit.org/2011/12/code-edenwall/</link>
      <pubDate>Thu, 01 Dec 2011 15:30:28 +0000</pubDate>
      <guid>https://home.regit.org/2011/12/code-edenwall/</guid>
      <description>&lt;p&gt;J’ai cofondÃ© la sociÃ©tÃ© INL en 2004. RenommÃ©e en 2009 EdenWall, suite Ã  une levÃ©e de fonds et un changement de mÃ©tier,&lt;br&gt;
le nouveau business model de la sociÃ©tÃ© fut la commercialisation d’appliances de sÃ©curitÃ© basÃ©es sur le logiciel libre NuFW&lt;br&gt;
que j’avais initiÃ© en 2003. NuFW, couche logicielle ajoutant l’authentification des flux Ã  Netfilter, est restÃ© le&lt;br&gt;
moteur technologique de la sociÃ©tÃ© mais n’Ã©tait pas d’un accÃ¨s facile car nÃ©cessitant des compÃ©tences bas niveaux pour&lt;br&gt;
son dÃ©ploiement. Nous avons donc distribuÃ© sous licence libre des briques complÃ©mentaires Ã  partir de 2005. Nulog,&lt;br&gt;
projet d’analyse de journaux, que j’avais commencÃ© en 2001 et Nuface, interface de configuration de politiques de&lt;br&gt;
filtrage en 2005. La conclusion de cette dÃ©marche d’ouverture a Ã©tÃ© NuFirewall, une solution autonome de pare-feu&lt;br&gt;
basÃ©e sur les briques EdenWall qui a Ã©tÃ© distribuÃ©e en 2010. Il s’agissait d’une version&lt;br&gt;
libre des appliances EdenWall distribuÃ©e sous forme d’une distribution indÃ©pendante publiÃ©e sous licence GPL.&lt;br&gt;
L’idÃ©e des fondateurs Ã©tait d’avoir une structure de produits similaires Ã  une offre comme celle de VirtualBox avec&lt;br&gt;
une distribution sous double licence : une solution libre convenant au plus grand nombre et une version avec des&lt;br&gt;
fonctionnalitÃ©s Entreprise.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Securing Netfilter connection tracking helpers</title>
      <link>https://home.regit.org/2011/11/securing-netfilter-helpers/</link>
      <pubDate>Wed, 30 Nov 2011 09:57:02 +0000</pubDate>
      <guid>https://home.regit.org/2011/11/securing-netfilter-helpers/</guid>
      <description>&lt;p&gt;Following the &lt;a href=&#34;http://home.regit.org/2011/08/eric-leblond-in-need-of-reverse-path-filtering/&#34;&gt;presentation&lt;/a&gt; I’ve made during the &lt;a href=&#34;http://workshop.netfilter.org/2011/&#34;&gt;8th Netfilter Workshop&lt;/a&gt;, it was decided to write a document containing the best practices for a secure use of iptables and connection tracking helpers.&lt;/p&gt;
&lt;p&gt;This document called &lt;a href=&#34;http://home.regit.org/netfilter-en/secure-use-of-helpers/&#34;&gt;“Secure use of iptables and connection tracking helpers”&lt;/a&gt; is now available on this site. It contains recommendations that should be followed carefully if you are the administrator of a Netfilter/Iptables or the developer of a Netfilter based software.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Acquisition systems and running modes evolution of Suricata</title>
      <link>https://home.regit.org/2011/10/suricata-new-feature/</link>
      <pubDate>Thu, 06 Oct 2011 23:06:24 +0000</pubDate>
      <guid>https://home.regit.org/2011/10/suricata-new-feature/</guid>
      <description>&lt;p&gt;Some new features have recently reach &lt;a href=&#34;https://redmine.openinfosecfoundation.org/projects/suricata/repository&#34;&gt;Suricata’s git tree&lt;/a&gt; and will be available in the next development release. I’ve worked on some of them that I will describe here.&lt;/p&gt;
&lt;h2 id=&#34;multi-interfaces-support-and-new-running-modes&#34;&gt;Multi interfaces support and new running modes&lt;/h2&gt;
&lt;h3 id=&#34;configuration-update&#34;&gt;Configuration update&lt;/h3&gt;
&lt;p&gt;IDS live mode in &lt;a href=&#34;http://www.openinfosecfoundation.org/&#34;&gt;suricata&lt;/a&gt; (pcap, pf_ring, af_packet) now supports the capture on multiple interfaces. The syntax of the YAML configuration file has evolved and it is now possible to set per-interface variables.&lt;/p&gt;
&lt;p&gt;For example, it is possible to define &lt;code&gt;pfring&lt;/code&gt; configuration with the following syntax:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Slides of my Suricata talk at Libre Software Meeting</title>
      <link>https://home.regit.org/2011/07/slides-of-my-suricata-talk-at-libre-software-meeting/</link>
      <pubDate>Wed, 13 Jul 2011 08:55:15 +0000</pubDate>
      <guid>https://home.regit.org/2011/07/slides-of-my-suricata-talk-at-libre-software-meeting/</guid>
      <description>&lt;p&gt;I gave a talk about Suricata entitled &lt;em&gt;Suricata, rethinking IDS/IPS&lt;/em&gt; at Libre Software Meeting (RMLL in french). &lt;a href=&#34;http://2011.rmll.info/IMG/pdf/2011_rmll_suricata.pdf&#34;&gt;The slides&lt;/a&gt; can be downloaded from the &lt;a href=&#34;http://2011.rmll.info/Suricata-repensez-les-IDS-IPS&#34;&gt;RMLL website&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Thanks a lot to &lt;a href=&#34;https://twitter.com/#!/cbrocas&#34;&gt;Christophe Brocas&lt;/a&gt; and Mathieu Blanc for the organisation of the security track of LSM.&lt;/p&gt;</description>
    </item>
    <item>
      <title>About Suricata performance boost between 1.0 and 1.1beta2</title>
      <link>https://home.regit.org/2011/06/about-suricata-performance-boost-between-1-0-and-1-1beta2/</link>
      <pubDate>Thu, 02 Jun 2011 19:45:03 +0000</pubDate>
      <guid>https://home.regit.org/2011/06/about-suricata-performance-boost-between-1-0-and-1-1beta2/</guid>
      <description>&lt;h2 id=&#34;discovering-the-performance-boost&#34;&gt;Discovering the performance boost&lt;/h2&gt;
&lt;p&gt;When doing some coding on both 1.0 and 1.1 branch of &lt;a href=&#34;http://www.openinfosecfoundation.org/&#34;&gt;suricata&lt;/a&gt;, I’ve remarked that there was a huge performance improvement of the 1.1 branch over the 1.0 branch. The parsing of a given real-life pcap file was taking 200 seconds with 1.0 but only 30 seconds with 1.1. This performance boost was huge and I decide to double check and to study how such a performance boost was possible and how it was obtained:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Suricata conference at Solutions Linux 2011</title>
      <link>https://home.regit.org/2011/05/suricata-sollinux-2011/</link>
      <pubDate>Wed, 11 May 2011 20:18:59 +0000</pubDate>
      <guid>https://home.regit.org/2011/05/suricata-sollinux-2011/</guid>
      <description>&lt;p&gt;I’ve gived today a presentation about &lt;a href=&#34;http://www.openinfosecfoundation.org/&#34;&gt;Suricata&lt;/a&gt; at the &lt;a href=&#34;http://www.solutionslinux.fr/&#34;&gt;Solutions Linux&lt;/a&gt; event. It was part of the security track presided by &lt;a href=&#34;http://hsc.fr/&#34;&gt;Herve Schauer&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The slides are in french and are available here: &lt;a href=&#34;http://home.regit.org/uploads/2011/05/2011_sollinux_suricata.pdf&#34;&gt;2011_sollinux_suricata&lt;/a&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
