[Info-vax] Assembly languages

[VAXman- at SendSpamHere.ORG]

In article <t31ose$pr0$1 at dont-email.me>, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:
>On 2022-04-11, VAXman-  @SendSpamHere.ORG <VAXman- at SendSpamHere.ORG> wrote:
>> In article <t318l3$92b$3 at dont-email.me>, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:
>>>On 2022-04-10, Richard Maher <maher_rjSPAMLESS at hotmail.com> wrote:
>>>>
>>>>   Remember when inner-mode code and protected sub-systems were essential.
>>>>
>>>> Happy days.
>>>
>>>From a _security_ point of view, VMS has only ever had one inner mode,
>>>just like other operating systems.
>>>
>>>Once you are in one of the hardware inner modes, you can get to the
>>>others without any additional privileges required on the part of the
>>>account doing it.
>>
>> If that were true, then Joe Noprivuser could go from user mode to kernel mode
>> through a series of steps -- user->supervisor then supervisor->executive then
>> executive->kernel.
>>
>
>Ok, Brian, you win. I'll be pedantic if you wish. :-)
>
>Once you have code you control running in one of the hardware inner modes,
>you can get to the others without any additional privileges required on
>the part of the account doing it.

NOT TRUE.  Stop confusing $CMKRNL from EXEC mode with all others.  You can 
NOT get to EXEC from SUPERVISOR mode.  Granted, you found an exploit with an
installed image but that was corrected.  There's no $CMEXEC jump from SUPER-
VISOR mode without privileges vis-a-vis $CMKRNL from EXEC mode.



>Happy now ? :-)

No, publish such code here to PROVE me wrong.  Otherwise, stop your bullshit.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.