The problem is that Paul's code don't actually know how proxy works.
I've just given him that information, so he might add the capability now.
Johnny
On 2020-05-01 16:26, Keith Halewood wrote:
Hi Bob,
The specific problem is when you've removed the default account associated with
objects like NML and rely instead on proxies to supply default information and thereby
limit those hosts that have default access to your objects.
So, I've removed the default account associated with NML (and one or two others) and
my participating VAXen have a series of proxies defined by authorize like:
(on DUNE) ADD/PROXY IX::* DECNET/DEFAULT
(on IX) ADD/PROXY DUNE::* DECNET/DEFAULT
The above works fine between those two and the other hosts in my network.
I added Paul's mapper userID as a proxy from a range of his hosts. The login
subsequently fails.
Keith
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of
Robert Armstrong
Sent: 01 May 2020 15:20
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] Proxy to VMS?
On VMS, how can you set up a network object to
allow access without a
password?
The short answer is - when you go thru the NETCONFIG dialog, there are a series of
questions about "do you want a default DECnet account" and "do you want
default access to the xxx object?", where NML is one of the objects listed. You have
to answer YES to those questions.
If you do this, what is required in the connect
request coming in?
No idea, but I have a VMS system and we can see what it does.
Bob
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol