Date: Tue, 13 Jun 2006 18:51:48 +0400 From: "Andrew Pantyukhin" <infofarmer@gmail.com> To: "Anish Mistry" <amistry@am-productions.biz> Cc: FreeBSD Ports <ports@freebsd.org>, Doug Barton <dougb@freebsd.org>, Tobias Roth <ports@fsck.ch>, UMENO Takashi <umeno@rr.iij4u.or.jp> Subject: Re: xlockmore - serious security issue Message-ID: <cb5206420606130751s65808df2rb39b2ebb163757c4@mail.gmail.com> In-Reply-To: <200606131037.58401.amistry@am-productions.biz> References: <cb5206420606130418x706ccd61t5840bd2b0c00f61b@mail.gmail.com> <20060613113151.GC8105@heechee.tobez.org> <cb5206420606130454i2c4fac71m53c7b2d81839e7dd@mail.gmail.com> <200606131037.58401.amistry@am-productions.biz>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/13/06, Anish Mistry <amistry@am-productions.biz> wrote: > On Tuesday 13 June 2006 07:54, Andrew Pantyukhin wrote: > > On 6/13/06, Anton Berezin <tobez@tobez.org> wrote: > > > 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? > > > > Nope. None at all. > > > > > What -modes do you use? Other command line parameters? > > > > I just run "xlock". No args. > > > > > Sounds like a random -mode failure to me. > > > > Now that you mention it, it does. I'll try to stick to swarm. I > > kinda like random modes, though. > I just stick with a blank screen and works fine for several weeks at a > time. I found some of the GL screensavers to cause problems. Ask me - we should mark this port forbidden and/or make and entry in vuxml until we resolve this issue. Let's make blank screen the default behavior or something. To leave this as is is unacceptable.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420606130751s65808df2rb39b2ebb163757c4>