Operating System - OpenVMS
1831349 Members
3057 Online
110024 Solutions
New Discussion

Remote procedure on DecNet V

 
SOLVED
Go to solution
Uwe Zessin
Honored Contributor

Re: Remote procedure on DecNet V

It's my understanding that CONVERT_PROXY copies from NETPROXY.DAT to NET$PROXY.DAT, but does not add PhV-style proxies.
.
Joseph Huber_1
Honored Contributor

Re: Remote procedure on DecNet V


Joseph,
I addes USERNAME="ILLEGAL"
It seems doesn't work


You got the answer about proxies.
Just to make it clear:
The user ILLEGAL (any username not existing in sysuaf) just ensures that no remote user without authorization (explicit with node"user passw":: or node"user":: with proxy , or implicit node:: with Default proxy) can access the object.
Now today where probably Your Decnet is a local net, this is probably no longer as important as in the time of the HEPNET/SPAN "internet": at that time (1987?) my system was hit by the WANK worm, which exploited exactly such open TASK objects.
http://www.mpp.mpg.de/~huber
Michael Yu_3
Valued Contributor

Re: Remote procedure on DecNet V

Hi,

On systems running DECnet phase IV, both net$proxy.dat and netproxy.dat contain proxy information stored using DECnet phase IV node names.

On systems running DECnet/OSI, net$proxy.dat contains proxy information stored using DECnet/OSI full names while netproxy.dat contains proxy information stored using node synonyms.

Thanks and regards.

Michael
Uwe Zessin
Honored Contributor

Re: Remote procedure on DecNet V

NETPROXY.DAT is only present for old code that accesses this file directly. All new code should use the API.
.