<?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>Sun, 08 Mar 2026 18:11:00 +0100</lastBuildDate>
  
   <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>Fri, 13 Jul 2018 12:42:00 +0100</pubDate>
      <link>https://vincentdelft.be/post/post_20180713</link> 
      <guid>https://vincentdelft.be/post/post_20180713</guid> 
      <title>Hardening your openbsd machine.</title>
      <description><![CDATA[<p>You have selected OpenBSD because this is one of the most secured OS (maybe the most secured :-) ), but people around you ask to go further. 
Your current machine is directly facing internet and some people fear that this machine could be compromised. In this blog I will explain what I did to secure one of my machine. </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>
   
   <item>
      <pubDate>Thu, 14 Jul 2016 15:25:00 +0100</pubDate>
      <link>https://vincentdelft.be/post/post_20160714</link> 
      <guid>https://vincentdelft.be/post/post_20160714</guid> 
      <title>How I've tuned OpenBSD to become my house's firewall</title>
      <description><![CDATA[<p>In this post I'll explain what I did to filter the internet access in my house. 
You will see that the access is based on simple rules and is not the same for every users. </p>]]></description>
   </item>
   
   <item>
      <pubDate>Tue, 12 Jul 2016 12:06:00 +0100</pubDate>
      <link>https://vincentdelft.be/post/post_20160712</link> 
      <guid>https://vincentdelft.be/post/post_20160712</guid> 
      <title>Build a Read only system with OpenBSD</title>
      <description><![CDATA[<p>When you have machines that must run 24x7, you must take into account the problem of powercut. 
To my eyes there is 2 possible solutions:</p>
<ul>
<li>use an UPS</li>
<li>have a readonly operating system</li>
</ul>
<p>In this post, I'll describe how you can easily transform your OpenBSD machine into a Read-only system. </p>]]></description>
   </item>
   
  </channel>
</rss>