Date: Tue, 7 Jul 1998 07:08:43 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: joelh@gnu.org, smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) Message-ID: <199807070708.AAA03942@usr06.primenet.com> In-Reply-To: <26015.899757973@time.cdrom.com> from "Jordan K. Hubbard" at Jul 6, 98 01:46:13 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > Most things that are disallowed under securelevel 1 are things that > > aren't frequently done except during rc, a system install, or an > > attack. But running X is a normal operation. I'd classify it as a > > bug myself. > > Actually, running X is not a "normal" operation at all - it performs > inb/outb instructions and does various privileged bits of syscons > frobbing that could be potentially quite hazardous in the hands of the > deliberately malicious. Running an X server should be a conscious > compromise of certain types of security. You wouldn't classify this as an architectural design bug in the granularity of FreeBSD's control over the I/O address space? Or in FreeBSD's console driver code leaving the X server no choice to obtain access to the display in bitmap mode? Admittedly, requiring user accessiblity to I/O space to get hardware to do something is wrong, but the requirement is because of FreeBSD not abstracting that access via a user<->kernel interface, not an inherent problem with the hardware. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807070708.AAA03942>