Conference bulova::decw_jan-89_to_nov-90

2646.0. "VMS fails to allow ULTRIX access to workstation" by HANNAH::OSMAN (see HANNAH::IGLOO$:[OSMAN]ERIC.VT240) Tue Apr 24 1990 09:53

From my Ultrix node trash1::, with decnet installed, I'm attempting to run
various DECwindows applications, and use my vms node osman:: as the screen,
and it's failing.

My test case is

	dxclock -d osman::0

I'm getting

	Xlib: connection to "osman::0.0" refused by server
	Xlib: Client is not authorized to access server

In customize security on "osman", I've authorized

	Node: trash1
	User: osman
	Transport: decnet

I log in as user osman on both systems.


What's curious is that

	dxterm -d osman::0

works fine !  (But dxclock fails, and my work-in-progress application fails).

I've found a workaround, which is to authorize user "*" instead of just osman,
but obviously this isn't desireable !

Does anyone know what's going on ?  If it should be qared, please tell me
what node/username/database.

By the way, the versions are (at least, what gets printed when I log in to the
Ultrix system):

	ULTRIX T4.0-1 (Rev. 144)
	UWS T4.0-1 (Rev. 108)

	VAX/VMS V5.3-1

Thanks.

/Eric

You may also need to authorize access for your Ultrix (numeric) user id.
The Ultrix command "id" will tell you your id number.

On OSMAN, authorize trash1::<id #>

I'll make that more definite... you definitely need to also authorize
your Ultrix user id.  This is documented in the VMS V5.3 DECwindows
User's guide.  It is not elegant, but it is an Ultrix fact of life.

    
    enable squeaky whiny voice:
    
    	then why does dxterm work, but dxclock doesn't ?
    
    	Perhaps if dxclock did what dxterm did, we wouldn't have to do the
    	id number bit ?
    
    

because dxterm is setuid root.

NO!  If an apllication isn't designed to handle being setuid, then
you will open a large security hole in your system.