https://dev-journal.hallblazzar.dev/categories/security/ Recent content in Security on Hallblazzar: Dev Journal Hugo en Mon, 05 Oct 2026 00:00:00 +0000 https://dev-journal.hallblazzar.dev/posts/2026_oct_5_metploit3_on_linux/ Mon, 05 Oct 2026 00:00:00 +0000 https://dev-journal.hallblazzar.dev/posts/2026_oct_5_metploit3_on_linux/ <p>TL;DR, If you&rsquo;re trying to run Metasploitable3 on Linux/KVM and AMD CPU, my best advise is: DON&rsquo;T. Switch to Wintel environments—it will save a lot of headaches.</p> <h1 id="background-and-workarounds"> Background and Workarounds <a class="heading-link" href="#background-and-workarounds"> <i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"></i> <span class="sr-only">Link to heading</span> </a> </h1> <p>Many security 101 articles recommend <a href="https://github.com/rapid7/metasploitable3" class="external-link" target="_blank" rel="noopener">Metasploitable3</a> as target machine, but this project is not actively maintained. In a Wintel-based environment, you can still simply boot it through <a href="https://portal.cloud.hashicorp.com/vagrant/discover?query=rapid7%2Fmetasploitable" class="external-link" target="_blank" rel="noopener">Vagrant</a> (even though the link to the Vagrant Registry in its repository is broken). By contrary, in a KVM/QEMU based environment, users must rebuild images by themselves as KVM/QEMU is not officially supported—and building them is practically impossible.</p>