1996-11-13 - RE: two bogus messages to this list

Header Data

From: Jim Wise <jim@santafe.arch.columbia.edu>
To: N/A
Message Hash: bc3689a77a33ed6c5e0a1105302c5f6a9cd740f78c73273eaabd2328a0ed0793
Message ID: <Pine.NEB.3.94.961113033655.7155A-100000@localhost>
Reply To: <01BBD081.63E4D3C0@blv-pm101-ip1.halcyon.com>
UTC Datetime: 1996-11-13 08:32:54 UTC
Raw Date: Wed, 13 Nov 1996 00:32:54 -0800 (PST)

Raw message

From: Jim Wise <jim@santafe.arch.columbia.edu>
Date: Wed, 13 Nov 1996 00:32:54 -0800 (PST)
Subject: RE: two bogus messages to this list
In-Reply-To: <01BBD081.63E4D3C0@blv-pm101-ip1.halcyon.com>
Message-ID: <Pine.NEB.3.94.961113033655.7155A-100000@localhost>
MIME-Version: 1.0
Content-Type: text/plain


On Tue, 12 Nov 1996, Mark M. Lacey wrote:

>> Even under NT, this DLL can be made to remain resident and trapping
>> Keystrokes, events, and window contents.
 
> This is (or was?) no problem under X Windows the last time I tried
> it (not recently), too.  In fact, you could monitor the keystrokes
> of any machine that you had access to remotely, as long as X was
> running.  All it took was a short little C program.  So what call
> is it on NT that you're talking about?

Only if the machines you are trapping from were silly enough to turn off
authentication.  This includes other users on the current machine trying
to trap from your display, BTW.

--
				Jim Wise
				System Administrator
				GSAPP, Columbia University
				jim@santafe.arch.columbia.edu
				http://www.arch.columbia.edu/~jim
				* Finger for PGP public key *






Thread