Conference bulova::decw_jan-89_to_nov-90

3662.0. "probl. : security and remote displ. on local node" by MUNICH::BENDER (two beer or not two beer...) Wed Nov 14 1990 11:15

Hi,

try the following :

- login on a vms decwindows system as user A,
- customize security : allow access for localnode, user B, transport DECNET
  (or LOCAL),
- create a decterm, do a set host 0 and login as user B,
- type set display/create[/trans=local][/node=localnode]
- start a decwindows application

Probably you will get one of the two error messages :

1. use transport LOCAL in customize security and set display/create :

XIO:  unable to open connection _WSA11:
      after 0 requests (0 known processed) with 0 events remaining.
%XLIB-F-IOERROR, xlib io error
-DECW-E-CNXABORT, connection aborted


2. use transport DECNET in customize security and set display/create

Xlib:  connection to "0::0.0" refused by server
Xlib:  Client is not authorized to access server
X Toolkit Error: Can't Open display
%DWT-F-DWTABORT, xtoolkit fatal error

This two error messages are generated with or without use of /node=localnode
in the set display command

But...
 if you use 0 as nodename in customize security, everything works fine !!

Could someone out there give me an explanation for this behaviour ?

  Thanks a lot, 

      -Andreas 

There is an undocumented restriction that the node name must be '0'
for local connections.

I suggest you QAR this problem so I don't forget to fix it.

    Thanks for your reply.
    But what about the decnet connection ?  Are there some more
    restrictions ?
    
    Thanks, -Andreas

Um, in this case a 'local' connection is a connection from a client
to a server on the same node, without regards to the transport type.

Unfortunately, we have overloaded the term 'local'.  The LOCAL
transport probably should have been named something like 'Shared
Memory', but we're stuck with the current name.