Date: Wed, 10 Jan 2001 07:51:54 -0800 From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca> To: Matjaz Martincic <matjaz.martincic@hermes.si> Cc: "'Rasputin'" <rasputin@FreeBSD-uk.eu.org>, freebsd-security@FreeBSD.ORG Subject: Re: Running X in securelevels > 0 ? Message-ID: <200101101551.f0AFpwH63004@cwsys.cwsent.com> In-Reply-To: Your message of "Tue, 09 Jan 2001 11:51:59 %2B0100." <EA63CEA50DF8D311ABAD00B0D0211732211A94@hal9000.hermes.si>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <EA63CEA50DF8D311ABAD00B0D0211732211A94@hal9000.hermes.si>, Matjaz M artincic writes: > Had the same problem. I somehow managed to bypass it by creating the shell > script that first run the Xserver and then change the securelevel with > sysctl. And it worked. But the problem is that the securelevel is not > changed at boot time :(, so you have to run X to set it first. In this situation xdm is your friend. Start xdm in rc.local, then manually set the securelevel in rc.local after xdm has started. Make sure that your X server does not start with the -terminate option, which BTW will leave you open to memory leaks in the X server. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101101551.f0AFpwH63004>