Re: running a command back down an ssh tunnel

From: Mark Rafn (dagon_at_dagon.net)
Date: 04/27/05 

Date: Tue, 26 Apr 2005 15:21:18 -0700

ducker <gufrbcqxczd@mailinator.com> wrote:
>The problem isn't that the remote work is untrusted (far from it), the
>problem is allowing them access into our network without amending our
>firewall rules.

If this is a type of work you need to allow, your firewall rules are broken.
Fixing them to allow incoming ssh to the appropriate host(s) is the right
answer. If you don't want to do this due to config maintenance, you REALLY
don't want to maintain the other options.

>I was assuming that connecting to the remote box and allowing a
>connection back down was possible.

It is definitely possible to tunnel in on an outbound connection (machine
inside the net makes an ssh conneciton to outside, and the outside machine
(or world, depeding on options) can then connect in. See the -R option to
OpenSSH or look up "remote port forwarding". 

--
Mark Rafn    dagon@dagon.net    <http://www.dagon.net/>

Relevant Pages

  • VPN connection problem??
    ... I downloaded the connection manager from remote work place and got it ... remotely connected to my sbs2003 server. ...
    (microsoft.public.windows.server.sbs)
  • Re: running a command back down an ssh tunnel
    ... The problem isn't that the remote work is untrusted, ... problem is allowing them access into our network without amending our ... firewall rules. ... I was assuming that connecting to the remote box and allowing a ...
    (comp.security.ssh)