Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!decwrl!labrea!csli!gandalf
From: gandalf@csli.STANFORD.EDU (Juergen Wagner)
Newsgroups: comp.sources.bugs
Subject: xlock (by John Coker, UCBerkeley)
Message-ID: <3572@csli.STANFORD.EDU>
Date: 22 Apr 88 04:03:12 GMT
Reply-To: gandalf@csli.stanford.edu (Juergen Wagner)
Organization: Center for the Study of Language and Information, Stanford U.
Lines: 9
Summary: Bug in xlock?

The program `xlock' which is available from ucbvax via anonymous ftp has
a bug/feature which makes it behave unexpected: if I am running X on 
machine A, and I am invoking xlock on machine B by
	xlock A:0
everything works fine....except....the password I am supposed to type in
in order to unlock the screen is the password I have on B!

-- 
Juergen "Gandalf" Wagner,		   gandalf@csli.stanford.edu
Center for the Study of Language and Information (CSLI), Stanford CA