Date: Tue, 13 Jun 2006 11:07:26 -0400 From: Anish Mistry <amistry@am-productions.biz> To: "Andrew Pantyukhin" <infofarmer@gmail.com> 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: <200606131107.45104.amistry@am-productions.biz> In-Reply-To: <cb5206420606130751s65808df2rb39b2ebb163757c4@mail.gmail.com> References: <cb5206420606130418x706ccd61t5840bd2b0c00f61b@mail.gmail.com> <200606131037.58401.amistry@am-productions.biz> <cb5206420606130751s65808df2rb39b2ebb163757c4@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart3054853.z3bsZYTU4I Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 13 June 2006 10:51, Andrew Pantyukhin wrote: > 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=20 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. I think making the blank screen default or disabling the GL modes and=20 marking it forbidden if you toggle the switch to enable the GL modes,=20 should be sufficient. Ideally someone who cares about the GL modes=20 should probably look into fixing the problem. =2D-=20 Anish Mistry amistry@am-productions.biz AM Productions http://am-productions.biz/ --nextPart3054853.z3bsZYTU4I Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEjtTBxqA5ziudZT0RArtlAJ43aSxOT3To7Ro9Ch2A+IA91wWjJgCfREAu qZ5795fxTMBRnmQ8VLqB0fk= =YZjN -----END PGP SIGNATURE----- --nextPart3054853.z3bsZYTU4I--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200606131107.45104.amistry>