tunneling through stdin/stdout, source routing
Simon.Richter at hogyros.de
Sat Nov 18 10:42:25 EST 2006
David Woodhouse wrote:
>> That's why I'd think a client-only solution would be the best solution
>> here. My client can always ask for a port forward, the server doesn't
>> care where it comes from.
> If you also use multiple _clients_ then you still have the problem of
> needing it compiled and installed for all machines.
Sure, but in general I have more control over the client than I have
over the machines in the DMZ at my university. In another setup I'd like
to be able to give people access to machines inside the internal network
without giving them a working shell in the passwd. If I require them to
run a command in order to hop to the next host I need to do that.
My point is that there is an use case for the feature I'm suggesting;
availability of only slightly less annoying ways to implement that does
not invalidate my use case.
I'd even be interested in contributing code, however I'm not sure on how
to do that in this case.
More information about the openssh-unix-dev