Tcl - Send command (X-server insecure) issues..

Author

Send command (X-server insecure) issues..

Shaun Deacon

2005-02-22, 9:00 pm

Hi,

I'm attempting to send commands between
two tcl/tk apps using the 'send' command.

However, I get the 'X-server insecure' error
even though my server is configured for
xauth-style authorization - This applies to
both a solaris box running a CDE desktop
and a RedHat linux box with a KDE desktop.

Unfortunately, I don't have root permissions
for either box...IT has tried various things
to get this working for me, but to no avail
(I can try to provide details if this helps)

Does anyone have any tips or suggestions
as to how I might find the source of the
problem ?

One idea is that it concerns permissions on
certain ports - is this possibly the case,
or totally a red herring ?

Any ideas would be most appreciated

cheers
Shau

David N. Welton

2005-02-22, 9:00 pm

"Shaun Deacon" <sdeacon@fma.fujitsu.com> writes:

> Any ideas would be most appreciated

One 'any idea' might be to use the comm package in tcllib. It has the
added benefit that it's cross platform.

--
David N. Welton
- http://www.dedasys.com/davidw/

Apache, Linux, Tcl Consulting
- http://www.dedasys.com/

Jeff Hobbs

2005-02-22, 9:00 pm

Shaun Deacon wrote:
> I'm attempting to send commands between
> two tcl/tk apps using the 'send' command.
>
> However, I get the 'X-server insecure' error
> even though my server is configured for
> xauth-style authorization - This applies to
> both a solaris box running a CDE desktop
> and a RedHat linux box with a KDE desktop.
>
> Unfortunately, I don't have root permissions
> for either box...IT has tried various things
> to get this working for me, but to no avail
> (I can try to provide details if this helps)

Root permissions are not necessary, if you are logged into
both boxes at the console. There are a few pointers here:
http://www.tcl.tk/man/tcl8.4/TkCmd/send.htm
as well as the fact that you can always copy over the magic
cookie (mmmmmm, cookies) to get access.

--
Jeff Hobbs, The Tcl Guy
http://www.ActiveState.com/, a division of Sophos

Shaun Deacon

2005-02-22, 9:00 pm

Unfortunately the man page gives no additional clues...
The IT guys and I have covered this carefully.

Furthermore, I have also tried to re-compile Tk with the
authorization checks disabled (-DTK_NO_SECURITY).
This also generates the same error (???) which I find a
little bit suspect...

I guess I'm hoping there may be an X guru here who may
have had similar problems - or can point me in the right
direction ?

cheers
Shaun

Shaun Deacon

2005-02-22, 9:00 pm

Thanks for the pointer...I actually only require communication
between LINUX/UNIX apps so wasn't particularly concerned
about cross-platform operation. 'Send' seemed to be the
easiest mechanism to achieve my goals.

However, if I am unable to sort out my send issues I will investigate
the comm package as you suggest.

cheers
Shaun

Donald Arseneau

2005-02-23, 3:59 am

"Shaun Deacon" <sdeacon@fma.fujitsu.com> writes:

> However, I get the 'X-server insecure' error
> even though my server is configured for
> xauth-style authorization

Check that your X client connection treats the server
as "trusted". (I can't remember the error messages,
so it is probably irrelevant, but it bit me recently.
If your X goes through an ssh tunnel, try ssh -Y.)

--
Donald Arseneau asnd@triumf.ca

Andreas Leitgeb

2005-02-23, 8:59 am

Shaun Deacon <sdeacon@fma.fujitsu.com> wrote:
> However, I get the 'X-server insecure' error
> even though my server is configured for
> xauth-style authorization -

It's not enough that *some* clients use the
xauth-style authorization.

If you type: "xhost" (without arguments), then it should print:

access control enabled, only authorized clients can connect

and *not* list *any* hosts (not even hosts unrelated to the
tk-app, nor localhost nor hostnames of the maschine itself).

In most cases this should be it.

Shaun Deacon

2005-02-23, 4:01 pm

Andreas Leitgeb wrote:
> It's not enough that *some* clients use the
> xauth-style authorization.
>
> If you type: "xhost" (without arguments), then it should print:
>
> access control enabled, only authorized clients can connect
>
> and *not* list *any* hosts (not even hosts unrelated to the
> tk-app, nor localhost nor hostnames of the maschine itself).
>
> In most cases this should be it.

Ah yes...that was it.

After checking carefully, It turned out that I have an old xterm
script that was re-adding a remote host name to the xhost list.

Thanks, everyone, for your help
Shaun

Sponsored Links