1 Oct
2023
1 Oct
'23
9:05 p.m.
On Sep 30, 2023, at 12:50 PM, Johnny Billquist
<bqt(a)softjar.se> wrote:
Hi.
On 2023-09-30 17:59, Wilm Boerhout wrote:
It's annoyingly incomplete. The protocol code is able to send a proxy request, but
only if a flag in the node database enables it. I think that matches what RSX does, at
least RSX has a node parameter "outgoing proxy". But while there is code to act
on that flag if it's set, there isn't any code in NCP/NML to manipulate that flag.
Oops.
I should see about enabling that.
paul
Thanks Johnny! Sign me up for the updates mail
please. It really simplifies my update scripts.
This address?
VMS and pyDECnet updates work as advertised. My
RSTS node (PIRSTS), whether I'm using COPY or NFT to execute your "grab"
instruction 😊always result in access failure:
PIRSTS::[1,2]$ copy mim::hecnet:fix.rst *
Node: MIM
User:
Password:
System Password:
?NFT -- Connection rejected to node MIM
?NFT -- Access not permitted
It may be some misconfiguration at my end, but my local inter-node DECnet copies work
fine from and to RSTS
The problem is that RSX do not have the concept of a default network account. Instead you
always have to provide this. To help things out a bit, there is something called proxy
access in DECnet, and I've set it up so that if people access MIM without any account
information, I use proxy to get them under a default account. However, this only works if
the outgoing node have enabled proxy. And I don't know if RSTS/E supports the concept
of proxy access.