<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Posts on Aperture Zone</title>
    <link>https://aperturezone.com/posts/</link>
    <description>Recent content in Posts on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Fri, 17 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Watercooling forever</title>
      <link>https://aperturezone.com/posts/water3/</link>
      <pubDate>Fri, 17 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/water3/</guid>
      <description>&lt;p&gt;Round three of the water cooling saga. An old-timer, a 2001 Juno P6 Full Tower, a Ryzen 7 5700X that was overheating with air cooling, an angle grinder, a Dremel, and a Corsair iCUE H100i.&lt;/p&gt;
&lt;p&gt;&amp;gt; The first two installments of the water cooling saga were intentionally brief—a few photos, the essentials, no long-winded stories. This time, I’ve decided to give you a real treat. You’ve been warned.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;i-want-one-too&#34;&gt;“I want one too”&lt;/h2&gt;
&lt;p&gt;There’s one phrase that sums up the whole project: &lt;em&gt;“I want one too”&lt;/em&gt;.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>TrueNAS SCALE: unfiltered feedback</title>
      <link>https://aperturezone.com/posts/truenas/</link>
      <pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/truenas/</guid>
      <description>&lt;p&gt;In recent years, TrueNAS SCALE has established itself as the go-to open-source solution for building a high-performance NAS for personal use. Based on Debian Linux and powered by ZFS, it promises the best of both worlds: the robustness of an enterprise-grade file system and the flexibility of a modern platform with containers and integrated applications. On paper, it sounds appealing. In practice, it’s a bit more nuanced—and that’s the focus of this article.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Cisco ASA &amp; Firepower FTD - Complete Guide</title>
      <link>https://aperturezone.com/posts/cisco-firewall-final/</link>
      <pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/cisco-firewall-final/</guid>
      <description>&lt;p&gt;&amp;gt; Comprehensive Guide: Beginner to Expert — Cisco ASA 5500-X · Firepower FTD · FMC · AnyConnect · Snort IPS 3&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;table-of-contents&#34;&gt;Table of Contents&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Part 1 — Cisco ASA&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;a href=&#34;#1-introduction--asa-models&#34;&gt;Introduction &amp;amp; ASA Models&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#2-getting-started--cli--asdm&#34;&gt;Getting Started: CLI &amp;amp; ASDM&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#3-interfaces--security-levels&#34;&gt;Interfaces &amp;amp; Security Levels&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#4-nat--pat-on-asa&#34;&gt;NAT &amp;amp; PAT on ASA&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#5-acl--security-policy&#34;&gt;ACL &amp;amp; Security Policy&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#6-site-to-site-vpn--anyconnect&#34;&gt;Site-to-Site VPN &amp;amp; AnyConnect&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#7-active-standby-high-availability&#34;&gt;Active/Standby High Availability&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Part 2 — ASA to FTD Migration&lt;/strong&gt;&lt;/p&gt;
&lt;ol start=&#34;8&#34;&gt;
&lt;li&gt;&lt;a href=&#34;#8-asa-vs-ftd--key-differences&#34;&gt;ASA vs. FTD — Key Differences&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#9-migration-process&#34;&gt;Migration Process&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Part 3 — Cisco Firepower FTD&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Installing Passbolt CE on Ubuntu 24.04 with an internal CA</title>
      <link>https://aperturezone.com/posts/passbolt-ce-install/</link>
      <pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/passbolt-ce-install/</guid>
      <description>&lt;p&gt;&amp;gt; When I decided to set up my own Passbolt server, I relied on the excellent article by &lt;strong&gt;caddy666&lt;/strong&gt;: &lt;a href=&#34;https://aperturezone.fr/posts/passbolt/&#34;&gt;https://aperturezone.fr/posts/passbolt/&lt;/a&gt;. However, the version has evolved quite a bit since then, and several steps no longer matched what I was seeing on my screen. So I decided to write an update—this in no way detracts from the relevance of the original article, which remains a very good introduction to Passbolt, but the steps below reflect the current state of version CE 5.10.0 on Ubuntu 24.04.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>OCS Inventory NG - What the doc doesn&#39;t say</title>
      <link>https://aperturezone.com/posts/ocs-inventory/</link>
      <pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/ocs-inventory/</guid>
      <description>&lt;h2 id=&#34;the-project&#34;&gt;The Project&lt;/h2&gt;
