From gjm11@dpmms.cam.ac.uk  Wed May 21 03:56:28 1997
Received: from lilac.csi.cam.ac.uk (lilac.csi.cam.ac.uk [131.111.8.44])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA03875
          for <FreeBSD-gnats-submit@freebsd.org>; Wed, 21 May 1997 03:56:25 -0700 (PDT)
Received: from g.pet.cam.ac.uk [131.111.209.233] 
	by lilac.csi.cam.ac.uk with smtp (Exim 1.62 #1)
	id 0wU93c-0004rZ-00; Wed, 21 May 1997 11:55:48 +0100
Received: from gjm11 by g.pet.cam.ac.uk with local (Exim 1.59 #1)
	id 0wU93b-0001Kt-00; Wed, 21 May 1997 11:55:47 +0100
Message-Id: <E0wU93b-0001Kt-00@g.pet.cam.ac.uk>
Date: Wed, 21 May 1997 11:55:47 +0100
From: gjm11@dpmms.cam.ac.uk
Reply-To: gjm11@dpmms.cam.ac.uk
To: FreeBSD-gnats-submit@freebsd.org
Subject: xlock quits on receipt of signalxx 8
X-Send-Pr-Version: 3.2

>Number:         3649
>Category:       ports
>Synopsis:       xlock quits on receipt of signalxx 8
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed May 21 04:00:01 PDT 1997
>Closed-Date:    Sun Nov 16 11:01:58 PST 1997
>Last-Modified:  Sun Nov 16 11:02:27 PST 1997
>Originator:     Gareth McCaughan
>Release:        FreeBSD 2.2-RELEASE i386
>Organization:
all too little
>Environment:

	FreeBSD 2.2, X11R6.3 (XFree86 release 3.2A), xlockmore 3.13

>Description:

	When xlock receives a signal, it exits. This is a security
	hole; if you're running on dodgy hardware or there's a bug
	in the code, the terminal can become unlocked.

>How-To-Repeat:

	Run xlock and arrange for it to receive a SIGSEGV or a SIGFPE
	or similar.

>Fix:
	
	xlock should not exit on receipt of SIGILL, SIGEMT, SIGFPE,
	SIGBUS, SIGSEGV.
	It should of course still exit on receipt of e.g. SIGKILL.
	I'm not familiar enough with xlock's internals to provide a
	patch and be confident that it will work.

	Of course, if there are hardware problems or buggy code
	nothing will *guarantee* that xlock will carry on working...
>Release-Note:
>Audit-Trail:

From: j@uriah.heep.sax.de (J Wunsch)
To: gjm11@dpmms.cam.ac.uk
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: ports/3649: xlock quits on receipt of signalxx 8
Date: Wed, 21 May 1997 20:41:50 +0200

 As gjm11@dpmms.cam.ac.uk wrote:
 
 > 
 > >Number:         3649
 > >Category:       ports
 > >Synopsis:       xlock quits on receipt of signalxx 8
 
 Basically a dup for PR # 3640 (and probably more).
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)
State-Changed-From-To: open->closed 
State-Changed-By: fenner 
State-Changed-When: Sun Nov 16 11:01:58 PST 1997 
State-Changed-Why:  
As with PR ports/3640, should be fixed in the latest 
version of xlockmore (4.05). 
>Unformatted:
