<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Software-Security on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/software-security/</link>
    <description>Recent content in Software-Security on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 16 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/software-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go Fuzzing in 2026: Native testing.F vs go-fuzz vs gofuzz — Which One Actually Finds Bugs?</title>
      <link>https://www.pistack.xyz/posts/2026-11-16-go-fuzzing-native-testing-vs-go-fuzz-vs-gofuzz/</link>
      <pubDate>Mon, 16 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-16-go-fuzzing-native-testing-vs-go-fuzz-vs-gofuzz/</guid>
      <description>&lt;p&gt;Your Go service parses HTTP headers, protobuf payloads, YAML manifests, or images from strangers on the internet. One malformed byte sequence can panic the handler, blow the memory limit, or quietly corrupt a downstream write. Unit tests won&amp;rsquo;t save you — you can&amp;rsquo;t enumerate the inputs you never imagined.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
