[Info-vax] Listeners in VMS Basic, was: Re: Integrity iLO Configuration?

Arne Vajhøj arne at vajhoej.dk
Thu Jul 1 21:24:47 EDT 2021


On 7/1/2021 9:16 PM, Richard Maher wrote:
> On 1/07/2021 10:06 pm, Arne Vajhøj wrote:
>> On 7/1/2021 12:18 AM, Richard Maher wrote:
>>> And IIRC correctly there is no thread-granularity
>>> T3$PERSONA_ASSUME which allows unprivileged code temporarily assume
>>> the Username of the authorized client.
>>>
>>> Let VMS check authorization and not try to duplicate it.
>>
>> Persona is probably a process attribute not a thread attribute. 
>> Process has P0 and S0 space. Threads just have a slice of P1 space.
>>
>> But I don't think that is an issue here.
> 
> You see no benefit from being able to become the client user so that all 
> security checking for files, print submission, dn trigger audit etc is 
> done as the user?

I don't know the application.

But the picture I got in my head is not that clients are
authenticated as VMS users, the server code switch to that user
and VMS access control is used to control access.

But I could be wrong. If that is the case then multi threaded
is not the way to go.

Arne




More information about the Info-vax mailing list