On Sun, Jun 16, 2002 at 12:03:39PM -0700, Karsten M. Self wrote: > > This is true. However, I see far too many people advocating "xhost +" > and disabling "-nolisten tcp", when the first attempt should be an "ssh > -X". If this turns out to be too slow for the necessary task (unlikely > for any business/system need), then other options can be explored. And <snip>
On a related note, I am facing a peculiar problem with ssh -X hostname. As mentioned previously on this list, I have edited the file /etc/ssh/ssh_config and /etc/ssh/sshd_config to allow X forwarding, etc. I can ssh from machine 'A' to another machine 'B'; run a X program on 'B' whose window comes properly on 'A'. Then the machine locks up. None of the keys work. I cannot telnet/ssh into 'A' from any other machine on the network. Sometimes even 'B' gets locked up. The lock up occurs only when I try X forwarding, else ssh does not give me any problems. What could be the reason for this weird behaviour? I am currently running woody on my machines. Regards, -- Sridhar M.A. Genius doesn't work on an assembly line basis. You can't simply say, "Today I will be brilliant." -- Kirk, "The Ultimate Computer", stardate 4731.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]