Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!spool.mu.edu!rex!ukma!seismo!dimacs.rutgers.edu!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.unix.wizards
Subject: Re: BSD tty security, part 3: How to Fix It
Message-ID: <16215@smoke.brl.mil>
Date: 21 May 91 03:40:12 GMT
References: <23893:May1901:19:2191@kramden.acf.nyu.edu> <19313@rpp386.cactus.org> <3690:May1921:22:5191@kramden.acf.nyu.edu>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 12

In article <3690:May1921:22:5191@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
>Can you please stop repeating the same stupid little question? If you
>can't understand Bellovin's explanations or my explanations or the
>series of diagrams above, I give up.

Gee, nice diagrams.  If done earlier, it might have saved a thousand words.

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.)