&lt;p&gt;The initial idea was simple: deploy &lt;strong&gt;OCS Inventory NG&lt;/strong&gt; to centralize the hardware and software inventory of the infrastructure. A server, agents, a web console. Nothing too complicated.&lt;/p&gt;
&lt;p&gt;Spoiler: I thought it would be a piece of cake, but it turned out to be a real headache.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;act-1--server-installation-or-quotperl-is-your-enemyquot&#34;&gt;Act 1 — Server Installation, or &amp;quot;Perl Is Your Enemy&amp;quot;&lt;/h2&gt;
&lt;p&gt;Installing OCS on the server side involves a &lt;code&gt;setup.sh&lt;/code&gt; script that asks questions. Lots of questions. And it expects precise answers—pressing Enter without thinking is a recipe for disaster.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>DRP on Hyper-V with Veeam: from chaos to clean failover</title>
      <link>https://aperturezone.com/posts/drpveeam/</link>
      <pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/drpveeam/</guid>
      <description>&lt;p&gt;I have a virtualized infrastructure running on &lt;strong&gt;Hyper-V&lt;/strong&gt; with a separate backup/DRP server. The entire stack runs on &lt;strong&gt;19 VMs&lt;/strong&gt;: two Active Directory domains with domain joining, Linux DNS forwarders (BIND9), RADIUS, monitoring, application services&amp;hellip; in short, not something we can afford to just reboot haphazardly.&lt;/p&gt;
&lt;p&gt;The project’s objective was simple to state, but complex to achieve:&lt;/p&gt;
&lt;p&gt;&amp;gt; &lt;strong&gt;Switchover the entire infrastructure to the DRP server with minimal effort, ensuring service continuity (at the very least, not cutting off internet access), then return to production cleanly.&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Backing up GPOs with Ansible and WinRM</title>
      <link>https://aperturezone.com/posts/backup_gpo/</link>
      <pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/backup_gpo/</guid>
      <description>&lt;p&gt;Group Policy Objects are at the heart of any robust Active Directory infrastructure. They define security settings, permissions, device configurations, and software restrictions. In the event of a disaster, human error, or simply a need to roll back after a change, not having a backup of your GPOs means facing hours of tedious reconstruction.&lt;/p&gt;
&lt;p&gt;The graphical interface of the Group Policy Management Console does offer a backup feature, but it is manual, easy to overlook, and, most importantly, not versioned. The goal of this article is to automate this process cleanly using Ansible via WinRM, on an infrastructure comprising &lt;strong&gt;two separate Active Directory domains&lt;/strong&gt;, with long-term archiving on a NAS and reporting via email.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Active Directory: krbtgt, from theory to practice</title>
      <link>https://aperturezone.com/posts/krbtgt2/</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/krbtgt2/</guid>
      <description>&lt;p&gt;In the &lt;a href=&#34;https://aperturezone.fr/posts/krbtgt/&#34;&gt;first part of this article&lt;/a&gt;, we laid the groundwork: what the krbtgt account is, why the Golden Ticket is a serious threat, and a theoretical Ansible architecture for automating rotations. If you haven’t read that part, I encourage you to start there.&lt;/p&gt;
&lt;p&gt;Now we’re getting down to business. The playbook in Part 1 was intentionally simplified to illustrate the concept. In a real production environment, things get complicated—the interactive script that refuses to be controlled, the XML file that can’t be found, the Kerberos double-hop that blocks everything, the root forest that isn’t what we think it is. These are all obstacles I’ve encountered and resolved, which I’m documenting here.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Server 2022 migration: multi-domain forest</title>
      <link>https://aperturezone.com/posts/migration2022/</link>
      <pubDate>Fri, 27 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/migration2022/</guid>
      <description>&lt;p&gt;In a &lt;a href=&#34;https://aperturezone.com/posts/approvals&#34;&gt;previous post&lt;/a&gt;, I described the 2016 functional upgrade and the approvals audit between my two domains. I ended on this note: &lt;em&gt;&amp;quot;I’ll also need to think about upgrading the OS on my other controllers.&amp;quot;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Well, that’s done.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;
