Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!att!ulysses!ulysses.att.com!smb
From: smb@ulysses.att.com (Steven Bellovin)
Newsgroups: comp.unix.internals
Subject: Re: BSD tty security, part 3: How to Fix It
Message-ID: <14858@ulysses.att.com>
Date: 21 May 91 18:55:51 GMT
References: <23893:May1901:19:2191@kramden.acf.nyu.edu> <19313@rpp386.cactus.org> <19323@rpp386.cactus.org>
Sender: netnews@ulysses.att.com
Lines: 13

In article <19323@rpp386.cactus.org>, jfh@rpp386.cactus.org (John F Haugh II) writes:
> AT&T, in their SV/MLS system, supports 3 different SAK mechanisms for
> the 630 MTG terminal.  They are 1) power cycling, 2) <CTRL><BREAK>
> and 3) <SHIFT><CTRL><ESC>.  I'd wager that the hardware guys prefer
> you don't power cycle because of the stress that places on the
> hardware compared to a simple keystroke sequence.  [ I'm sure the
> customers would prefer the system not nuke everything in sight. ]

Umm -- ctrl-BREAK drops DTR, which is one solution already suggested.
And ctrl-shift-ESC on the 630 is the reset sequence, which not only
drops DTR, but also wipes the program cache, the font cache, etc.,
on the terminal.  In other words, it's the software equivalent of
power-cycling...