From owner-freebsd-current@FreeBSD.ORG  Sun Apr 25 05:55:58 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0E9B716A4D2
	for <freebsd-current@FreeBSD.org>;
	Sun, 25 Apr 2004 05:55:57 -0700 (PDT)
Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 239C843D2D
	for <freebsd-current@FreeBSD.org>;
	Sun, 25 Apr 2004 05:55:57 -0700 (PDT)	(envelope-from bde@zeta.org.au)
Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au
	[61.8.0.86])i3PCtt5v022924;	Sun, 25 Apr 2004 22:55:55 +1000
Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246])
	i3PCtrI2031056;	Sun, 25 Apr 2004 22:55:54 +1000
Date: Sun, 25 Apr 2004 22:55:51 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: Randy Bush <randy@psg.com>
In-Reply-To: <16523.38199.999917.660146@ran.psg.com>
Message-ID: <20040425224147.H15264@gamplex.bde.org>
References: <16523.38199.999917.660146@ran.psg.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: FreeBSD Current <freebsd-current@FreeBSD.org>
Subject: Re: xterm -C not working
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Apr 2004 12:55:58 -0000

On Sun, 25 Apr 2004, Randy Bush wrote:

> ...
> xtem -C seems not to get console output on the xterm,
> though, if i run in non-X, i do get console messages
> ...
> not sure this is related, but i noticed that the kernel
> config
>    options         UCONSOLE
> is no longer legal (and the handbook on kernel configuration
> forgot to remove it).

This option opened a security hole in the broken TIOCCONS ioctl.
I think xterm -C uses this ioctl.  The security hole was that
everyone was permitted to take over the console.  Now only users
who can open /dev/console for reading can take it over.  The
brokenness is that TIOCCONS causes panics.  It apparently never
worked, but it causes panics more reliably now because the bad
things that it does are detected by locking assertions.

Bruce