<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fuzzing on Sakura Sky: Cloud, Data, Security</title><link>https://www.sakurasky.com/tags/fuzzing/</link><description>Recent content in Fuzzing on Sakura Sky: Cloud, Data, Security</description><generator>Hugo</generator><language>en-US</language><copyright>Sakura Sky</copyright><lastBuildDate>Mon, 31 Aug 2026 00:00:00 -0400</lastBuildDate><atom:link href="https://www.sakurasky.com/tags/fuzzing/index.xml" rel="self" type="application/rss+xml"/><item><title>GATE v1.5 Roadmap</title><link>https://www.sakurasky.com/blog/gate-roadmap-v1-5/</link><pubDate>Mon, 31 Aug 2026 00:00:00 -0400</pubDate><guid>https://www.sakurasky.com/blog/gate-roadmap-v1-5/</guid><description>&lt;p&gt;The &lt;a href="https://www.sakurasky.com/blog/gate-roadmap-v1-4/"



 


&gt;v1.4 roadmap&lt;/a&gt; named six things: C20 output validation, break-glass formalisation, the OWASP AISVS and MITRE ATLAS mappings, gate-rust, gate-fuzz, and gate-knowledge. Five shipped in full, although C20 shipped with a streaming constraint I come back to below. gate-fuzz shipped one of its three deliverables, the Python-to-Rust differential harness. The bundle-derived strategy generator and the HTTP-level protocol fuzzer moved to v1.5, and the &lt;a href="https://www.sakurasky.com/blog/gate-v1-4-release/"



 


&gt;v1.4 release post&lt;/a&gt; named the deferral on the day. v1.5 delivers them.&lt;/p&gt;</description></item></channel></rss>