Date: Sun, 25 Apr 2004 10:28:10 -0700 From: Randy Bush <randy@psg.com> To: Bruce Evans <bde@zeta.org.au> Cc: FreeBSD Current <freebsd-current@FreeBSD.org> Subject: Re: xterm -C not working Message-ID: <16523.62762.329440.73697@ran.psg.com> References: <16523.38199.999917.660146@ran.psg.com> <20040425224147.H15264@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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. hmmm. and, considering the devfs stuff, when/how can/should one allow the X server user to have read perms? randy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16523.62762.329440.73697>