Path: utzoo!attcan!uunet!world!bzs
From: bzs@world.std.com (Barry Shein)
Newsgroups: comp.unix.internals
Subject: Re: Finding Passwords
Message-ID: <BZS.90Oct9150046@world.std.com>
Date: 9 Oct 90 19:00:46 GMT
References: <652@puck.mrcu> <22024:Oct606:35:1090@kramden.acf.nyu.edu>
	<13@tdatirv.UUCP> <9105:Oct910:13:5190@kramden.acf.nyu.edu>
	<278@pdxgate.UUCP>
Sender: bzs@world.std.com (Barry Shein)
Organization: The World
Lines: 26
In-Reply-To: griffith@eecs.cs.pdx.edu's message of 9 Oct 90 15:31:03 GMT


Wouldn't an uncatchable (except by a root process) SIGTSTOP character
solve a lot of this relatively harmlessly? The only real problem with
such a thing (that comes up commonly) is the ability to put the
terminal back into line mode when the process is suspended (e.g. full
screen applications.)

Or even a character similar to the TOPS-20 ^T command which printed a
line on the screen about session status.

That way you could type ^T or whatever it is and it might echo:

	/bin/login (PID=2833) running as UID=0

And, again, ^xyz couldn't be trapped.

I would opt for BREAK soas not to lose another control char. And, even
if you have a noisy line sending some breaks at worst you have to
suffer a few unwanted messages to your screen.

Heck, something like this could even be otherwise useful.
-- 
        -Barry Shein

Software Tool & Die    | {xylogics,uunet}!world!bzs | bzs@world.std.com
Purveyors to the Trade | Voice: 617-739-0202        | Login: 617-739-WRLD