<?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>Recon on Akshit Kathuria</title>
    <link>https://ak-debug.github.io/tags/recon/</link>
    <description>Recent content in Recon 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/recon/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Web Recon: Finding Secrets in Source, robots.txt, and Client-Side Storage</title>
      <link>https://ak-debug.github.io/posts/web-recon-finding-client-side-secrets/</link>
      <pubDate>Thu, 12 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://ak-debug.github.io/posts/web-recon-finding-client-side-secrets/</guid>
      <description>Developers keep hiding data in places the browser can read: HTML comments, robots.txt, hidden fields, and local storage. None of it is secret. Here I reassemble a flag split across the page source, a robots.txt disallow entry, and an inspected value, and explain why client-side is never a hiding place.</description>
    </item>
  </channel>
</rss>
