<?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>Protocol Notes</title><link>https://syycorax.xyz/</link><description>Recent content on Protocol Notes</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 20 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://syycorax.xyz/index.xml" rel="self" type="application/rss+xml"/><item><title>Stack Smashing to ROP: What a Return Address Is Worth</title><link>https://syycorax.xyz/posts/stack-smashing-to-rop/</link><pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate><guid>https://syycorax.xyz/posts/stack-smashing-to-rop/</guid><description>How a bounds check failure becomes control of the instruction pointer, what each mitigation blocks, and why ROP still works on a stack that cannot execute.</description></item><item><title>Kerberos: Tickets All the Way Down</title><link>https://syycorax.xyz/posts/kerberos-tickets/</link><pubDate>Tue, 13 Oct 2026 00:00:00 +0000</pubDate><guid>https://syycorax.xyz/posts/kerberos-tickets/</guid><description>What the KDC hands out, why a golden ticket works without touching a domain controller, and which defenses change the economics of the attack.</description></item><item><title>TLS 1.3: The Handshake, Byte by Byte</title><link>https://syycorax.xyz/posts/tls-1-3-handshake/</link><pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate><guid>https://syycorax.xyz/posts/tls-1-3-handshake/</guid><description>A walk through the TLS 1.3 flight, the HKDF key schedule, and the certificate checks that most custom clients get subtly wrong.</description></item><item><title>HTTP Request Smuggling: Two Parsers, One Socket</title><link>https://syycorax.xyz/posts/http-request-smuggling/</link><pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate><guid>https://syycorax.xyz/posts/http-request-smuggling/</guid><description>How a disagreement over Content-Length and Transfer-Encoding turns a keep-alive connection into a request queue that one client can write into.</description></item></channel></rss>