<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Support on System Overlord</title><link>https://systemoverlord.com/tags/support.html</link><description>Recent content in Support on System Overlord</description><generator>Hugo</generator><language>en-us</language><managingEditor>david@systemoverlord.com (David Tomaschik)</managingEditor><webMaster>david@systemoverlord.com (David Tomaschik)</webMaster><lastBuildDate>Tue, 20 Sep 2011 15:37:46 +0000</lastBuildDate><atom:link href="https://systemoverlord.com/tags/support/index.xml" rel="self" type="application/rss+xml"/><item><title>Using an SSH Connection to Provide Remote Support (Part I)</title><link>https://systemoverlord.com/2011/09/20/using-an-ssh-connection-to-provide-remote-support-part-i/</link><pubDate>Tue, 20 Sep 2011 15:37:46 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2011/09/20/using-an-ssh-connection-to-provide-remote-support-part-i/</guid><description>&lt;p&gt;
	Last week, at the ALE meeting, a question came up about using SSH to provide remote support for someone who is not especially Linux-literate.  I suggested using an SSH reverse tunnel so the end-user wouldn't need to worry about firewalls, NAT, etc.&lt;/p&gt;
&lt;p&gt;
	Thinking about the problem, I realize that it's a little more complicated than that.  So in part 1, I'm going to discuss the general solution and the approach to the problem.  In Part II, I'll present a more comprehensive solution that will (I think) scale better.&lt;/p&gt;</description></item></channel></rss>