<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Homenas on Linux Security</title><link>https://linuxtransfer.com/tags/homenas/</link><description>Recent content in Homenas on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 28 Oct 2026 11:11:23 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/homenas/index.xml" rel="self" type="application/rss+xml"/><item><title>Rootless Podman: Running a Home‑NAS Service Without Privilege Escalation</title><link>https://linuxtransfer.com/post/2026-10-28-rootless-podman-running-a-homenas-service-wit/</link><pubDate>Wed, 28 Oct 2026 11:11:23 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-10-28-rootless-podman-running-a-homenas-service-wit/</guid><description>&lt;h3 id="why-rootless-containers-matter-for-a-homenas">Why Rootless Containers Matter for a Home‑NAS&lt;/h3>
&lt;p>When a home‑NAS sits on a single‑user machine, the first instinct is to give the NAS service full root access. That works, but it also opens a door for accidental or malicious privilege escalation. Rootless Podman lets you run containerized services—Nextcloud, Syncthing, or a simple Nginx reverse proxy—inside a user namespace that isolates the container from the host. The container can still read and write to your data directories, but it can’t touch the kernel or system services.&lt;/p></description></item></channel></rss>