<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Remote-Shell on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/remote-shell/</link>
    <description>Recent content in Remote-Shell on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 16 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/remote-shell/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Remote Shell: Mosh vs Eternal Terminal vs OpenSSH with tmux</title>
      <link>https://www.pistack.xyz/posts/2026-06-16-remote-shell-mosh-eternal-terminal-ssh-tmux/</link>
      <pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-16-remote-shell-mosh-eternal-terminal-ssh-tmux/</guid>
      <description>&lt;p&gt;Remote server access is the daily bread of system administrators, DevOps engineers, and backend developers. While OpenSSH has been the gold standard for secure remote access since 1999, its design assumes reliable, low-latency connections — an assumption that breaks down over WiFi, mobile networks, and intercontinental links. Two open-source tools have emerged to solve this problem: Mosh (Mobile Shell) and Eternal Terminal (ET). This article compares them against the classic OpenSSH + tmux combination to help you choose the right remote access strategy.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
