From owner-freebsd-current Mon Jul 6 13:47:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16145 for freebsd-current-outgoing; Mon, 6 Jul 1998 13:47:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16129 for ; Mon, 6 Jul 1998 13:47:24 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id NAA26019; Mon, 6 Jul 1998 13:46:14 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: joelh@gnu.org cc: smoergrd@oslo.geco-prakla.slb.com, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG Subject: Re: xf86OpenConsole: KDENABIO failed (Operation not permitted) In-reply-to: Your message of "Mon, 06 Jul 1998 11:46:33 CDT." <199807061646.LAA06285@detlev.UUCP> Date: Mon, 06 Jul 1998 13:46:13 -0700 Message-ID: <26015.899757973@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message