<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>File Handling on Nalar</title>
    <link>https://nalar.dev/tags/file-handling/</link>
    <description>Recent content in File Handling on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/file-handling/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Inspect ZIP Archives Before Extraction in Python</title>
      <link>https://nalar.dev/inspect-zip-archives-before-extraction-in-python/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/inspect-zip-archives-before-extraction-in-python/</guid>
      <description>&lt;p&gt;ZIP extraction looks like a single filesystem operation, but an archive is really a collection of filenames, metadata, and compressed byte streams supplied by whoever created the file. When the archive is untrusted, that metadata belongs at a trust boundary.&lt;/p&gt;&#xA;&lt;p&gt;Python&amp;rsquo;s &lt;code&gt;zipfile&lt;/code&gt; module provides convenient extraction helpers, and those helpers include protections for suspicious path components. The documentation still warns against extracting untrusted archives without prior inspection. That distinction is useful: library normalization is not the same thing as an application-specific acceptance policy.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
