<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Openssh on Lead DevOps</title><link>https://lead-devops.blackdevhub.online/en/tags/openssh/</link><description>Recent content in Openssh on Lead DevOps</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 30 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://lead-devops.blackdevhub.online/en/tags/openssh/index.xml" rel="self" type="application/rss+xml"/><item><title>ssh-connection-manager: a TUI for hosts in ~/.ssh/config</title><link>https://lead-devops.blackdevhub.online/en/posts/ssh-connection-manager/</link><pubDate>Sun, 30 Aug 2026 00:00:00 +0000</pubDate><guid>https://lead-devops.blackdevhub.online/en/posts/ssh-connection-manager/</guid><description>&lt;p&gt;When &lt;code&gt;~/.ssh/config&lt;/code&gt; holds dozens of stands, bastions, and jump hosts, memorizing aliases stops being fun. &lt;strong&gt;ssh-connection-manager&lt;/strong&gt; is a TUI on top of ordinary OpenSSH: a host list, a filter, a connect via the system &lt;code&gt;ssh&lt;/code&gt;, and a way to append a new block to the config.&lt;/p&gt;
&lt;p&gt;The CLI command is &lt;code&gt;ssh-connect&lt;/code&gt;. Repository: &lt;a href="https://gitlab.com/public-projects-docff-devops/ssh-connection-manager"&gt;gitlab.com/unsorted-projects/ssh-connection-manager&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="why-not-another-ssh-client"&gt;Why not another SSH client&lt;/h2&gt;
&lt;p&gt;The client already exists: the system &lt;code&gt;ssh&lt;/code&gt;. What is missing is navigation over the config file.&lt;/p&gt;</description></item></channel></rss>