All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Jaspreet Singh <jsingh@ensim.com>
Cc: nsa <SELinux@tycho.nsa.gov>, Stephen Smalley <sds@epoch.ncsc.mil>
Subject: Re: Configuring kernel module for labeling ...
Date: Tue, 2 Nov 2004 10:26:47 +0000	[thread overview]
Message-ID: <20041102102647.GV9643@lkcl.net> (raw)
In-Reply-To: <1099385154.11681.3.camel@jsingh>


On Tue, Nov 02, 2004 at 02:15:55PM +0530, Jaspreet Singh wrote:
> Hi,
> 
> could anybody explain me the following msg ...

 in a roundabout way that i _hope_ will demonstrate a methodolgy and
 guess-work that will enhance your own ability to track these issues
 down, yes, i think so.

 [i had to go through the same process with adding fuse, but had help
 from stephen in the fs_use bit iirc]

> SELinux: initialized (dev overlay_fs, type overlay_fs), not configured
> for labeling
 
 okay, grep "not configured for label" in security/*/*.c, gives
 selinux/hooks.c an array of labeling behaviours - entry with index 4 is
 "not configured for labeling".

 sbsec->behaviour indexes that array (line 593) and looking at locations
 where it's used, you have #defines SECURITY_FS_USE_XATTR -->
 SECURITY_FS_USE_MNTPOINT in selinux/include/security.h

 i think i know where this is leading, especially with the
 Opt_defcontent and stuff.

 okay, jaspreet: did you add overlay_fs to /etc/selinux/src/fs_use?

 because i _think_ the fs_use file contains wordy versions of the
 SECURITY_FS_USE #defines.

 and the default is "not configured".

 so you will need to specify, in /etc/selinux/src/fs_use, a line
 fs_use_xattr overlay system_u:object_r:fs_t;

 [just like i had to do with fuse].

 the name (overlay) MUST match the name of your module in your overlay
 kernel source code.

 l.

-- 
--
you don't have to BE MAD   | this space    | my brother wanted to join mensa,
  to work, but   IT HELPS  |   for rent    | for an ego trip - and get kicked 
 you feel better!  I AM    | can pay cash  | out for a even bigger one.
--

--
This message was distributed to subscribers of the selinux mailing 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.

  reply	other threads:[~2004-11-02 10:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02  8:45 Configuring kernel module for labeling Jaspreet Singh
2004-11-02 10:26 ` Luke Kenneth Casson Leighton [this message]
2004-11-02 16:23 ` Russell Coker
2004-11-02 17:45   ` Jaspreet Singh
2004-11-02 18:28     ` Stephen Smalley
2004-11-02 18:42       ` Stephen Smalley
2004-11-02 20:33         ` Jaspreet Singh
2004-11-02 20:48           ` Stephen Smalley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041102102647.GV9643@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=SELinux@tycho.nsa.gov \
    --cc=jsingh@ensim.com \
    --cc=sds@epoch.ncsc.mil \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.