<?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>Harness on sigprobe</title><link>https://personal-blog-1jz.pages.dev/tags/harness/</link><description>Recent content in Harness on sigprobe</description><image><title>sigprobe</title><url>https://personal-blog-1jz.pages.dev/og.png</url><link>https://personal-blog-1jz.pages.dev/og.png</link></image><generator>Hugo</generator><language>en-us</language><copyright>2026 Matt</copyright><lastBuildDate>Wed, 19 Aug 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://personal-blog-1jz.pages.dev/tags/harness/index.xml" rel="self" type="application/rss+xml"/><item><title>Fuzzing an MQTT broker with AFL++ persistent mode and a state-aware harness</title><link>https://personal-blog-1jz.pages.dev/writeups/placeholder-fuzzing-writeup/</link><pubDate>Wed, 19 Aug 2026 09:00:00 +0000</pubDate><guid>https://personal-blog-1jz.pages.dev/writeups/placeholder-fuzzing-writeup/</guid><description>Naive packet fuzzing never got past CONNECT. Building a harness that drives a real session, keeps state between messages, and runs fast enough in persistent mode to find three crashes in a week.</description></item><item><title>From harness to crash triage: fuzzing a Zigbee frame parser</title><link>https://personal-blog-1jz.pages.dev/writeups/placeholder-zigbee-frame-fuzzing/</link><pubDate>Thu, 12 Feb 2026 09:00:00 +0000</pubDate><guid>https://personal-blog-1jz.pages.dev/writeups/placeholder-zigbee-frame-fuzzing/</guid><description>The full loop on a small parser: isolating the frame-handling code from the radio stack, writing the harness, and turning forty raw crashes into three distinct root causes.</description></item></channel></rss>