Date: Sun, 25 Apr 2004 22:55:51 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Randy Bush <randy@psg.com> Cc: FreeBSD Current <freebsd-current@FreeBSD.org> Subject: Re: xterm -C not working Message-ID: <20040425224147.H15264@gamplex.bde.org> In-Reply-To: <16523.38199.999917.660146@ran.psg.com> References: <16523.38199.999917.660146@ran.psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040425224147.H15264>