Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Focus-Linux
[Top] [All Lists]

Re: Reverse SSH tunelling

Subject: Re: Reverse SSH tunelling
Date: Sat, 28 Aug 2004 08:26:53 +0100

Raistlin Majere wrote:

      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 .. 

If you have root on the remote systems, I would suggest using a real
VPN rather than the sort of ad-hoc mechanisms which others have
suggested. The choice of exactly which VPN is likely to be determined
by what you can get through the firewall; e.g. if it only allows TCP,
then you will be limited to a PPP/SLIP-over-SSH/SSL type VPN.

-- 
Glynn Clements <glynn.clements@virgin.net>

<Prev in Thread] Current Thread [Next in Thread>