<?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>Forensics on Kartik Sankhla</title>
    <link>https://kartiksankhla.com/tags/forensics/</link>
    <description>Recent content in Forensics on Kartik Sankhla</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 30 May 2026 00:05:00 +0530</lastBuildDate>
    <atom:link href="https://kartiksankhla.com/tags/forensics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A court-admissible FAT32 investigation, byte by byte</title>
      <link>https://kartiksankhla.com/posts/court-admissible-fat32/</link>
      <pubDate>Sat, 30 May 2026 00:05:00 +0530</pubDate>
      <guid>https://kartiksankhla.com/posts/court-admissible-fat32/</guid>
      <description>A FAT32 USB image examined the way a court requires — no GUI shortcuts, every claim tied to raw bytes: recovering a deleted JPEG, and catching four files wearing the wrong extension.</description>
    </item>
    <item>
      <title>The file we couldn&#39;t recover: an ext3 deleted-file investigation</title>
      <link>https://kartiksankhla.com/posts/the-file-we-couldnt-recover/</link>
      <pubDate>Sat, 30 May 2026 00:05:00 +0530</pubDate>
      <guid>https://kartiksankhla.com/posts/the-file-we-couldnt-recover/</guid>
      <description>A user created five files and deleted some. Recovering them from an ext3 image meant Trash artifacts, orphan inodes full of GNOME metadata — and proving why one file was gone for good.</description>
    </item>
  </channel>
</rss>
