<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Raspberry-Pi on Linux Security</title><link>https://linuxtransfer.com/tags/raspberry-pi/</link><description>Recent content in Raspberry-Pi on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 20 Nov 2026 10:47:36 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/raspberry-pi/index.xml" rel="self" type="application/rss+xml"/><item><title>Resolve DNS Cache Poisoning on Raspberry Pi with resolvectl – One‑Step Fix</title><link>https://linuxtransfer.com/post/2026-11-20-resolve-dns-cache-poisoning-on-raspberry-pi-w/</link><pubDate>Fri, 20 Nov 2026 10:47:36 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-11-20-resolve-dns-cache-poisoning-on-raspberry-pi-w/</guid><description>&lt;p&gt;DNS cache poisoning is a classic attack that can redirect traffic from a legitimate domain to a malicious IP. On a Raspberry Pi running a recent Debian‑based OS (e.g., Raspberry Pi OS 2026‑stable), the default resolver is &lt;strong&gt;systemd‑resolved&lt;/strong&gt;, which exposes the &lt;code&gt;resolvectl&lt;/code&gt; command. This guide shows how to harden that resolver in a single, repeatable step, with practical examples, caveats, and troubleshooting tips.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id="why-the-pi-is-a-target"&gt;Why the Pi is a Target&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Low‑cost, always‑on devices&lt;/strong&gt; are often used as home routers, media servers, or IoT gateways.&lt;/li&gt;
&lt;li&gt;Many users leave the default DNS settings unchanged, pointing to public resolvers (Google, Cloudflare, ISP).&lt;/li&gt;
&lt;li&gt;A compromised Pi can become a pivot point for lateral movement or a source of DNS‑based exfiltration.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Hardening the resolver is a low‑effort, high‑impact measure.&lt;/p&gt;</description></item></channel></rss>