Date: Tue, 13 Jun 2006 04:50:04 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Andrew Pantyukhin <infofarmer@gmail.com> Cc: FreeBSD Ports <ports@freebsd.org>, UMENO Takashi <umeno@rr.iij4u.or.jp>, Tobias Roth <ports@fsck.ch> Subject: Re: xlockmore - serious security issue Message-ID: <448EA66C.9070301@FreeBSD.org> In-Reply-To: <cb5206420606130418x706ccd61t5840bd2b0c00f61b@mail.gmail.com> References: <cb5206420606130418x706ccd61t5840bd2b0c00f61b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Pantyukhin wrote: > 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? Yes, I used to experience it regularly back when I used xlockmore, that's why I switched to xscreensaver. The part of the program that locks the screen is totally separate from the screen savers, so if a screen saver program goes wonky, it won't compromise your system. hth, Doug
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?448EA66C.9070301>