SSL wrapping or SSH tunnelling? Which is more secure?

[Mark Blackman]

I believe '-N' sort of helps. Limited to protocol 2 and keeps
the stdin and stdout mapped to the local terminal.  It supposed
to deal with this problem, but just gives you other ones.

However, like you I just run
a simple sh-loop with a sleep in the middle. i.e.

ssh -n -L 4200:othermachine.net:4200 xxx at othermachine.net "/bin/sh -c 'while (true); do sleep 86400; done'" &

- Mark

> > I use ssh forwarding, just because it's the approach I found first.
> > Never had a problem with it.
> 
> Ou of interest, how do you do the ssh forwarding ? I've not yet found the
> magic combination of arguments to let me set up a permentnet tunnel without
> something running on the far end. At the moment thats a shell script which
> sleeps 10 minutes and then dies. Any alternative suggestions ?
> 
> -bat.
> 
> ------ FreeBSD UK Users' Group  -  Mailing List ------
> http://listserver.uk.freebsd.org/mailman/listinfo/freebsd-users