&lt;p&gt;The infrastructure is based on a two-domain Active Directory forest:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A &lt;strong&gt;forest root domain&lt;/strong&gt;, dedicated to servers and hypervisors—two domain controllers ensure its availability. The first holds the domain roles (PDC Emulator, RID Master, Infrastructure Master), while the second holds the forest roles (Schema Master, Domain Naming Master).&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;child domain&lt;/strong&gt;, dedicated to workstations and users—also with two domain controllers. The first holds the domain’s FSMO roles as well as the DNS service and the primary DHCP. The second ensures continuity: Global Catalog, secondary DNS, failover DHCP, and Certificate Authority. Without these roles, a second DC would be nothing more than a passive replica—so we might as well give it a real reason to exist.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;All were running on &lt;strong&gt;Windows Server 2016&lt;/strong&gt;, for which mainstream support ended in 2022 and extended support ends in January 2027. The time had come to migrate to &lt;strong&gt;Windows Server 2022&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Active Directory: krbtgt the scary account</title>
      <link>https://aperturezone.com/posts/krbtgt/</link>
      <pubDate>Wed, 25 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/krbtgt/</guid>
      <description>&lt;p&gt;There are elements in Active Directory that we completely forget about because they never come up in day-to-day operations. The &lt;strong&gt;krbtgt&lt;/strong&gt; account is one of them. Though invisible in everyday use, it is at the heart of all Kerberos authentication in your domain—and its compromise is one of the most catastrophic scenarios an attacker could trigger.&lt;/p&gt;
&lt;p&gt;In this article, we’ll explore what this account really is, why you need to change its password regularly, and how to automate this process cleanly with &lt;strong&gt;Ansible&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Automate network device configuration backup with Ansible</title>
      <link>https://aperturezone.com/posts/ansible2/</link>
      <pubDate>Mon, 23 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/ansible2/</guid>
      <description>&lt;p&gt;Whether in a home lab or a professional infrastructure, network equipment is often overlooked in backup strategies. We think about backing up VMs, data, and servers—but rarely the configurations of switches and Wi-Fi access points. However, in the event of a failure or hardware replacement, not having the configuration on hand can result in hours of work to rebuild the system.&lt;/p&gt;
&lt;p&gt;In this article, we’ll set up an Ansible playbook that automatically backs up our network equipment configurations, stores them locally with a 30-day retention period, and sends an HTML report via email after each run.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Spanning Tree Protocol: understanding and deploying STP/MSTP</title>
      <link>https://aperturezone.com/posts/stp/</link>
      <pubDate>Fri, 13 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/stp/</guid>
      <description>&lt;h1 id=&#34;heading&#34;&gt;&lt;/h1&gt;
&lt;hr&gt;
&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;If you have multiple switches, you’ve surely heard of the &lt;strong&gt;Spanning Tree Protocol&lt;/strong&gt;. But there’s often a gap between theory and practice—especially when you encounter unusual hardware with unexpected interfaces.&lt;/p&gt;
&lt;p&gt;This article details a real-world implementation of MSTP on three HP 1910 switches (based on Comware H3C), including the problems encountered and the solutions found. Spoiler: the GUI won’t be your friend.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;why-stp&#34;&gt;Why STP?&lt;/h2&gt;
&lt;h3 id=&#34;the-loop-problem&#34;&gt;The Loop Problem&lt;/h3&gt;
&lt;p&gt;In a network with multiple interconnected switches, &lt;strong&gt;physical loops&lt;/strong&gt; can exist—whether intentional for redundancy or accidental. Without protection, a broadcast frame enters a loop and circulates indefinitely, duplicating itself with each pass. Within seconds, the network is 100% saturated: this is a &lt;strong&gt;broadcast storm&lt;/strong&gt;, and it renders the infrastructure completely unusable.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Aperture Zone now available in English!</title>
      <link>https://aperturezone.com/posts/versionuk/</link>
      <pubDate>Thu, 12 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/versionuk/</guid>
      <description>&lt;p&gt;Good news! &lt;strong&gt;Aperture Zone is now available in English&lt;/strong&gt; at &lt;a href=&#34;https://aperturezone.com&#34;&gt;aperturezone.com&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;Starting today, all of our technical articles are available in both languages:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;🇫🇷 French version&lt;/strong&gt;: &lt;a href=&#34;https://aperturezone.fr&#34;&gt;aperturezone.fr&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;🇬🇧 English version&lt;/strong&gt;: &lt;a href=&#34;https://aperturezone.com&#34;&gt;aperturezone.com&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;automatic-translation&#34;&gt;Automatic translation&lt;/h2&gt;
