<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nfs on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/nfs/</link>
    <description>Recent content in Nfs on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 25 Oct 2026 10:55:15 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/nfs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Detect and Fix a Silent NFS Export Leak on a Home NAS</title>
      <link>https://linuxeries.org/post/2026-10-25-how-to-detect-and-fix-a-silent-nfs-export-lea/</link>
      <pubDate>Sun, 25 Oct 2026 10:55:15 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-10-25-how-to-detect-and-fix-a-silent-nfs-export-lea/</guid>
      <description>&lt;h2 id=&#34;silent-nfs-export-leaks-on-home-nas&#34;&gt;Silent NFS Export Leaks on Home NAS&lt;/h2&gt;&#xA;&lt;p&gt;Running a lightweight NFS server on a Raspberry Pi or a small Ubuntu Server is a common way to share media or backups.&lt;br&gt;&#xA;The problem? A mis‑configured export table can let a client mount a directory that was never meant to be exposed. The server happily replies “yes”, so the admin might not notice until a log entry pops up or a backup job starts to fail.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
