<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nmap on Zachary Morgan</title>
    <link>https://zacharymorgan.dev/tags/nmap/</link>
    <description>Recent content in Nmap on Zachary Morgan</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Apr 2026 18:00:00 -0600</lastBuildDate>
    <atom:link href="https://zacharymorgan.dev/tags/nmap/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Day 8 — Local Kali, Nmap, and a Note on the Coming Week</title>
      <link>https://zacharymorgan.dev/posts/day-8-kali-and-nmap/</link>
      <pubDate>Wed, 29 Apr 2026 18:00:00 -0600</pubDate>
      <guid>https://zacharymorgan.dev/posts/day-8-kali-and-nmap/</guid>
      <description>&lt;p&gt;Set up a Kali VM on my main machine today because I could not stand the input lag from running it on the homelab. Connecting to a remote VM over SPICE works, but stack WiFi latency, Tailscale routing, and SPICE on top of each other and you get a generally crappy to use workspace.&lt;/p&gt;&#xA;&lt;p&gt;Used virt-manager on my laptop with KVM as the hypervisor — same stack as Proxmox underneath, so the workflow is familiar. Installed Kali with the GNOME desktop, the default toolset plus the Top 10 metapackage, and added the OSCP-prep tools I&amp;rsquo;ll actually need (Bloodhound, NetExec, Impacket, evil-winrm, Responder, ffuf, gobuster, feroxbuster, SecLists, and a few others). Snapshotted a clean baseline once everything was working.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
