From owner-freebsd-ports@FreeBSD.ORG  Tue Jun 13 11:18:17 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 873E016A492
	for <ports@freebsd.org>; Tue, 13 Jun 2006 11:18:17 +0000 (UTC)
	(envelope-from infofarmer@gmail.com)
Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.193])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CE22E43D49
	for <ports@freebsd.org>; Tue, 13 Jun 2006 11:18:16 +0000 (GMT)
	(envelope-from infofarmer@gmail.com)
Received: by wx-out-0102.google.com with SMTP id i31so1048083wxd
	for <ports@freebsd.org>; Tue, 13 Jun 2006 04:18:16 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=n+IvRfkfzyd5w9xZoZEn4uhNDx8Lmg3xcK4C++U/43UvvkLoa+YMjYfy74Ezs8AAK/Ljo93cWJjXEiBJr80e/x2lHq7f9GlQ9zPjTGaAfs6WhviIZHcHmk+5h53pBlgXLBRbX3dGGDltiLOjoYEJ84/mYNNKZHWpOyHStrvOo1o=
Received: by 10.70.33.8 with SMTP id g8mr3544813wxg;
	Tue, 13 Jun 2006 04:18:16 -0700 (PDT)
Received: by 10.70.83.15 with HTTP; Tue, 13 Jun 2006 04:18:16 -0700 (PDT)
Message-ID: <cb5206420606130418x706ccd61t5840bd2b0c00f61b@mail.gmail.com>
Date: Tue, 13 Jun 2006 15:18:16 +0400
From: "Andrew Pantyukhin" <infofarmer@gmail.com>
To: "FreeBSD Ports" <ports@freebsd.org>, "UMENO Takashi" <umeno@rr.iij4u.or.jp>,
	"Tobias Roth" <ports@fsck.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 
Subject: 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:18:17 -0000

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.

Thanks!