30 Nov
2023
30 Nov
'23
12:13 a.m.
On 2023-11-29 23:52, John Forecast wrote:
Sounds possible. Maybe used in the same way as in RSTS/E? Because I do
seem to remember that VMS also can have a system password... Unexpected
that it would merge information from the default parameters with
provided parameters. I would have expected it to fully use one or the other.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On Nov 29, 2023, at 5:13 PM, Paul Koning
<paulkoning(a)comcast.net> wrote:
But it still tries to login using the default account information. Probably the ACCOUNT
field is causing problems for loginout.exe. On Nov 29, 2023, at 5:06 PM, John Forecast
<john(a)forecast.name> wrote:
Anyway, I’ve found the problem! sendvmsmail (the program Linux uses to send mail to VMS)
tries really hard to put something in the account field of access control. This seems to
cause login to the nonpriviledged account to fail. I don’t believe I’ve seen any
documentation about this issue. Comment out the logic which fills in the account field and
everything works OK, even the V3 protocol is almost functional.
That seems sensible; the default stuff applies when authentication data isn't
present. "Account" is an obscure authentication field that is only used in some
operating systems, but I can imagine how its presence might make a check for "there
was no authentication data" fail.