🚀 go-pugleaf

In article <3pchj8$fah@news-s01.ny.us.ibm.net> jtpye@ibm.net writes:
$WARNING if you are using the Console Lock feature of the MONITOR.NLM any
$failed attempt at the password will be taken as an attempt at the SUPERVISOR
$password.
$
$It is recommended that the SUPERVISOR password is not used for the Console
$Lock password because if the SUPERVISOR account is locked you are stuck.

   This won't help in keeping the SUPERVISOR account from being locked
out due to console unlock attempts; I'm not sure if that's what you're
suggesting or not.  Regardless of whether the console lock password is
or is not the same as the SUPERVISOR password, you can end up locking
out the SUPERVISOR account.

   When you supply a password to try to unlock the console, MONITOR first
checks to see if it's the same password you gave when you locked the
console.  If it is, the console is unlocked and no check is made against
the SUPERVISOR password.

   If the passwords don't match, then MONITOR checks against the
SUPERVISOR password.  If that's what you entered, then the console is
unlocked.  If it isn't right, though, then you have just made a failed
login attempt as far as intruder detection is concerned.

   Note that nowhere in the process does MONITOR check to see if the
password which was used to lock the console is the same as the
SUPERVISOR password.  Even if it is, if you don't type it in
correctly when attempting to unlock the console, it will still be
checked against both the MONITOR and the SUPERVISOR passwords, as
MONITOR does not know or care if they're the same.

   Note corrected list of newsgroups in the Followup-To: line.
-- 
stephen@bokonon.UUCP                     ...!{xrtll,gts.org}!bokonon!stephen
----------------------------------------------------------------------------
Stephen M. Dunn, CNE, ACE, Sr. Systems Analyst, United System Solutions Inc.
104 Carnforth Road, Toronto, ON, Canada M4A 2K7          (416) 750-7946 x251