COMMAND
kernel (SAS)
SYSTEMS AFFECTED
WinNT
PROBLEM
Jarod Jenson was playing and found something interesting with
the SAS. On NT 4.0 SP4, when you CTRL-ALT-DEL and enter your
username and password, let's change our mind before hitting
return. Delete the password using BKSPC and walkaway. The next
lucky guy gets to right click over the password entry dialog, UNDO
and press return. Walla, he's YOU.
Not only that, but if you press CTRL-ALT-ESC-DEL, you can't get
the logon screen back with *any* keys on the keyboard, only the
mouse click works. AND, if you try a combination of the ALT key
and other keys, the logon screen *never* returns, and you have to
warm reboot to get the logon screen back. (This was working from
a locked workstation. When tested during login after reboot, the
logon screen would always return with a mouse click). This was
tested on NT 4.0 WKS/SP5. by Paul L. Schmehl.
Ben Ryan found also something regarding a strange behaviour in the
opening screen for Windows NT. The SAS, or Secure Attention
Screen (?) is the dialog that appears telling you to hit
CTRL-ALT-DEL to log on. This key sequence, according to MS, is
intended to prevent Trojan applications from taking over the logon
process. This was done back in the days when DOS applications
could be loaded upon boot waiting for someone to logon. Anyway,
Ben's observation was that if you hit CTRL-ALT-ESC-DEL (all 4 keys
at the same time), the SAS dialog would clear, but no logon dialog
would appear. If, however, you press a mouse button after hitting
the 4 keys simultaneously, the logon dialog box *would* appear.
SOLUTION
Maybe some keyboard coder can explain why NT respects
CTRL-ALT-ESC-DEL mouse-click as CTRL-ALT-DEL, but this would seem
to be a bit of a problem in the theory. NT isn't supposed to take
us to the logon dialog via any other key sequence other than
CTRL-ALT-DEL. As for UNDO problem, nothing yet too.