<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kinwilder · Code anatomy</title><link>https://kinwilder.com/</link><description>Cybersecurity, decoded. AI-assisted analysis with primary sources.</description><language>en</language><atom:link href="https://kinwilder.com/feeds/code.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Sun, 25 Oct 2026 06:11:10 GMT</lastBuildDate><item><title>OpenSSH’s three-line equality loop and the limits of timing safety</title><link>https://kinwilder.com/read/openssh-timingsafe-bcmp-aa18063-equality-boundary-2026-10-25</link><guid isPermaLink="true">https://kinwilder.com/read/openssh-timingsafe-bcmp-aa18063-equality-boundary-2026-10-25</guid><pubDate>Sun, 25 Oct 2026 06:11:10 GMT</pubDate><description>An analysis of what a comparison accumulator proves, what compilation can change, and which assumptions its caller must preserve.</description><category>Code anatomy</category></item><item><title>The flag that outlived the data.</title><link>https://kinwilder.com/read/dirty-pipe-the-flag-that-outlived-the-data</link><guid isPermaLink="true">https://kinwilder.com/read/dirty-pipe-the-flag-that-outlived-the-data</guid><pubDate>Sat, 24 Oct 2026 17:27:26 GMT</pubDate><description>Three lines from Dirty Pipe’s original exploit PoC drain a pipe. A live bit-level model shows why security-relevant state can survive—and how initialization breaks the chain.</description><category>Incident anatomy</category></item><item><title>Why Linux hides a number from its compiler.</title><link>https://kinwilder.com/read/linux-why-hide-an-index-from-the-compiler</link><guid isPermaLink="true">https://kinwilder.com/read/linux-why-hide-an-index-from-the-compiler</guid><pubDate>Sat, 24 Oct 2026 16:13:12 GMT</pubDate><description>Three lines connect compiler proofs, transient execution, and a security assumption ordinary bounds checks cannot express. Read the mask—and the limits of the mask.</description><category>Code &amp; binaries</category></item><item><title>When a security verdict needs a third value.</title><link>https://kinwilder.com/read/pyrit-the-security-verdict-that-needs-three-values</link><guid isPermaLink="true">https://kinwilder.com/read/pyrit-the-security-verdict-that-needs-three-values</guid><pubDate>Sat, 24 Oct 2026 16:13:12 GMT</pubDate><description>A five-line Microsoft PyRIT helper preserves “undetermined.” The hard part is keeping that meaning intact all the way to a release decision.</description><category>AI security</category></item><item><title>The same loader. A different authority.</title><link>https://kinwilder.com/read/nist-juliet-same-loader-different-authority</link><guid isPermaLink="true">https://kinwilder.com/read/nist-juliet-same-loader-different-authority</guid><pubDate>Sat, 24 Oct 2026 16:13:12 GMT</pubDate><description>Inside a public NIST/NSA training case, the loader call barely changes. The security decision lives upstream—in who gets to choose the code.</description><category>Code &amp; binaries</category></item><item><title>When test data became a build step.</title><link>https://kinwilder.com/read/xz-when-test-data-became-a-build-step</link><guid isPermaLink="true">https://kinwilder.com/read/xz-when-test-data-became-a-build-step</guid><pubDate>Sat, 24 Oct 2026 05:00:00 GMT</pubDate><description>An exact fragment of the compromised XZ release macro, an inspectable byte-level model, and the boundary where build data became instructions.</description><category>Incident anatomy</category></item><item><title>Memory safe. Boundary broken.</title><link>https://kinwilder.com/read/rust-the-boundary-is-the-bug</link><guid isPermaLink="true">https://kinwilder.com/read/rust-the-boundary-is-the-bug</guid><pubDate>Sat, 24 Oct 2026 05:00:00 GMT</pubDate><description>Three innocent lines in a Rust archive library explain why memory safety is only the beginning of a security argument.</description><category>Rust &amp; systems</category></item><item><title>Two parsers. One very bad assumption.</title><link>https://kinwilder.com/read/rust-windows-two-parsers-one-argument</link><guid isPermaLink="true">https://kinwilder.com/read/rust-windows-two-parsers-one-argument</guid><pubDate>Sat, 24 Oct 2026 05:00:00 GMT</pubDate><description>Rust’s Windows batch-file advisory shows why “passed as an argument” is not a universal property of a string.</description><category>Rust &amp; systems</category></item><item><title>The bit that fell off.</title><link>https://kinwilder.com/read/the-bit-that-fell-off</link><guid isPermaLink="true">https://kinwilder.com/read/the-bit-that-fell-off</guid><pubDate>Sat, 24 Oct 2026 05:00:00 GMT</pubDate><description>From an eight-bit sum to a C allocation: how arithmetic quietly changes the size of a security boundary.</description><category>Code &amp; binaries</category></item></channel></rss>
