<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Linux on VisorCraft News</title><link>https://www.visorcraft.com/news/tags/linux/</link><description>Recent content in Linux on VisorCraft News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 02 Aug 2026 09:30:00 -0500</lastBuildDate><atom:link href="https://www.visorcraft.com/news/tags/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>A Database Client With SSH Tunneling Built In, and Why the Bastion Should Be a Dropdown</title><link>https://www.visorcraft.com/news/2026/08/database-client-with-ssh-tunnel/</link><pubDate>Sun, 02 Aug 2026 09:30:00 -0500</pubDate><guid>https://www.visorcraft.com/news/2026/08/database-client-with-ssh-tunnel/</guid><description>&lt;p&gt;If you work with real infrastructure for more than a month, every database you care about ends up behind a bastion host, because nobody with their name on the firewall rules exposes 5432 to the internet, and yet the default workflow for reaching that database from a desktop GUI is still a ritual from 2005: open a terminal, type an &lt;code&gt;ssh -L&lt;/code&gt; incantation you half-remember, leave the terminal open forever, point your database client at &lt;code&gt;localhost:15432&lt;/code&gt;, and hope nobody reboots the jump box mid-join.&lt;/p&gt;</description></item></channel></rss>