Date: Tue, 13 Jun 2006 15:18:16 +0400 From: "Andrew Pantyukhin" <infofarmer@gmail.com> To: "FreeBSD Ports" <ports@freebsd.org>, "UMENO Takashi" <umeno@rr.iij4u.or.jp>, "Tobias Roth" <ports@fsck.ch> Subject: xlockmore - serious security issue Message-ID: <cb5206420606130418x706ccd61t5840bd2b0c00f61b@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
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. Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420606130418x706ccd61t5840bd2b0c00f61b>