From owner-freebsd-ports@FreeBSD.ORG Tue Jun 13 14:51:51 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E69C16A473 for ; Tue, 13 Jun 2006 14:51:51 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5641B43D48 for ; Tue, 13 Jun 2006 14:51:50 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so1079941wxd for ; Tue, 13 Jun 2006 07:51:49 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tClddTArYnMeNdBElES/I7fmJI7I6y2+fVhETBtwGxJ96c7cExKxVR8iApPQ3wn2vvnbxt01Fl9cSfPb6F9tBbWLChhtDmalQP3V0/rhy2EaVoRuy1iz33yYlXKVgAK7SkWnVFC1fP+YRESZ092QLphXZw8EJb/kOjlGHl/3JXY= Received: by 10.70.7.5 with SMTP id 5mr7545790wxg; Tue, 13 Jun 2006 07:51:48 -0700 (PDT) Received: by 10.70.83.15 with HTTP; Tue, 13 Jun 2006 07:51:48 -0700 (PDT) Message-ID: Date: Tue, 13 Jun 2006 18:51:48 +0400 From: "Andrew Pantyukhin" To: "Anish Mistry" In-Reply-To: <200606131037.58401.amistry@am-productions.biz> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060613113151.GC8105@heechee.tobez.org> <200606131037.58401.amistry@am-productions.biz> Cc: FreeBSD Ports , Doug Barton , Tobias Roth , UMENO Takashi Subject: Re: xlockmore - serious security issue X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jun 2006 14:51:51 -0000 On 6/13/06, Anish Mistry wrote: > On Tuesday 13 June 2006 07:54, Andrew Pantyukhin wrote: > > On 6/13/06, Anton Berezin 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.