On Mon, May 31, 1999 at 11:25:49AM -0700, you [Harry Putnam] claimed:
>
> ssh -l reader -L 119:host.machine3:119 host.machine2
At this point you have established a normal shell connection to machine2.
As a side effect, you have a secure nntp tunnel for your news traffic. If
you now configure your news reader at machine1 to connect localhost port
119 (or machine1, port 119 for that matter) ssh will forward the
connection through encrypted channel all the way down to machine2, and
through non-encrypted channel from machine2 to machine3. This is
completely transparent to both the news reader and the news server.
> This does bring up password authentication and login on machine2, but
> once logged in what to do? It looks just like a normal login.
If you don't need the shell prompt, (assuming your finish reading your
news within 50 days) you may do
ssh -l reader -L 119:host.machine3:119 host.machine2 sleep 50d
This keeps the secure nntp forwarding channel open while executing a
dull command.
> Setting the hosts the other way:
>
> ssh -l reader -L 119:host.machine2:119 host.machine3
>
> produces the error message:
> "Sorry you are not allowed to connect"
This attempts to connect machine3 and forward connection through it to
machine2, which -- AFAIU -- is not what you want.
> But neither way says anything about the home machine I'm running this
> from. I want to get the nntp output from machine 3 to machine 1.
After executing the ssh -L... command, you can see the server output this
way:
telnet localhost 119
This is useful for debugging whether the secure channel has been correctly
established.
Hope this helps,
-- v --
[EMAIL PROTECTED]
