Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!execu!sequoia!rpp386!jfh
From: jfh@rpp386.cactus.org (John F Haugh II)
Newsgroups: comp.unix.internals
Subject: Re: BSD tty security, part 3: How to Fix It
Message-ID: <19323@rpp386.cactus.org>
Date: 21 May 91 12:41:35 GMT
References: <23893:May1901:19:2191@kramden.acf.nyu.edu> <19313@rpp386.cactus.org> <3690:May1921:22:5191@kramden.acf.nyu.edu> <16215@smoke.brl.mil>
Reply-To: jfh@rpp386.cactus.org (John F Haugh II)
Organization: Lone Star Cat Emporium and BBQ Grill
Lines: 24
X-Clever-Slogan: Help Prevent Robbery.  Tax the IRS.

In article <16215@smoke.brl.mil> gwyn@smoke.brl.mil (Doug Gwyn) writes:
>Gee, nice diagrams.  If done earlier, it might have saved a thousand words.

The problem is that his diagrams still didn't answer the question.  I
don't care about what happens at login time, but rather what happens
well after login time.

>Ready for the next question?  Why an SAK like ^K?  Why not just have loss
>of DTR be the attention signal?  You're going to blow off the previous
>session anyway, might as well let terminal poweroff automatically serve
>as your SAK.  (Yes, I know you have to wire and configure things correctly,
>but that sort of argument applies to any scheme.)

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. ]
-- 
John F. Haugh II        | Distribution to  | UUCP: ...!cs.utexas.edu!rpp386!jfh
Ma Bell: (512) 255-8251 | GEnie PROHIBITED :-) |  Domain: jfh@rpp386.cactus.org
"If liberals interpreted the 2nd Amendment the same way they interpret the
 rest of the Constitution, gun ownership would be mandatory."