<?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>Aes on Akshit Kathuria</title>
    <link>https://ak-debug.github.io/tags/aes/</link>
    <description>Recent content in Aes on Akshit Kathuria</description>
    <image>
      <title>Akshit Kathuria</title>
      <url>https://ak-debug.github.io/social-preview.png</url>
      <link>https://ak-debug.github.io/social-preview.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 12 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ak-debug.github.io/tags/aes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>When Symmetric Crypto Goes Wrong: AES Key-as-IV and XOR Mistakes</title>
      <link>https://ak-debug.github.io/posts/symmetric-crypto-misuse-aes-and-xor/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/symmetric-crypto-misuse-aes-and-xor/</guid>
      <description>AES is not broken, but code that uses it often is. Here I explain why reusing the key as the CBC initialisation vector can hand an attacker the key itself, and why home-made XOR ciphers fall to known plaintext and key reuse. Each mistake comes with a working Python demonstration, the correct pattern, and a worked example from the bi0s DD CTF.</description>
    </item>
  </channel>
</rss>
