<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" >
<channel>
  <title>Vincent's blog</title>
  <link>https://vincentdelft.be/rss</link>
  <description>Vincent's ideas</description>
  <atom:link href="https://vincentdelft.be/rss" rel="self" type="application/rss+xml" />
  <lastBuildDate>Sat, 24 Oct 2026 17:43:00 +0100</lastBuildDate>
  
   <item>
      <pubDate>Sat, 24 Oct 2026 17:43:00 +0100</pubDate>
      <link>https://vincentdelft.be/post/post_20261024</link> 
      <guid>https://vincentdelft.be/post/post_20261024</guid> 
      <title>Tuning log2table rules with real logs, and with an AI looking over my shoulder</title>
      <description><![CDATA[<p><img alt="Give a shoutout to Zach M on unsplash.com" src="/static/post/post_20261024/ai.jpg" title="Give a shoutout to Zach M on unsplash.com" />
log2table is a small daemon I wrote: it watches log files, recognizes attack patterns with regular expressions, and puts the offending IP addresses in a PF table so the firewall blocks them. The whole behavior is driven by one file: <code>parameters.py</code>.</p>
<p>Writing rules is easy. Knowing whether they are <em>good</em> rules is harder: do they catch what is really hitting my server today? Do they ban innocent visitors? Do two rules count the same attack twice?</p>
<p>This post explains the new version of <code>parameters.py</code> in the repository, its built-in checker that runs against your real log files, and how I used an AI (Claude, through Claude Code) to read the checker's output and propose improvements.</p>]]></description>
   </item>
   
   <item>
      <pubDate>Sun, 08 Mar 2026 18:11:00 +0100</pubDate>
      <link>https://vincentdelft.be/post/post_20260308</link> 
      <guid>https://vincentdelft.be/post/post_20260308</guid> 
      <title>Thanks to log2table I'm able to secure my servers</title>
      <description><![CDATA[<p><img alt="Generated by AI" src="/static/post/post_20260308/log2table.png" title="Generated by AI" />
As for each server on internet, I receive lot of bad requests. Thanks to a continuous check on different log files, I'm able to automatically add bad IPs in the pf firewall (OpenBSD). 
This blog will explain how I've setup log2table and how I treat those bad IPs</p>]]></description>
   </item>
   
   <item>
      <pubDate>Sat, 27 May 2017 20:41:00 +0100</pubDate>
      <link>https://vincentdelft.be/post/post_20170517</link> 
      <guid>https://vincentdelft.be/post/post_20170517</guid> 
      <title>Log2table to protect your machines from intrusions</title>
      <description><![CDATA[<p>Log2table allows you to continuously monitor your logfiles. You can trigger actions when a specific message comes in your audited logfiles or when a specific number of occurrences are present. </p>]]></description>
   </item>
   
   <item>
      <pubDate>Sun, 06 Nov 2016 17:04:00 +0100</pubDate>
      <link>https://vincentdelft.be/post/post_20161106</link> 
      <guid>https://vincentdelft.be/post/post_20161106</guid> 
      <title>Block bad visitors with PF</title>
      <description><![CDATA[<p>Those days, when you fire-up a new machine, it takes few hours that bad persons are trying to connect to your machine via ssh, try default URL with default passwords, ... </p>
<p>This post will explain how OpenBSD can easily helps you to ban those persons out of your machine for quite a long time. </p>]]></description>
   </item>
   
  </channel>
</rss>