At 11:36 AM 1/25/00 -0600, you wrote:
[FFWD]
> 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
are not authorized. There would be an authentication breakdown at this
point, and the display would refuse the connection from the server in the
middle of the transmission. That would cause the X session to shutdown
because it can't see the display. What he is trying to do, essentially, is
inject packets into an encrypted tunnel without encrypting them.
Just a thought,
Kenny
**********************************************************
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
**********************************************************