&lt;p&gt;To make our content accessible to as many people as possible, we use DeepL automatic translation. Articles are translated automatically when they are published.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Important note&lt;/strong&gt;: Caddy666 will manually review and correct the translations to ensure quality and technical accuracy.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>PFSENSE - Complete &amp; Professional Guide</title>
      <link>https://aperturezone.com/posts/pfsense/</link>
      <pubDate>Thu, 12 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/pfsense/</guid>
      <description>&lt;p&gt;&amp;gt; Advanced Professional Guide — pfSense 2.7+ · FreeBSD · OpenVPN · IPsec · VLAN · HAProxy · Snort / Suricata&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;table-of-contents&#34;&gt;Table of Contents&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;a href=&#34;#1-hardware--environment-requirements&#34;&gt;Hardware &amp;amp; Environment Requirements&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#2-installing-pfSense&#34;&gt;Installing pfSense&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#3-initial-configuration--interfaces&#34;&gt;Initial configuration &amp;amp; interfaces&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#4-advanced-firewall-rules&#34;&gt;Advanced firewall rules&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#5-vlan--network-segmentation&#34;&gt;VLAN &amp;amp; network segmentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#6-vpn--openvpn--ipsec&#34;&gt;VPN — OpenVPN &amp;amp; IPsec&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#7-idsips--snort--suricata&#34;&gt;IDS/IPS — Snort &amp;amp; Suricata&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#8-high-availability-carp&#34;&gt;High availability (CARP)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#9-monitoring--alerts&#34;&gt;Monitoring &amp;amp; alerts&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;#10-best-practices--hardening&#34;&gt;Best practices &amp;amp; hardening&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;h2 id=&#34;1-hardware-amp-environment-prerequisites&#34;&gt;1. Hardware &amp;amp; environment prerequisites&lt;/h2&gt;
&lt;p&gt;pfSense is based on FreeBSD and requires dedicated or virtualized hardware for optimal performance in production.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>LACP on HP V1910 (H3C Comware)</title>
      <link>https://aperturezone.com/posts/lacp/</link>
      <pubDate>Wed, 11 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/lacp/</guid>
      <description>&lt;p&gt;&amp;gt; &lt;strong&gt;Infrastructure involved&lt;/strong&gt;: HP V1910 (x2), Synology NAS (x3), TrueNAS, Windows Server 2022 (Hyper-V)&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;LACP (Link Aggregation Control Protocol), defined by the &lt;strong&gt;IEEE 802.3ad&lt;/strong&gt; standard (part of 802.1AX), allows multiple physical links to be grouped into a single logical link called a LAG (Link Aggregation Group). There are numerous benefits:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Increased aggregate bandwidth&lt;/strong&gt; for multiple traffic flows&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Automatic redundancy&lt;/strong&gt;: if a physical link fails, the others take over without intervention&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dynamic negotiation&lt;/strong&gt;: the protocol detects and adapts to changes in link status&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&amp;gt; ⚠️ &lt;strong&gt;Important&lt;/strong&gt;: LACP does not increase the throughput of a single flow. A given flow always remains on the same physical link (hashing). The benefit is realized across multiple simultaneous flows.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>HTTPS on HP ProCurve V1910</title>
      <link>https://aperturezone.com/posts/procurve/</link>
      <pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/procurve/</guid>
      <description>&lt;p&gt;Securing access to the web interface of managed switches is one of those tasks that seems trivial on paper. On recent hardware, it is indeed trivial. On HP ProCurve V1910 switches—Comware v5 switches that are still used in many home labs and small infrastructures—it&#39;s a different story. This article documents the entire project, the pitfalls, the discoveries, and an honest conclusion about what it&#39;s really worth.&lt;/p&gt;
&lt;p&gt;The test infrastructure: three HP V1910 switches (firmware 5.20 Release 1519P06) on a dedicated, isolated management VLAN with no Internet access. An internal CA based on OpenSSL runs on a Linux server in the infrastructure.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>WiFi WPA2-Enterprise authentication with NPS and Active Directory</title>
      <link>https://aperturezone.com/posts/nps/</link>
      <pubDate>Sat, 07 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/nps/</guid>
      <description>&lt;p&gt;Are you tired of managing a shared WiFi key that everyone knows, which you never dare to change for fear of having to reconfigure all your devices? The clean solution is &lt;strong&gt;WPA2-Enterprise&lt;/strong&gt;—each user authenticates with their own Active Directory credentials, without ever entering a WiFi password. The domain-joined laptop connects automatically, transparently, as soon as the Ethernet cable is unplugged.&lt;/p&gt;
