<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Firewalld on UID1k Blog</title>
    <link>https://uid1k.blog/tags/firewalld/</link>
    <description>Recent content in Firewalld on UID1k Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 22 Aug 2026 17:30:25 +0300</lastBuildDate>
    <atom:link href="https://uid1k.blog/tags/firewalld/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Collecting and blocking IP addresses of failed login attempts</title>
      <link>https://uid1k.blog/posts/firewalld-ipset-postfix/</link>
      <pubDate>Sat, 22 Aug 2026 17:30:25 +0300</pubDate>
      <guid>https://uid1k.blog/posts/firewalld-ipset-postfix/</guid>
      <description>&lt;p&gt;Today we gonna explore a interesting security issue and solution for it.&#xA;While most organization are using centralized logging and centralized firewalls, services running&#xA;on standalone servers or VMs have been always a target to malicious actors.&#xA;In today post we will dive into authentication failures and ways to protect ourselves from those. In our scenario&#xA;we will be protecting a mail server, which is running postfix and dovecot locally. However the method&#xA;described here is not limited to the services mentioned above and can be applied to a large number of others.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
