Re: Reverse SSH tunelling
From: L0stm4n (lostman_at_gmail.com)
Date: Fri, 27 Aug 2004 15:34:50 -0500 To: Raistlin Majere <email@example.com>
Check out this URL:
you could probably combine that with key auth instead of passwords.
And instead of having them always trying to ssh in, you could setup a
file on a webserver and have them parse the file. if they see their
hostname in the file it means they should "call home". just have em
check that file every 5 minutes or so.
On Wed, 25 Aug 2004 22:50:54 -0400, Raistlin Majere <firstname.lastname@example.org> wrote:
> Hi All,
> I need some advice .. I have a situation where about fifty servers will
> be located in fifty sites that cannot allow services to be hosted. These
> servers will be in private network space behind firewalls. I can use
> them to 'scp' files out to a common home base server, but sometimes I
> need to access a command line console on these servers. I am thinking of
> having a hourly cron job ssh out to my home base server and leaving that
> tunnel open so that I can access that console, but am looking for the
> specific way of doing this. Security os pf the utmost concern, so I need
> some sort of encrypted tunnel, hence the thought of ssh, but I don't
> know how to do this 'reverse' tunnel... I was also thinking of a 'free
> swan' vpn tunnel ..