<?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 vxlabs</title>
		<link>https://vxlabs.com/tags/ssh/</link>
		<description>Recent content in Ssh on vxlabs</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 30 May 2026 10:56:27 +0200</lastBuildDate>
		
			<atom:link href="https://vxlabs.com/tags/ssh/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>SSH authorized_keys command restriction to isolate container access to host functions</title>
				<link>https://vxlabs.com/2026/05/30/ssh-command-restriction-container-to-host/</link>
				<pubDate>Sat, 30 May 2026 10:56:27 +0200</pubDate>
				<guid>https://vxlabs.com/2026/05/30/ssh-command-restriction-container-to-host/</guid>
				<description>&lt;h2 id=&#34;preview&#34;&gt;Preview&lt;/h2&gt;&#xA;&lt;p&gt;This post documents how you can use a lesser known &lt;code&gt;authorized_keys&lt;/code&gt; config to give AI agents (or anything else) programmatically designed and limited access to any resources and tools on a different system, for example the system hosting the agent container.&lt;/p&gt;&#xA;&lt;p&gt;See &lt;a href=&#34;https://github.com/cpbotha/ssh-restricted-dispatcher&#34;&gt;the ssh-restricted-dispatcher github repo&lt;/a&gt; for code to set this up yourself.&lt;/p&gt;&#xA;&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;&#xA;&lt;p&gt;I have been experimenting with different AI agent setups on a hobby Linux server at home.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
