photog.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for your photos and banter. Photog first is our motto Please refer to the site rules before posting.

Administered by:

Server stats:

245
active users

#openssh

2 posts1 participant0 posts today
Marcus Adams<p><a href="https://mastodon.social/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSSH</span></a> in Trixie is being upgraded, which does two important things.</p><p>1) It adds a hybrid post quantum key exchange (screenshot of a verbose login to my server attached).</p><p>2) It disables DSA keys entirely. As in, you can't even manually enable them. They've been disabled "by default" for years, but now they're just straight up removed. If you need to log into an old machine with a DSA key, there is now a separate openssh-client-ssh1 package and ssh1 command.</p><p><a href="https://www.debian.org/releases/trixie/release-notes/issues.en.html#openssh-no-longer-supports-dsa-keys" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">debian.org/releases/trixie/rel</span><span class="invisible">ease-notes/issues.en.html#openssh-no-longer-supports-dsa-keys</span></a></p>
Marcus Adams<p>So it looks like <a href="https://mastodon.social/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSSH</span></a> is getting a new feature to auto-ban users after a number of failed login attempts. This looks like it might even work for public-key auth, which doesn't always get logged in a way that other tools like Fail2Ban can monitor.</p><p>Link: <a href="https://michael-prokop.at/blog/2025/04/13/openssh-penalty-behavior-in-debian-trixie-newintrixie/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">michael-prokop.at/blog/2025/04</span><span class="invisible">/13/openssh-penalty-behavior-in-debian-trixie-newintrixie/</span></a></p>
Le Journal du hacker<p>Bonjour Bignole ! <a href="https://www.journalduhacker.net/s/1cbuvq/bonjour_bignole" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">journalduhacker.net/s/1cbuvq/b</span><span class="invisible">onjour_bignole</span></a> <a href="https://fiat-tux.fr/2025/07/16/bonjour-bignole/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">fiat-tux.fr/2025/07/16/bonjour</span><span class="invisible">-bignole/</span></a> <a href="https://framapiaf.org/tags/application" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>application</span></a> <a href="https://framapiaf.org/tags/openssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openssh</span></a></p>
Richard Chamberlain<p>🛡️ Tired of SSH keys living forever on your servers? 🛡️</p><p>I wrote up a quick, practical guide on how to use OpenSSH Signing CA to create SSH keys that expire.</p><p>Perfect for homelabs, enterprise ops, and anyone who cares about tightening Linux access controls. 🔑 Short-lived certificates 🔑 Simplifies SSH key management 🔑 Reduces risks from lost/stolen devices</p><p>Read here 👉 <a href="https://richard-sebos.github.io/sebostechnology/posts/OpenSSH-Cert-SSH-Keys/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">richard-sebos.github.io/sebost</span><span class="invisible">echnology/posts/OpenSSH-Cert-SSH-Keys/</span></a></p><p><a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://mastodon.social/tags/SSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSH</span></a> <a href="https://mastodon.social/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSSH</span></a> <a href="https://mastodon.social/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Security</span></a> <a href="https://mastodon.social/tags/SysAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SysAdmin</span></a> <a href="https://mastodon.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DevOps</span></a> <a href="https://mastodon.social/tags/Homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Homelab</span></a> <a href="https://mastodon.social/tags/Cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cybersecurity</span></a></p>
🆘Bill Cole 🇺🇦<p><span class="h-card" translate="no"><a href="https://libranet.de/profile/clacke" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>clacke</span></a></span> Yes and no… <br>Instead of the overhead of containers, my 'jump' machines bind specific keys to the ssh commands that do the specifically authorized next hops and (where possible) restrict to specific client IPs. The OS of those machines are only accessible over a VPN or (for some VMs) a tightly secured web interface that has VNC over WebSockets inside a private network to their virtual consoles. </p><p><a href="https://toad.social/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://toad.social/tags/bastion" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bastion</span></a> <a href="https://toad.social/tags/jumphost" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>jumphost</span></a><br><a href="https://toad.social/tags/ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ssh</span></a> <a href="https://toad.social/tags/sshd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sshd</span></a> <a href="https://toad.social/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSSH</span></a></p>
clacke: exhausted pixie dream boy 🇸🇪🇭🇰💙💛<p>When you have an ssh jumphost, the trivial setup is one that conflates OS access and application access.</p><p>The application is ssh, providing the jump to the privileged network, but ssh also allows OS access, potentially allowing privilege escalation within the jumphost.</p><p>Are people taking this seriously and e.g. running an unprivileged sshd inside a container? Access the OS over port 22 to the privileged sshd, restricting that to the segregated admin network, access the jumping over port 2222 and minimize the attack surface on the outer host?</p><p><a href="https://libranet.de/search?tag=infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>infosec</span></a> <a href="https://libranet.de/search?tag=bastion" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bastion</span></a> <a href="https://libranet.de/search?tag=jumphost" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>jumphost</span></a><br><a href="https://libranet.de/search?tag=ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ssh</span></a> <a href="https://libranet.de/search?tag=sshd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sshd</span></a> <a href="https://libranet.de/search?tag=OpenSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSSH</span></a></p>
Zack Weinberg<p>I'm betting the answer here is "this isn't possible" but if anyone knows how to tell OpenSSH that when it's enumerating pubkeys it should check which of the two known authentication dongles is actually plugged into the computer, and only prompt me to unlock the SK key that belongs to that dongle, not both of them, please tell me how.</p><p><a href="https://masto.hackers.town/tags/openssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openssh</span></a> <a href="https://masto.hackers.town/tags/yubikey" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>yubikey</span></a></p>
Soliman Hindy<p>OpenSSH Config Tags How To</p><p><a href="https://mrod.space/2023/09/04/using-tags-in-ssh-config" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mrod.space/2023/09/04/using-ta</span><span class="invisible">gs-in-ssh-config</span></a></p><p>To be honest I did not know tags existed in <a href="https://mastodon.lovetux.net/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSSH</span></a></p>
Schenkl | 🏳️‍🌈🦄<p>Warum genau liegt im Archiv mit dem Quelltext von <a href="https://chaos.social/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSSH</span></a> "openssh-10.0p2.tar.gz" der Quelltext von openssh-10.0p1?</p><p>Meine Pipeline ist auf die Nase gefallen, weil es p2 erwaret aber nur p1 findet...</p><p>Auch die Hashes von p1 und p2 sind gleich...</p><p>689148621a2eaa734497b12bed1c5202 openssh-10.0p1.tar.gz<br>689148621a2eaa734497b12bed1c5202 openssh-10.0p2.tar.gz</p>
scy 🔜 WHY<p>TIL: According to the ssh_config man page, comments in ~/.ssh/config need to be on their own line. In other words,</p><p>Host foo # my awesome host</p><p>is not a valid comment.</p><p>The ssh command seems pretty relaxed about this, but other tools (e.g. Paramiko) are not necessarily.</p><p><a href="https://github.com/paramiko/paramiko/issues/2111" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/paramiko/paramiko/i</span><span class="invisible">ssues/2111</span></a></p><p><a href="https://chaos.social/tags/SSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSH</span></a> <a href="https://chaos.social/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSSH</span></a> <a href="https://chaos.social/tags/Paramiko" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Paramiko</span></a> <a href="https://chaos.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Python</span></a></p>
Marcus Adams<p>If you're on <a href="https://mastodon.social/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debian</span></a> stable but would like a PQ key exchange algorithm on your SSH service, <a href="https://mastodon.social/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSSH</span></a> 10 is available in the Bookworm backports with the following release notes.</p><p><a href="https://mastodon.social/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Security</span></a> <a href="https://mastodon.social/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CyberSecurity</span></a> <a href="https://mastodon.social/tags/Quantum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Quantum</span></a></p>
nixCraft 🐧<p>Multiplexing will boost your SSH connectivity or speed by reusing existing TCP connections to a remote host. Here are commands that you can use to control multiplexing when using OpenSSH server or client on your Linux, macOS, FreeBSD or Unix-like systems. Not sure what SSH multiplexing is? Learn how to set it up and use it to speed up your SSH sessions with our handy guide: <a href="https://www.cyberciti.biz/faq/ssh-multiplexing-control-command-to-check-forward-list-cancel-stop-connections/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">cyberciti.biz/faq/ssh-multiple</span><span class="invisible">xing-control-command-to-check-forward-list-cancel-stop-connections/</span></a></p><p><a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://mastodon.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unix</span></a> <a href="https://mastodon.social/tags/freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freebsd</span></a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> <a href="https://mastodon.social/tags/openssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openssh</span></a> <a href="https://mastodon.social/tags/macos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macos</span></a></p>
r1w1s1<a href="https://snac.bsd.cafe?t=openssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#openssh</a> is the best tool for admin bsd and linux box.<br>
Dendrobatus Azureus<p>An unimportant remnant of the past has been removed from open SSH;<br>DSA.</p><p>Read about it in this article the next article linked will show you that it has been removed finally</p><p><a href="https://mastodon.bsd.cafe/tags/SSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSH</span></a> <a href="https://mastodon.bsd.cafe/tags/openSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openSSH</span></a> <a href="https://mastodon.bsd.cafe/tags/DSA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DSA</span></a> <a href="https://mastodon.bsd.cafe/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programming</span></a> <a href="https://mastodon.bsd.cafe/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>coding</span></a> <a href="https://mastodon.bsd.cafe/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://mastodon.bsd.cafe/tags/openBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openBSD</span></a> <a href="https://mastodon.bsd.cafe/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BSD</span></a> <a href="https://mastodon.bsd.cafe/tags/secureShell" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>secureShell</span></a> <a href="https://mastodon.bsd.cafe/tags/Infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Infosec</span></a> </p><p><a href="https://undeadly.org/cgi?action=article;sid=20240111105900" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">undeadly.org/cgi?action=articl</span><span class="invisible">e;sid=20240111105900</span></a></p>
Peter N. M. Hansteen<p>DSA signature support removed from OpenSSH <a href="https://www.undeadly.org/cgi?action=article;sid=20250507010932" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">undeadly.org/cgi?action=articl</span><span class="invisible">e;sid=20250507010932</span></a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openbsd</span></a> <a href="https://mastodon.social/tags/openssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openssh</span></a> <a href="https://mastodon.social/tags/ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ssh</span></a> <a href="https://mastodon.social/tags/dsa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dsa</span></a> <a href="https://mastodon.social/tags/dsaremoval" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dsaremoval</span></a> <a href="https://mastodon.social/tags/deadkeys" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>deadkeys</span></a> <a href="https://mastodon.social/tags/signature" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>signature</span></a> <a href="https://mastodon.social/tags/deadciphers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>deadciphers</span></a> <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> <a href="https://mastodon.social/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a> <a href="https://mastodon.social/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cryptography</span></a> <a href="https://mastodon.social/tags/crypto" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>crypto</span></a></p>
Peter N. M. Hansteen<p>Call for testing: Last bits of DSA to be removed from OpenSSH <a href="https://www.undeadly.org/cgi?action=article;sid=20250506054255" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">undeadly.org/cgi?action=articl</span><span class="invisible">e;sid=20250506054255</span></a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openbsd</span></a> <a href="https://mastodon.social/tags/openssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openssh</span></a> <a href="https://mastodon.social/tags/ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ssh</span></a> <a href="https://mastodon.social/tags/dsa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dsa</span></a> <a href="https://mastodon.social/tags/dsaremoval" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dsaremoval</span></a> <a href="https://mastodon.social/tags/crypto" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>crypto</span></a> <a href="https://mastodon.social/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cryptography</span></a> <a href="https://mastodon.social/tags/ciphers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ciphers</span></a> <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> <a href="https://mastodon.social/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a> <a href="https://mastodon.social/tags/development" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>development</span></a> <a href="https://mastodon.social/tags/freesoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freesoftware</span></a> <a href="https://mastodon.social/tags/libresoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>libresoftware</span></a></p>
Peter N. M. Hansteen<p>ssh: listener sockets relocated from /tmp to ~/.ssh/agent <a href="https://www.undeadly.org/cgi?action=article;sid=20250506044643" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">undeadly.org/cgi?action=articl</span><span class="invisible">e;sid=20250506044643</span></a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openbsd</span></a> <a href="https://mastodon.social/tags/ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ssh</span></a> <a href="https://mastodon.social/tags/openssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openssh</span></a> <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> <a href="https://mastodon.social/tags/unveil" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unveil</span></a> <a href="https://mastodon.social/tags/sshagent" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sshagent</span></a> <a href="https://mastodon.social/tags/snoopresistant" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>snoopresistant</span></a> <a href="https://mastodon.social/tags/freesoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freesoftware</span></a> <a href="https://mastodon.social/tags/libresoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>libresoftware</span></a></p>
Bryan Steele :flan_beard:<p>A very welcome change in <a href="https://bsd.network/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenBSD</span></a> -current that impacts software which restrict filesystem access with unveil(2), but permit access to /tmp (like web browsers). :flan_thumbs:​</p><p>ssh-agent(1) listener sockets and forwarded sockets in sshd(8) will now be under ~/.ssh/agent instead.</p><blockquote><p>djm@ modified src/usr.bin/ssh/*: Move agent listener sockets from /tmp to under ~/.ssh/agent for both ssh-agent(1) and forwarded sockets in sshd(8).</p><p>This ensures processes (such as Firefox) that have restricted filesystem access that includes /tmp (via unveil(3)) do not have the ability to use keys in an agent.</p><p>Moving the default directory has the consequence that the OS will no longer clean up stale agent sockets, so ssh-agent now gains this<br>ability.</p><p>To support $HOME on NFS, the socket path includes a truncated hash of the hostname. ssh-agent will by default only clean up sockets from the same hostname.</p><p>ssh-agent gains some new flags: -U suppresses the automatic cleanup of stale sockets when it starts. -u forces a cleanup without keeping a running agent, -uu forces a cleanup that ignores the hostname. -T makes ssh-agent put the socket back in /tmp.</p><p>feedback deraadt@ naddy@<br>doitdoitdoit deraadt@</p></blockquote><p><a href="https://bsd.network/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSSH</span></a></p>
Marcus Adams<p>This version will come down the pipe in <a href="https://mastodon.social/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debian</span></a> Trixie later this year. Other distributions may already have it, or should in the near future.</p><p>Headline: <a href="https://mastodon.social/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSSH</span></a> 10.0 Introduces Default Post-Quantum Key Exchange Algorithm - Quantum Computing Report</p><p>Source: <a href="https://quantumcomputingreport.com/openssh-10-0-introduces-default-post-quantum-key-exchange-algorithm/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">quantumcomputingreport.com/ope</span><span class="invisible">nssh-10-0-introduces-default-post-quantum-key-exchange-algorithm/</span></a></p><p><a href="https://mastodon.social/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Security</span></a> <a href="https://mastodon.social/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CyberSecurity</span></a> <a href="https://mastodon.social/tags/Quantum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Quantum</span></a></p>
Daniel Böhmer<p>I never expected this but I’m actually affected by an open bug in <a href="https://ieji.de/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSSH</span></a> what's generally excellent software.</p><p>I want to set a proxy depending on whether there’s a route to some net. There’s no such escape mechanism in exec-clauses though.</p><p>Match host some-host !exec "[ -z \"$( ip route list 192.168.123.0/24 )\" ]"<br> HostName some-alt-host</p><p>My workaround with grep:</p><p>Match some-host !exec "ip route | grep -q ^192.168.123.0/24"<br> HostName some-alt-hostname</p><p><a href="https://bugzilla.mindrot.org/show_bug.cgi?id=3474" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">bugzilla.mindrot.org/show_bug.</span><span class="invisible">cgi?id=3474</span></a></p>