&lt;p&gt;In this article, we&#39;ll transform an existing SSID into WPA2-Enterprise using &lt;strong&gt;NPS (Network Policy Server)&lt;/strong&gt; as the RADIUS server, &lt;strong&gt;Active Directory&lt;/strong&gt; for user management, and a &lt;strong&gt;GPO&lt;/strong&gt; to automate the connection on domain laptops. We&#39;ll use &lt;strong&gt;Cisco Aironet&lt;/strong&gt; access points in standalone mode.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Watercooling, oops i did it again!</title>
      <link>https://aperturezone.com/posts/water2/</link>
      <pubDate>Fri, 06 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/water2/</guid>
      <description>&lt;p&gt;I emptied my Pea and treated myself to a second Corsair kit (actually, it was on sale and begged me to buy it).
Unlike the first article I published, this case was not designed to accommodate water cooling at all. You&#39;ll see that you&#39;ll need to get out the angle grinder!&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/WATER2/Water2_001.jpg&#34; alt=&#34;Photo 1&#34;  /&gt;

Here is the tower before modification. It&#39;s not in its prime, but it&#39;s functional. It&#39;s an Antec from the early 2010s.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Active Directory: 2016 functional upgrade and approval audit</title>
      <link>https://aperturezone.com/posts/approbations/</link>
      <pubDate>Mon, 02 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/approbations/</guid>
      <description>&lt;p&gt;There are some projects that we put off for years. Not because they&#39;re impossible, but because there&#39;s always something getting in the way. In my case, it was Exchange 2013—that good old mail server that stood in the way of any attempt to modernize the AD. Since migrating to a lighter solution, the coast was clear. So here&#39;s the story of a busy night&#39;s work.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;the-context&#34;&gt;The context&lt;/h2&gt;
&lt;p&gt;The infrastructure runs on two separate Active Directory domains linked by a two-way trust relationship:&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Hardening AD with PingCastle</title>
      <link>https://aperturezone.com/posts/pingcastle/</link>
      <pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/pingcastle/</guid>
      <description>&lt;h1 id=&#34;pingcastle-amp-hardening-active-directory&#34;&gt;PingCastle &amp;amp; Hardening Active Directory&lt;/h1&gt;
&lt;p&gt;Active Directory is the cornerstone of identity and access management in most Windows environments. Its critical nature also makes it a prime target for attackers. A poorly configured AD can allow privilege escalation, lateral movement, or even total domain compromise.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;PingCastle&lt;/strong&gt; is now one of the benchmark tools for assessing the security posture of an Active Directory. It was developed by &lt;strong&gt;Vincent Le Toux&lt;/strong&gt;, a renowned French expert in offensive security circles whose mastery of Windows and Active Directory internals is widely recognized. He is said to have close ties to &lt;strong&gt;ANSSI&lt;/strong&gt;—a persistent urban legend in the community, fueled by the depth and quality of the tool&#39;s detection rules, which reflect a knowledge of attack vectors rarely achieved outside of government circles. Vincent Le Toux is also co-author of &lt;strong&gt;mimikatz&lt;/strong&gt;, the global benchmark tool for extracting Windows credentials.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Integrating a watercooler into an old LianLi box</title>
      <link>https://aperturezone.com/posts/water1/</link>
      <pubDate>Wed, 25 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/water1/</guid>
      <description>&lt;p&gt;#For Christmas, I was given a CORSAIR water cooling kit. This isn&#39;t an advertisement; I just think it&#39;s good equipment.
