<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ssh on Pi Stack</title><link>https://www.pistack.xyz/tags/ssh/</link><description>Recent content in Ssh on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 16 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/ssh/index.xml" rel="self" type="application/rss+xml"/><item><title>Self-Hosted SSH Bastion Host &amp; Jump Server Guide: Teleport, Guacamole, Trisail 2026</title><link>https://www.pistack.xyz/posts/self-hosted-ssh-bastion-jump-server-teleport-guacamole-trysail-guide-2026/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/self-hosted-ssh-bastion-jump-server-teleport-guacamole-trysail-guide-2026/</guid><description>&lt;h2 id="why-self-host-an-ssh-bastion-host">Why Self-Host an SSH Bastion Host?&lt;/h2>
&lt;p>Every homelab, small team, and distributed infrastructure faces the same problem: you have dozens of servers, VMs, and containers spread across clouds and local networks, and you need secure, audited access to all of them. Opening SSH port 22 on every machine is a security nightmare. Managing individual SSH keys across a growing fleet becomes unsustainable. And when someone leaves the team, you&amp;rsquo;re manually revoking keys on every server.&lt;/p></description></item></channel></rss>