From owner-freebsd-ports@FreeBSD.ORG  Tue Jun 13 11:31:53 2006
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 08C5C16A41A
	for <ports@freebsd.org>; Tue, 13 Jun 2006 11:31:53 +0000 (UTC)
	(envelope-from tobez@tobez.org)
Received: from heechee.tobez.org (heechee.tobez.org [194.255.56.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8D24143D45
	for <ports@freebsd.org>; Tue, 13 Jun 2006 11:31:52 +0000 (GMT)
	(envelope-from tobez@tobez.org)
Received: by heechee.tobez.org (Postfix, from userid 1001)
	id 17DDC125427; Tue, 13 Jun 2006 13:31:51 +0200 (CEST)
Date: Tue, 13 Jun 2006 13:31:51 +0200
From: Anton Berezin <tobez@tobez.org>
To: Andrew Pantyukhin <infofarmer@gmail.com>
Message-ID: <20060613113151.GC8105@heechee.tobez.org>
Mail-Followup-To: Anton Berezin <tobez@tobez.org>,
	Andrew Pantyukhin <infofarmer@gmail.com>,
	FreeBSD Ports <ports@freebsd.org>,
	UMENO Takashi <umeno@rr.iij4u.or.jp>, Tobias Roth <ports@fsck.ch>
References: <cb5206420606130418x706ccd61t5840bd2b0c00f61b@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <cb5206420606130418x706ccd61t5840bd2b0c00f61b@mail.gmail.com>
User-Agent: Mutt/1.4.2.1i
X-Powered-By: FreeBSD http://www.freebsd.org/
Cc: FreeBSD Ports <ports@freebsd.org>, UMENO Takashi <umeno@rr.iij4u.or.jp>,
	Tobias Roth <ports@fsck.ch>
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 <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jun 2006 11:31:53 -0000

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?  What -modes do you use?  Other command line parameters?

Sounds like a random -mode failure to me.  I've been using -mode swarm for 8
or 9 years now with no ill effects whatsoever, with multiple versions of
FreeBSD, X11, and xlockmore.

\Anton.
-- 
An undefined problem has an infinite number of solutions.
-- Robert A. Humphrey