<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://blog.gl2i.com/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://blog.gl2i.com/feed.php">
        <title>Blog GL2i - en:security</title>
        <description></description>
        <link>http://blog.gl2i.com/</link>
        <image rdf:resource="http://blog.gl2i.com/lib/exe/fetch.php?media=wiki:dokuwiki.svg" />
       <dc:date>2026-05-30T19:29:21+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://blog.gl2i.com/doku.php?id=en:security:iptables&amp;rev=1620013154&amp;do=diff"/>
                <rdf:li rdf:resource="http://blog.gl2i.com/doku.php?id=en:security:reaction-v2&amp;rev=1754242215&amp;do=diff"/>
                <rdf:li rdf:resource="http://blog.gl2i.com/doku.php?id=en:security:reaction&amp;rev=1754241812&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://blog.gl2i.com/lib/exe/fetch.php?media=wiki:dokuwiki.svg">
        <title>Blog GL2i</title>
        <link>http://blog.gl2i.com/</link>
        <url>http://blog.gl2i.com/lib/exe/fetch.php?media=wiki:dokuwiki.svg</url>
    </image>
    <item rdf:about="http://blog.gl2i.com/doku.php?id=en:security:iptables&amp;rev=1620013154&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-05-03T03:39:14+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>iptables</title>
        <link>http://blog.gl2i.com/doku.php?id=en:security:iptables&amp;rev=1620013154&amp;do=diff</link>
        <description>Iptables

One golden rule we have in security is: first close everything then open services one by one and only to  white listed IPs.

It is exactly what we are going to see together with SSH protocol.

Firewall

Iptables is one of the most famous firewall on Linux. Some people say that it is too complicated and that's why ufw has been created. But still, Iptables is the only one for me</description>
    </item>
    <item rdf:about="http://blog.gl2i.com/doku.php?id=en:security:reaction-v2&amp;rev=1754242215&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-08-03T17:30:15+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>reaction-v2</title>
        <link>http://blog.gl2i.com/doku.php?id=en:security:reaction-v2&amp;rev=1754242215&amp;do=diff</link>
        <description>Reaction v2

Great news, reaction has released a version 2. It goes from GO to Rust.

In my OpenSSH use case, memory usage drops down by half.

[usage reaction v2]

Background image by David Revoy CC-BY 4.0

To celebrate, I updated my ansible playbook.


- name: install packages required to have logs
  package:
    name: &quot;{{ item }}&quot;
    state: latest
  with_items:
    - iptables
    - iptables-persistent
    - logrotate
    - rsyslog
  become: True

- name: stop reaction if running
  service:
 …</description>
    </item>
    <item rdf:about="http://blog.gl2i.com/doku.php?id=en:security:reaction&amp;rev=1754241812&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-08-03T17:23:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>reaction</title>
        <link>http://blog.gl2i.com/doku.php?id=en:security:reaction&amp;rev=1754241812&amp;do=diff</link>
        <description>Reaction the new fail2ban

Context

When you have a server reachable from internet, it is a very good idea to control who has access to it and how. For years I am using the very good tool called iptables in a very restricted way. But it happened to me a story that I am going to share with you that made change my mind</description>
    </item>
</rdf:RDF>
