From owner-freebsd-ports@FreeBSD.ORG  Tue Jun 13 23:58:16 2006
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: freebsd-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 0418D16A474;
	Tue, 13 Jun 2006 23:58:16 +0000 (UTC)
	(envelope-from tarc@tarc.po.cs.msu.su)
Received: from tarc.po.cs.msu.su (tarc.po.cs.msu.su [158.250.16.33])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3A46D43D46;
	Tue, 13 Jun 2006 23:58:15 +0000 (GMT)
	(envelope-from tarc@tarc.po.cs.msu.su)
Received: from tarc.po.cs.msu.su (localhost [127.0.0.1])
	by tarc.po.cs.msu.su (8.13.4/8.13.4) with ESMTP id k5E00mSP053634;
	Wed, 14 Jun 2006 04:00:48 +0400 (MSD)
	(envelope-from tarc@tarc.po.cs.msu.su)
Received: (from tarc@localhost)
	by tarc.po.cs.msu.su (8.13.4/8.13.4/Submit) id k5E00mo1053633;
	Wed, 14 Jun 2006 04:00:48 +0400 (MSD) (envelope-from tarc)
Date: Wed, 14 Jun 2006 04:00:48 +0400
From: Tarc <tarc@tarc.po.cs.msu.su>
To: "Simon L. Nielsen" <simon@freebsd.org>
Message-ID: <20060614000048.GM22799@tarc.po.cs.msu.su>
References: <cb5206420606130418x706ccd61t5840bd2b0c00f61b@mail.gmail.com>
	<20060613113151.GC8105@heechee.tobez.org>
	<cb5206420606130454i2c4fac71m53c7b2d81839e7dd@mail.gmail.com>
	<200606131037.58401.amistry@am-productions.biz>
	<cb5206420606130751s65808df2rb39b2ebb163757c4@mail.gmail.com>
	<20060613234027.GC1074@zaphod.nitro.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
In-Reply-To: <20060613234027.GC1074@zaphod.nitro.dk>
User-Agent: mutt-ng/devel-r581 (FreeBSD)
Cc: freebsd-ports@freebsd.org
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 23:58:16 -0000

> FORBIDDEN and a VuXML entry seems in a way a bit overkill to me seems
> a bit overkill to me, since it's not really a vulnerability, but I'm
> open to input.
> 
> As mentioned by others, xlockmore is fundamentally flawed
> wrt. guaranteeing that the screen stays locked in that the
> screensavers code can kill the lock, which it should not be able to
> happen.
> 
> Has anyone contacted the xlockmore author for comment on this issue?
> 
> One thing we could do right now is to add a message at install time
> warning that xlockmore might unlock the screen (a bit like the Pine
> warning).
> 
> -- 
> Simon L. Nielsen

about signals:
	xlockmore catchs SIGINT SIGTERM SIGQUIT SIGSEGV SIGBUS SIGFPE and SIGHUP if compilled with debug.
	on these signals it lockout your display.

	But you can lock vt switching
-- 
   Best regards,
   	Arseny Nasokin