(Yes, Santa Claus does exist! Here&#39;s the proof!)&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/WATER1/Water1_001.jpg&#34; alt=&#34;Photo 1&#34;  /&gt;

So here&#39;s the tower that will integrate the water cooling before modifications. It&#39;s a Lian Li case that&#39;s between 10 and 15 years old, but still very clean and functional.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/WATER1/Water1_002.jpg&#34; alt=&#34;Photo 2&#34;  /&gt;

There you go, I&#39;ve made some space to work.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Automation with Ansible</title>
      <link>https://aperturezone.com/posts/ansible/</link>
      <pubDate>Tue, 24 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/ansible/</guid>
      <description>&lt;h3 id=&#34;package-updates-ntp-synchronization-and-html-email-notifications-on-ubuntu-2404&#34;&gt;Package updates, NTP synchronization, and HTML email notifications on Ubuntu 24.04&lt;/h3&gt;
&lt;hr&gt;
&lt;p&gt;Manually managing multiple Linux servers quickly becomes tedious and prone to errors: forgotten updates, undetected time zone differences, inconsistent NTP configurations, etc. Ansible solves this problem by allowing you to automate system administration in a reproducible way, without having to install an agent on the target machines.&lt;/p&gt;
&lt;p&gt;We will set up an Ansible server on &lt;strong&gt;Ubuntu 24.04 LTS&lt;/strong&gt;, configure a server inventory, and deploy a complete playbook that performs the following in a single execution:&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Internal mail server with postfix and dovecot</title>
      <link>https://aperturezone.com/posts/postfix/</link>
      <pubDate>Mon, 23 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/postfix/</guid>
      <description>&lt;p&gt;I need an internal mail server (it will not be open to the outside world) to receive posts from the infrastructure in general, router switch, or backup reports. We will do this with Postfix and Dovecot on Ubuntu 24.04. The emails are intended for an existing AD user.&lt;/p&gt;
&lt;h2 id=&#34;1-join-the-server-to-the-active-directory-domain-with-sssd&#34;&gt;1. Join the server to the Active Directory domain with SSSD&lt;/h2&gt;
&lt;h3 id=&#34;install-the-necessary-packages&#34;&gt;Install the necessary packages&lt;/h3&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;sudo apt update
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;sudo apt install realmd sssd sssd-tools adcli samba-common-bin libnss-sss libpam-sss
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id=&#34;discover-and-join-the-domain&#34;&gt;Discover and join the domain&lt;/h3&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#75715e&#34;&gt;# Check that the domain is accessible&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;realm discover mydomain.local
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;&lt;span style=&#34;color:#75715e&#34;&gt;# Join the domain (an AD account with sufficient rights is required)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;sudo realm join --user&lt;span style=&#34;color:#f92672&#34;&gt;=&lt;/span&gt;Administrator mydomain.local
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id=&#34;check-the-join&#34;&gt;Check the join&lt;/h3&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;realm list
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;You should see something like:&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Installing and securing Passbolt</title>
      <link>https://aperturezone.com/posts/passbolt/</link>
      <pubDate>Fri, 20 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/passbolt/</guid>
      <description>&lt;h1 id=&#34;passbolt-configuration-and-security-tutorial&#34;&gt;Passbolt Configuration and Security Tutorial&lt;/h1&gt;
&lt;p&gt;This tutorial covers the installation, configuration, and security of a Passbolt server: &lt;a href=&#34;https://www.passbolt.com/docs/&#34;&gt;Documentation&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;prerequisites&#34;&gt;Prerequisites&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A domain name/host name pointing to a server, or at least the ability to reach the server via a static IP address.&lt;/li&gt;
&lt;li&gt;A VM with at least 2 cores and 2 GB of RAM&lt;/li&gt;
&lt;li&gt;An SMTP server&lt;/li&gt;
&lt;li&gt;A functional NTP service to avoid GPG authentication issues&lt;/li&gt;
&lt;li&gt;Ubuntu Server 24.04 with LVM encryption&lt;/li&gt;
&lt;li&gt;Provision SSL certificates&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&#34;it-is-important-to-use-a-clean-server-with-no-other-services-or-tools-already-installed-the-installation-scripts-could-potentially-crash-and-damage-data&#34;&gt;It is important to use a clean server with no other services or tools already installed. The installation scripts could potentially crash and damage data.&lt;/h3&gt;
&lt;h3 id=&#34;vm-configuration&#34;&gt;VM configuration:&lt;/h3&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/PASSBOLT/hardwareVMpassbolt.png&#34; alt=&#34;VM hardware configuration&#34;  /&gt;
&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Clonezilla &#43; Samba server</title>
      <link>https://aperturezone.com/posts/clonezilla3/</link>
      <pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/clonezilla3/</guid>
      <description>&lt;p&gt;Okay, we&#39;ve seen how to create a Clonezilla image, and we&#39;ve also seen how to restore it. All of that was done locally, so now we&#39;re going to do the same thing but with remote storage on the network.
We&#39;re going to work with a share on a Microsoft server with authentication.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/CLONEZILLA3/Clonezilla3_001.jpg&#34; alt=&#34;Photo 1&#34;  /&gt;

I&#39;ll start by creating a user on the AD.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/CLONEZILLA3/Clonezilla3_002.jpg&#34; alt=&#34;Photo 2&#34;  /&gt;

I&#39;m not going to complicate things too much; the user is called clonezilla.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Backup system with Clonezilla</title>
      <link>https://aperturezone.com/posts/clonezilla1/</link>
      <pubDate>Wed, 18 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/clonezilla1/</guid>
      <description>&lt;p&gt;Download the latest ISO from &lt;a href=&#34;https://clonezilla.org/downloads.php&#34;&gt;https://clonezilla.org/downloads.php&lt;/a&gt;
and prepare a bootable USB key or boot pxe with Iventoy, for example&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/CLONEZILLA1/Clonezilla1_001.jpg&#34; alt=&#34;Photo 1&#34;  /&gt;

This is the welcome screen. It&#39;s minimalist, but that&#39;s all you need.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/CLONEZILLA1/Clonezilla1_002.jpg&#34; alt=&#34;Photo 2&#34;  /&gt;

Select French at random.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/CLONEZILLA1/Clonezilla1_003.jpg&#34; alt=&#34;Photo 3&#34;  /&gt;

We&#39;ll choose a French keyboard, as it will be more practical.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/CLONEZILLA1/Clonezilla1_004.jpg&#34; alt=&#34;Photo 4&#34;  /&gt;

Select Latin9.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/CLONEZILLA1/Clonezilla1_005.jpg&#34; alt=&#34;Photo 5&#34;  /&gt;

Start Clonezilla, of course.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/CLONEZILLA1/Clonezilla1_006.jpg&#34; alt=&#34;Photo 6&#34;  /&gt;

We are going to create an image of an entire disk, so we select device-image.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Restore system with Clonezilla</title>
      <link>https://aperturezone.com/posts/clonezilla2/</link>
      <pubDate>Wed, 18 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/clonezilla2/</guid>
      <description>&lt;p&gt;We have seen how to create a system image with Clonezilla.
Now we are going to restore it.
In the previous article, we saw how to start up, set up the French keyboard, etc. I won&#39;t repeat the screenshots.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/CLONEZILLA2/Clonezilla2_001.jpg&#34; alt=&#34;Photo 1&#34;  /&gt;

We reselect our /dev/sdd1/CLONEZILLA folder as the source.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/CLONEZILLA2/Clonezilla2_002.jpg&#34; alt=&#34;Photo 2&#34;  /&gt;

And we confirm.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/CLONEZILLA2/Clonezilla2_003.jpg&#34; alt=&#34;Photo 3&#34;  /&gt;

Expert mode, of course.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/CLONEZILLA2/Clonezilla2_004.jpg&#34; alt=&#34;Photo 4&#34;  /&gt;

So this time we select restoredisk&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Raid controller replacement</title>
      <link>https://aperturezone.com/posts/lsi_raid/</link>
      <pubDate>Mon, 16 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/lsi_raid/</guid>
      <description>&lt;p&gt;Problem with my IBM ServeRaid M5015 controller. I found the same one second-hand on eBay for €30.
So replacement will be seamless with a foreign config import.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/LSI_RAID/Lsi_Raid_001.jpg&#34; alt=&#34;Photo 1&#34;  /&gt;

Here&#39;s the beast. The fan on top is already custom-made because it was heating up a lot.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/LSI_RAID/Lsi_Raid_002.jpg&#34; alt=&#34;Photo 2&#34;  /&gt;

Removing the fan to reuse it.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/LSI_RAID/Lsi_Raid_003.jpg&#34; alt=&#34;Photo 3&#34;  /&gt;

Same for the battery.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/LSI_RAID/Lsi_Raid_004.jpg&#34; alt=&#34;Photo 4&#34;  /&gt;

Here is the replacement&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Boote PXE with Iventoy</title>
      <link>https://aperturezone.com/posts/iventoy/</link>
      <pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/iventoy/</guid>
      <description>&lt;p&gt;Ventoy, which many people are familiar with, can be installed on a USB drive or external hard drive.
You add ISOs and boot from the ISO you want to use.
Less well known is the PXE server version.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/IVENTOY/Iventoy_001.png&#34; alt=&#34;Photo 1&#34;  /&gt;

A nice logo&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/IVENTOY/Iventoy_002.png&#34; alt=&#34;Photo 2&#34;  /&gt;

wget &lt;a href=&#34;https://github.com/ventoy/PXE/releases/download/v1.0.21/iventoy-1.0.21-linux-free.tar.gz&#34;&gt;https://github.com/ventoy/PXE/releases/download/v1.0.21/iventoy-1.0.21-linux-free.tar.gz&lt;/a&gt;
to retrieve the archive&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/IVENTOY/Iventoy_003.png&#34; alt=&#34;Photo 3&#34;  /&gt;

tar -xvf iventoy-1.0.21-linux-free.tar.gz
To unzip&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/IVENTOY/Iventoy_004.png&#34; alt=&#34;Photo 4&#34;  /&gt;

sudo ./iventoy.sh start
You can now connect to your Iventoy server&#39;s GUI&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>QUADRO Revival</title>
      <link>https://aperturezone.com/posts/quadro/</link>
      <pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/quadro/</guid>
      <description>&lt;p&gt;I needed to install a graphics card for a machine intended for office use.
I dug out this old Quadro from the grave, but what an unbearable noise it makes!
The fan shaft has play, it rubs and squeaks like an animal in agony.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/QUADRO/Quadro_001.jpg&#34; alt=&#34;Photo 1&#34;  /&gt;

It&#39;s not in its prime, but it works&amp;hellip;&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/QUADRO/Quadro_002.jpg&#34; alt=&#34;Photo 2&#34;  /&gt;

Oh, there&#39;s a nice layer of crap inside&amp;hellip;&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/QUADRO/Quadro_003.jpg&#34; alt=&#34;Photo 3&#34;  /&gt;

A quick blast with a 3-bar air gun later&amp;hellip;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Mod of an Nvme SSD</title>
      <link>https://aperturezone.com/posts/mod_ssd_nvme/</link>
      <pubDate>Fri, 13 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/mod_ssd_nvme/</guid>
      <description>&lt;p&gt;I noticed by chance that my M2 SSD was getting really hot.
I couldn&#39;t even leave my finger on it, so I took it apart.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/SSD_NVME/ssd001.jpg&#34; alt=&#34;Photo 1&#34;  /&gt;

Here&#39;s the baby.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/SSD_NVME/ssd002.jpg&#34; alt=&#34;Photo 2&#34;  /&gt;

Warranty void if removed&amp;hellip; choose between the label or overheating?
The choice is easy, we&#39;ll remove the label.&lt;/p&gt;
&lt;p&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://aperturezone.com/images/SSD_NVME/ssd003.jpg&#34; alt=&#34;Photo 3&#34;  /&gt;

I cut a radiator to the right size
from an old Pentium 3 radiator that was lying around.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Welcome to Aperture Zone</title>
      <link>https://aperturezone.com/posts/premier-article/</link>
      <pubDate>Fri, 13 Feb 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/posts/premier-article/</guid>
      <description>&lt;h1 id=&#34;beyond-specs-deep-tech-stories&#34;&gt;Beyond Specs. Deep Tech Stories.&lt;/h1&gt;
&lt;p&gt;Welcome to APERTURE ZONE, a space dedicated to technical experiments, infrastructure, and hacks that go beyond simple specifications.
There&#39;s a world of difference between the datasheet and reality in the field. Because true expertise isn&#39;t found in marketing benchmarks, but in the hours spent debugging, optimizing, and understanding why it overheats, why it lags, why it doesn&#39;t scale.
We&#39;re done with corporations that sell you equipment and promise you the moon, copy-and-paste tutorials that don&#39;t work, and best practices that ignore the real constraints of the field.
Here, we talk about what really works. What really crashes. Solutions we found at 3 a.m. when everything goes haywire.
We&#39;re not saying it&#39;s better. We&#39;re not saying it&#39;s for everyone. But it&#39;s our way of doing IT.
This site is not sponsored. We don&#39;t sell anything. We don&#39;t do product placement. If we talk about a piece of equipment, it&#39;s because we actually use it and have an opinion about it.
The configurations we share are what we use ourselves. For real. Not in a sterile lab, but in our racks, with our constraints, our extremely limited budgets, our sometimes aging hardware that we keep running because we know how.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
