Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!execu!sequoia!rpp386!jfh
From: jfh@rpp386.cactus.org (John F. Haugh II)
Newsgroups: comp.unix.wizards
Subject: Re: Utility to keep all typed command lines.
Message-ID: <17562@rpp386.cactus.org>
Date: 5 Jan 90 06:40:45 GMT
References: <1527@utkcs2.cs.utk.edu> <1990Jan2.180615.28396@ux1.cso.uiuc.edu> <17538@rpp386.cactus.org> <1990Jan3.225009.17563@world.std.com>
Reply-To: jfh@rpp386.cactus.org (John F. Haugh II)
Organization: Lone Star Cafe and BBS Service
Lines: 18

In article <1990Jan3.225009.17563@world.std.com> bzs@world.std.com (Barry Shein) writes:
>Gak, I'm amazed at the bad advice this poor fool is getting, I think
>people don't understand what he's really after, probably spying on
>users to trap certain hackery. I assume that's what you mean,
>otherwise just use "script".

The same technology which brings us "script" works for spying as well.
You are looking for a complex solution where easy ones probably exist
as well.

To see how this works, consider the behavior of putting script onto a
port which the hacker is on, or likely to be on.  It is a trivial
matter to read from the port and write to a pty with a shell on the
other end of the pty.  This works equally well, regardless of whether
the user is co-operating or not ...
-- 
John F. Haugh II                             UUCP: ...!cs.utexas.edu!rpp386!jfh
Ma Bell: (512) 832-8832                           Domain: jfh@rpp386.cactus.org