13 Sep
2022
13 Sep
'22
5:12 p.m.
The "protection violation" message is a standard RSTS message. It means that
some OS request was made by a program and that request was rejected because it requires
privilege and the program/user does not have that. I don't remember why the OS
requests to query DECnet state require privilege; perhaps because they are the same
request as is used to change state, which obviously needs to, or perhaps because some of
the state is potentially sensitive and being more selective in the access checking
wasn't worth the trouble.
Disallowed anonymous access would show up differently, that would be a connection reject
with reject code 34 (authorization data not valid).
paul
On Sep 13, 2022, at 10:02 AM, Johnny Billquist
<bqt(a)softjar.se> wrote:
Well. I suspect any scraping would get the same effect I saw. On most any other machine
that don't allow anonymous access, you'd see something like:
.ncp tell jocke sho exec
NCP -- Show failed, Listener connect failed, access control rejected
But it might be that RSTS/E gives a result like that when no access. Just not what I
would have expected.
Johnny
On 2022-09-13 14:12, Wilm Boerhout wrote:
> Funny as in "mostly vanilla"?
> Attached is the command output with credentials.
> But having priv access only here should not cause that behavior?
> Wilm
> -----Original Message-----
> From: Johnny Billquist <bqt(a)softjar.se>
> Sent: Tuesday, September 13, 2022 1:55 PM
> To: hecnet(a)lists.dfupdate.se
> Subject: [HECnet] Re: RSTS DECnet config question
> PIRSTS is "funny".
> .ncp tell pirsts sho exec cha
> NCP -- Show failed, operation failure
> ?Protection violation
> Error finding executor state
> .
> Maybe related?
> Johnny