Quoting "Kenneth E. Lussier" <[EMAIL PROTECTED]>:
> > I've got a question regarding this. What does how you communicate with
> the
> >shell have to do with how the xclient is going to contact the X server?
> It's a
> >completely seperate socket stream going back to the server, so how does
> the fact
> >that your text is being secured affect it?
> While I am certainly not an SSH expert, I'll take a stab at answering this
> one.... Again with the ABC's. Derek has an encrypted tunnel from box A to
> box B. All traffic between the two goes through that tunnel. The connection
> between box B and box C is unencrypted, and on a different stream. So, when
> the X output goes from box C back to box B, it tries to switch streams and
> go through the encrypted tunnel. Since the original packets (the X output)
> are not signed correctly, they are regected by the ssh tunnel because they
As far as I could tell, *IT'S JUST AN SSH SHELL*. There is no tunnel here.
An ssh shell is quite literally no different from a telnet session between two
machines. It's an encrypted stream over IP. From one socket to another..
There is no 'all traffic' involved here..
---
Thomas Charron
<< Wanted: One decent sig >>
<< Preferably litle used >>
<< and stored in garage. ?>>
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
