Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

OT: Never Leave A Privilleged Session Unattended

Robert Atkinson
Respected Contributor

OT: Never Leave A Privilleged Session Unattended

Used to love leaving this running on the Operators PC's when they disappeared and left the session unlocked.

Never seen someone go so white!

:)
8 REPLIES
Jan van den Ende
Honored Contributor

Re: OT: Never Leave A Privilleged Session Unattended

Robert,

slightly different, but in my early (VMS 3.2) days I had someting similar april for fools day.

It did a DIR, pasted it into a DELETED message.
For the entire SYS$LOGIN directory tree.
Then logged out.

On the next login it displayed:
April 1st -- but do not tell anyone yet.

Pretty soon it was necessary to put the phone OFF the hook at Operations and System Management....

Oh well, those were the days.

Proost.

Have one on me.

jpe


Don't rust yours pelled jacker to fine doll missed aches.
Colin Butcher
Esteemed Contributor

Re: OT: Never Leave A Privilleged Session Unattended

Try embedding an XOFF character into the prompt string :)
Entia non sunt multiplicanda praeter necessitatem (Occam's razor).
RBrown_1
Trusted Contributor

Re: OT: Never Leave A Privilleged Session Unattended

Of course this gag works just as well for non-privileged users. Perhaps better.
John Gillings
Honored Contributor

Re: OT: Never Leave A Privilleged Session Unattended

Back in V1.0 days, a lecturer at my university made the mistake of leaving a terminal open. The only change was to redefine the LOGOUT command to issue a message instead of logging out:

%LOGOUT-E-DISABLED, Logouts are currently disabled, please try again later.

The biggest surprise was he actually believed it! ;-)
A crucible of informative mistakes
John Gillings
Honored Contributor

Re: OT: Never Leave A Privilleged Session Unattended

Robert,

Here's an nastier procedure that closes quite a few loopholes left open by your procedure:

TRICK.COM
$ MACRO/OBJ=FAIL SYS$INPUT
.TITLE FAIL
$RMSDEF
.ENTRY start,^M<>
MOVL #RMS$_FNF,R0
RET
.END start
$ LINK FAIL
$ DEFINE/NOLOG FAIL 'F$SEARCH("FAIL.EXE")'
$ DEFINE/NOLOG DIRECTORY FAIL
$ DEFINE/NOLOG TYPE FAIL
$ DEFINE/NOLOG DELETE FAIL
$ DEFINE/NOLOG SEARCH FAIL
$ DEFINE/NOLOG VMSHELP FAIL
$ SET COMMAND SYS$INPUT
DEFINE VERB LOGOUT
SYNONYM LO
IMAGE FAIL
qualifier brief
qualifier full
qualifier hangup
$ EXIT
A crucible of informative mistakes

Re: OT: Never Leave A Privilleged Session Unattended

John,

I tried compiling and running your little assembler program but I don't think it worked. All I got was

%RMS-E-FNF, file not found

John :)


p.s. anyone remember ZOOP from RSTS days
John Harper
John Gillings
Honored Contributor

Re: OT: Never Leave A Privilleged Session Unattended

re the other John:

Sounds like it works perfectly! The purpose of the little program is to generate exactly that message.

The DEFINE commands will redirect all versions the named commands to run the program which issues the error, so no need to run inside a DCL shell loop, and no need to parse all the possible variants of the commands.

The LOGOUT command is implemented as a CLI routine, so hijacking it requires some CLD.
A crucible of informative mistakes
Bojan Nemec
Honored Contributor

Re: OT: Never Leave A Privilleged Session Unattended

Robert,

For more "damage" the procedure can be upgraded with:

$ RECALL/ERASE

$ dir*ectory=="write sys$error ""%DIRECT-W-NOFILES, no files found""!"
$ EXIT


Taken from an old joke similar to the one mentioned by Jan.

Bojan