Re: Error: Can't open display: 192.168.21.159:0.0
Re: Error: Can't open display: 192.168.21.159:0.0
- Subject: Re: Error: Can't open display: 192.168.21.159:0.0
- From: Ambrose LI <email@hidden>
- Date: Thu, 9 Dec 2010 22:06:44 -0500
2010/12/9 Jeremy Huddleston <email@hidden>:
>
> It's not really "Apple Policy" so much as common sense. If you set DISPLAY in ~/.bashrc or somewhere else, it's most likely going to be wrong.
>
> Furthermore, people who try to use TCP/IP for X11 connections overwhelmingly open themselves up to security concerns. The attempt to use 'xhost +' proves that. It's not "Apple Policy" that I'm talking about here, it's the X.org community and the security community at large saying "Don't do that." We put in a ton of work to make sure that ssh forwarding "just works" so this kind of thing wouldn't be a problem.
>
> If it's some closed software with their own version of libX11, then they should update. libX11 has had support for the launchd socket for about 3 years now.
The software is obviously running on a Sun, so I would say launchd
support does not have anything to do with what he's experiencing. In
any case, once you log into another host, launchd becomes irrelevant.
I'm not going to debate the merits of making network connections not
work by default in a private network setting. But I'd like to say it
is not useful to automatically say the problems are caused by
assigning DISPLAY / relying on direct network connections / not using
ssh -Y etc.
--
cheers,
-ambrose
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden