xlockmore - serious security issue

Anton Berezin tobez at tobez.org
Tue Jun 13 11:31:53 UTC 2006

On Tue, Jun 13, 2006 at 03:18:16PM +0400, Andrew Pantyukhin wrote:
> For months I've been in doubt, holding my own insanity
> responsible for compromising my own workstation for
> several times on end.
> The problem is that xlockmore exits all by itself when
> left alone for a couple of days. It works all right overnight,
> but when left for the weekend, it almost certainly fails. I
> just come to work and see that my workstation is unlocked,
> what a surprise.
> At first I was sure that xlockmore could not just fail like that,
> that it was me who forgot to launch it before leaving. But for
> the last few times (over a month, considering that I can only
> experiment at weekends), I made a strong mental note
> about me launching xlock (I do it from the fluxbox context
> menu, btw).
> Has anyone experienced this? My xlockmore is compiled
> without any knobs tweaked. I use 5.22 and I'm not sure
> if this problem was there in 5.21 or earlier versions. What
> I am sure of is that I've used xlockmore for over a year
> and never had this problem until a few months back.

Any coredumps?  What -modes do you use?  Other command line parameters?

Sounds like a random -mode failure to me.  I've been using -mode swarm for 8
or 9 years now with no ill effects whatsoever, with multiple versions of
FreeBSD, X11, and xlockmore.

An undefined problem has an infinite number of solutions.
-- Robert A. Humphrey

More information about the freebsd-ports mailing list