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

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.

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.

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, ...

This post will explain how OpenBSD can easily helps you to ban those persons out of your machine for quite a long time.

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.

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:

• use an UPS
• have a readonly operating system

In this post, I'll describe how you can easily transform your OpenBSD machine into a Read-only system.