<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rhel9 on Panic! At The Terminal</title>
    <link>https://blog.nousiainen.xyz/tags/rhel9/</link>
    <description>Recent content in Rhel9 on Panic! At The Terminal</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 20 Jul 2025 22:45:27 +0300</lastBuildDate>
    <atom:link href="https://blog.nousiainen.xyz/tags/rhel9/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SSH Hardening and Automation User Setup with Ansible</title>
      <link>https://blog.nousiainen.xyz/docs/ssh-hardening-ansible/</link>
      <pubDate>Sat, 12 Jul 2025 12:00:00 +0300</pubDate>
      <guid>https://blog.nousiainen.xyz/docs/ssh-hardening-ansible/</guid>
      <description>&lt;h1 id=&#34;ssh-hardening-and-automation-user-setup-with-ansible&#34;&gt;&#xA;  SSH Hardening and Automation User Setup with Ansible&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#ssh-hardening-and-automation-user-setup-with-ansible&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;Here&amp;rsquo;s a little post about how I do SSH hardening for my RHEL9 homelab and how I ensure that the Ansible automation user is properly set. The playbook stems from an incident I had in Red Hat Insights where it was reported that I had an SSH configuration that allowed legacy ciphers. It was also adviced to create a crypto policy that disables weak algorithms.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Setting up BIND9 for Internal DNS on RHEL9</title>
      <link>https://blog.nousiainen.xyz/docs/bind9-internal-setup-guide/</link>
      <pubDate>Thu, 03 Jul 2025 20:00:00 +0300</pubDate>
      <guid>https://blog.nousiainen.xyz/docs/bind9-internal-setup-guide/</guid>
      <description>&lt;h1 id=&#34;setting-up-bind9-for-internal-dns-on-rhel9&#34;&gt;&#xA;  Setting up BIND9 for Internal DNS on RHEL9&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#setting-up-bind9-for-internal-dns-on-rhel9&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;This guide covers setting up BIND9/named for internal reverse/forward DNS resolution on a RHEL9 server. Unlike public authoritative DNS servers, internal DNS servers provide recursive resolution for your internal network and handle local domain queries.&lt;/p&gt;&#xA;&lt;p&gt;All IP addresses, network ranges, and hostnames in this guide are examples. Replace them with your actual values.&lt;/p&gt;&#xA;&lt;p&gt;For the entirety of the guide we&amp;rsquo;ll be running every single command as root.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Setting up BIND9 for Public DNS on RHEL9</title>
      <link>https://blog.nousiainen.xyz/docs/bind9-external-setup-guide/</link>
      <pubDate>Thu, 03 Jul 2025 18:00:00 +0300</pubDate>
      <guid>https://blog.nousiainen.xyz/docs/bind9-external-setup-guide/</guid>
      <description>&lt;h1 id=&#34;setting-up-bind9-for-public-dns-on-rhel9&#34;&gt;&#xA;  Setting up BIND9 for Public DNS on RHEL9&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#setting-up-bind9-for-public-dns-on-rhel9&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;This guide covers setting up BIND9/named as an authoritative public DNS server on RHEL9. Unlike internal DNS servers that provide recursive resolution, public authoritative DNS servers are responsible for answering queries about domains you own and control.&lt;/p&gt;&#xA;&lt;p&gt;This setup includes security hardening measures such as proper logging and zone transfer restrictions to protect your DNS infrastructure from abuse.&lt;/p&gt;&#xA;&lt;p&gt;All IP addresses, domain names, and server configurations in this guide are examples. Replace them with your actual values.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Installing Red Hat Identity Management (IPA) without DNS on RHEL9</title>
      <link>https://blog.nousiainen.xyz/docs/redhat-idm-install-guide/</link>
      <pubDate>Thu, 03 Jul 2025 16:00:00 +0300</pubDate>
      <guid>https://blog.nousiainen.xyz/docs/redhat-idm-install-guide/</guid>
      <description>&lt;h1 id=&#34;installing-red-hat-identity-management-ipa-without-dns-on-rhel9&#34;&gt;&#xA;  Installing Red Hat Identity Management (IPA) without DNS on RHEL9&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#installing-red-hat-identity-management-ipa-without-dns-on-rhel9&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;Red Hat Identity Management (IdM) provides centralized authentication, authorization, and account information by storing data about users, groups, hosts, and other objects necessary to manage the security aspects of a network of computers. This guide covers installing IdM/IPA server without the integrated DNS service on RHEL9.&lt;/p&gt;&#xA;&lt;p&gt;This guide demonstrates setting up a high-availability IPA deployment with two servers:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Automated KVM VM Provisioning with Ansible and OSBuild on RHEL9</title>
      <link>https://blog.nousiainen.xyz/docs/automated-vm-provisioning-with-ansible-and-osbuild/</link>
      <pubDate>Thu, 03 Jul 2025 14:00:00 +0300</pubDate>
      <guid>https://blog.nousiainen.xyz/docs/automated-vm-provisioning-with-ansible-and-osbuild/</guid>
      <description>&lt;h1 id=&#34;automated-kvm-vm-provisioning-with-ansible-and-osbuild-on-rhel9&#34;&gt;&#xA;  Automated KVM VM Provisioning with Ansible and OSBuild on RHEL9&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#automated-kvm-vm-provisioning-with-ansible-and-osbuild-on-rhel9&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;h2 id=&#34;introduction&#34;&gt;&#xA;  Introduction&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#introduction&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;When I started looking into automating my homelab VM provisioning, I was surprised by the lack of examples combining Ansible with OSBuild for KVM environments. Not many tutorials focus on KVM, so I wanted something that used Red Hat&amp;rsquo;s tooling - as I run a RHEL homelab.&lt;/p&gt;&#xA;&lt;p&gt;I used to provision my homelab virtual machines by hand and eventually I got tired of doing it since I like to tinker around a lot and constantly add new VMs. So, I decided to automate the process using the combination of Ansible and OSBuild.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Enable EPEL Repository on RHEL9</title>
      <link>https://blog.nousiainen.xyz/docs/epel/</link>
      <pubDate>Tue, 03 Jun 2025 17:53:34 +0300</pubDate>
      <guid>https://blog.nousiainen.xyz/docs/epel/</guid>
      <description>&lt;h1 id=&#34;enable-epel-repository-on-rhel-9&#34;&gt;&#xA;  Enable EPEL Repository on RHEL 9&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#enable-epel-repository-on-rhel-9&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;The EPEL repository provides packages that are not included in the standard RHEL repositories, such as &lt;code&gt;htop&lt;/code&gt; and &lt;code&gt;vim&lt;/code&gt; for example.&lt;/p&gt;&#xA;&lt;h2 id=&#34;prerequisites&#34;&gt;&#xA;  Prerequisites&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#prerequisites&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Before installing EPEL, you need to enable the CodeReady Builder repository, which provides dependencies for many EPEL packages.&lt;/p&gt;&#xA;&lt;h2 id=&#34;installation-steps&#34;&gt;&#xA;  Installation Steps&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#installation-steps&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;h3 id=&#34;enable-codeready-builder-repository&#34;&gt;&#xA;  Enable codeready builder repository&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#enable-codeready-builder-repository&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h3&gt;&#xA;&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;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;subscription-manager repos --enable codeready-builder-for-rhel-9-&lt;span style=&#34;color:#66d9ef&#34;&gt;$(&lt;/span&gt;arch&lt;span style=&#34;color:#66d9ef&#34;&gt;)&lt;/span&gt;-rpms&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id=&#34;install-epel-release&#34;&gt;&#xA;  Install epel-release&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#install-epel-release&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h3&gt;&#xA;&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;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-shell&#34; data-lang=&#34;shell&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2 id=&#34;verification&#34;&gt;&#xA;  Verification&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#verification&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;After installation, you can verify that EPEL is enabled by listing available repositories:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
