Received: from jazzband.ncsc.mil (jazzband.ncsc.mil [144.51.5.4]) by tycho.ncsc.mil (8.9.3/8.9.3) with ESMTP id JAA17227 for ; Wed, 26 Jun 2002 09:43:56 -0400 (EDT) Received: from jazzband.ncsc.mil (localhost [127.0.0.1]) by jazzband.ncsc.mil with ESMTP id NAA00903 for ; Wed, 26 Jun 2002 13:42:30 GMT Received: from web40003.mail.yahoo.com (web40003.mail.yahoo.com [66.218.78.21]) by jazzband.ncsc.mil with SMTP id NAA00899 for ; Wed, 26 Jun 2002 13:42:29 GMT Message-ID: <20020626134354.53630.qmail@web40003.mail.yahoo.com> Date: Wed, 26 Jun 2002 06:43:54 -0700 (PDT) From: Brad Chapman Subject: Re: Configuration issues on a new installation To: Stephen Smalley Cc: selinux@tycho.nsa.gov In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-selinux@tycho.nsa.gov List-Id: selinux@tycho.nsa.gov Mr. Smalley, --- Stephen Smalley wrote: > > On Tue, 25 Jun 2002, Brad Chapman wrote: > > > I have just started using SELinux on my 2.4.18 system. I found an > enormous > > number of avc: denied messages in my dmesg and attempted to remove them. So > far > > I have tweaked the devfs_contexts and the policy.conf files (using > > scripts/newrules.pl for policy.conf) since most of the errors were related > to > > device files and system call commands. I have also installed the SELinux > devfsd > > extension and added the config entries to my devfsd.conf, to no apparent > avail. > > > > What is the fastest way to eliminate most (if not preferably all) of > these > > messages and put me closer to activating enforcing mode? > > The Configuring the SELinux Policy report discusses how to customize your > policy, although this is certainly not a fast process. The report is > included in the distribution and is also available from the NSA SELinux > web site. I saw it there, but it is not an easy-to-read document and would take some time to parse correctly. > > It sounds like you are using Russell Coker's Debian selinux package rather > than the upstream distribution. Is that correct? Russell's package > includes a more complete example policy configuration. No. My base platform is RedHat 6.2 (heavily modified) with the 2.4.18 kernel (as mentioned previously) and the SELinux utils package dated 1000hrs May 31, 2002. > > You should be cautious about simply adding rules generated by newrules.pl. > It can be a helpful tool if used properly, but you should not blindly add > the rules it generates to your policy configuration. In many cases, you > will want to define new domains and/or types rather than granting > permissions to the existing ones in order to preserve your security goals. I am aware of that. I have read through parts of the policy.conf file and was about to start working on that before messing with the *.te files in policy/. > > The SELinux devfsd support has known problems with preserving security > contexts on devfs entries. Fully supporting the SELinux devfsd will > require modifications to the kernel devfs code. I'd suggest using > devfs_contexts instead. I edited that too. > > -- > Stephen D. Smalley, NAI Labs > ssmalley@nai.com > Thanks for the help, Brad ===== Brad Chapman Permanent e-mails: kakadu_croc@yahoo.com jabiru_croc@yahoo.com tanami_croc@devel.lbsd.net __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com -- You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without quotes as the message.