1 May
2020
1 May
'20
10:05 p.m.
I've looked a bit further and my guess is that Tops-20 doesn't implement
proxies, but this is not definitive.
I am not sure that I have either the latest documentation or sources for
the NICE interface on Tops-20 (sadly, DEC never released the sources for
NMLT20).? I had thought that this was because NMLT20 might have been
written in BLISS and shared, but looking at the executable did not
immediately provide proof.
NMLT20 is communicated with by the NCP sub-mode of the Tops-20 Galaxy
Operator Interface (OPR).? In order to do this, parse tables are
provided and these are in MACRO (NCPTAB.MAC).? None of the keywords
therein match PROXY.
As far as "NCP SET EXEC OUT PROX ENA" is concerned, the only keyword I
can parse after that is TIMER.? This is about the only place in Tops-20
where you configure DECnet. /Except/... To enable NI DECnet in the first
place, you've got to put a few lines in the SYSTEM: config file.? I have
the source for that (SETSPD) and that doesn't parse PROXY, either.
So it doesn't seem as if Tops-20 knows anything about proxies.
------------------------------------------------------------------------
On 5/1/20 11:29 AM, Johnny Billquist wrote:
Do TOPS-20 know about proxy access? Have you enabled outgoing proxy
access?
In RSX and VMS, you do that by
NCP SET EXEC OUT PROX ENA
For people with VMS systems, it probably makes sense to *both* have
the default DECnet user, and to have proxy access enabled. Or at least
the default user. Having only proxy access enabled is a bad idea since
not all other systems knows about proxy. Proxy is nice, in that you
can map different remote users to different local users, in comparison
to the default DECnet account, which is just a catch-all. But both
have their uses...
? Johnny
------------------------------------------------------------------------
On 2020-05-01 17:25, Thomas DeBellis wrote:
It fails from other hosts, too, although I don't know if that would
be relevant.? This is from VENTI2.
NCP>telL DUNE:: shoW exECUTOR chARACTERISTICS
NCP>
11:23:52 ??? NCP
???? ??? Request # 98 Accepted
NCP>
11:23:53 ??? NCP
Request # 98; Show Executor Node Characteristics Failed, Listener
link connect failed,
Link Failure = Access control rejected
NCP>
> ------------------------------------------------------------------------
> On 5/1/20 10:26 AM, 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
> ------------------------------------------------------------------------
> *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
>
>