From: Dennis Wronka <linuxweb@gmx.net>
To: Justin Mattock <justinmattock@gmail.com>
Cc: "SE-Linux" <selinux@tycho.nsa.gov>, tresys <refpolicy@oss.tresys.com>
Subject: Re: ext3 security labels missing
Date: Fri, 20 Feb 2009 15:42:47 +0800 [thread overview]
Message-ID: <200902201542.50638.linuxweb@gmx.net> (raw)
In-Reply-To: <dd18b0c30902192304w76b8c2ebt1f0954d2d5cb903b@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2750 bytes --]
Might it be possible that you didn't enable support for security labels when
compiling the kernel?
Check Filesystems -> Ext3 Security Labels
Also, when installing LFS with SELinux, did you compile GLibC twice?
I first compile it without SELinux, afterwards the SELinux-libraries, so that
those can link against GLibC, and then again GLibC, with SELinux-support that
time.
Don't know though if that would be any issue, having a GLibC that isn't aware
of SELinux.
But I, for myself found that probably the safest way seems to add an extra
compile of GLibC to the install after installing the SELinux-libs.
On Friday 20 February 2009 15:04:54 Justin Mattock wrote:
> I've a strange issue.
> with my experimental learning machine(LFS)
> I'm able to load the policy etc.. but have no labels
> on my files.(just a question mark);
>
>
> ls -lZ shows
>
> drwxr-xr-x 2 root root ? 4096 Feb 18 11:19 bin
> drwxr-xr-x 3 root root ? 4096 Feb 19 22:36 boot
> lrwxrwxrwx 1 root 999 ? 11 Feb 9 16:34 cdrom -> media/cdrom
> drwxr-xr-x 17 root root ? 4120 Feb 19 22:42 dev
> drwxr-xr-x 28 root root ? 4096 Feb 19 22:47 etc
> drwxr-xr-x 4 root root ? 4096 Feb 19 22:36 home
> drwxr-xr-x 4 root root ? 4096 Feb 18 11:19 include
> drwxr-xr-x 10 root root ? 4096 Feb 19 18:52 lib
> drwx------ 2 root root ? 16384 Feb 9 16:34 lost+found
> drwxr-xr-x 3 root root ? 4096 Feb 19 22:42 media
> drwxr-xr-x 3 root root ? 4096 Feb 11 12:09 mnt
> drwxr-xr-x 2 root root ? 4096 Feb 10 09:54 opt
> dr-xr-xr-x 113 root root ? 0 Feb 19 22:42 proc
> drwxr-xr-x 5 root root ? 4096 Feb 18 11:24 root
> drwxr-xr-x 2 root root ? 4096 Feb 19 21:11 sbin
> drwxr-xr-x 7 root root ? 0 Feb 19 22:42 selinux
> drwxr-xr-x 8 root root ? 4096 Feb 18 11:19 share
> drwxr-xr-x 2 root root ? 4096 Feb 10 09:54 srv
> drwxr-xr-x 12 root root ? 0 Feb 19 22:42 sys
> drwxrwxrwt 5 root root ? 4096 Feb 19 22:50 tmp
> drwxr-xr-x 6 root root ? 4096 Feb 11 12:05 tools
> drwxr-xr-x 14 root root ? 4096 Feb 14 10:09 usr
> drwxr-xr-x 10 root root ? 4096 Feb 18 22:31 var
> lrwxrwxrwx 1 root root ? 24 Feb 10 13:11 vmlinuz ->
> /boot/vmlinuz-2.6.29-rc4
>
> if I do a id -Z I get:
> id: --context (-Z) works only on an SELinux-enabled kernel
> (but it is enabled in the kernel)
>
> >From looking back, I enabled as much as possible in any app/lib I was
> > compiling
>
> that provided selinux support.(libc,xserver,hal,dbus, etc..);
> But could be missing an important app/lib that might make the security
> labels give the proper label. by chance if anybody had experienced this
> and/or knows what might be going on,(would be really appreciated).
>
> regards;
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-20 7:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 7:04 ext3 security labels missing Justin Mattock
2009-02-20 7:04 ` [refpolicy] " Justin Mattock
2009-02-20 7:42 ` Dennis Wronka [this message]
2009-02-20 14:14 ` Stephen Smalley
2009-02-20 14:14 ` [refpolicy] " Stephen Smalley
2009-02-20 15:03 ` Justin Mattock
2009-02-20 15:03 ` [refpolicy] " Justin Mattock
2009-02-20 15:20 ` Dennis Wronka
2009-02-20 23:10 ` Justin Mattock
2009-02-21 5:51 ` Dennis Wronka
2009-02-21 9:55 ` Justin Mattock
[not found] ` <200902211806.55864.linuxweb@gmx.net>
[not found] ` <4B40ED4D-BDE5-447D-A374-FDFF3B9CE634@gmail.com>
2009-02-21 19:49 ` Justin Mattock
2009-02-21 19:49 ` [refpolicy] " Justin Mattock
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=200902201542.50638.linuxweb@gmx.net \
--to=linuxweb@gmx.net \
--cc=justinmattock@gmail.com \
--cc=refpolicy@oss.tresys.com \
--cc=selinux@tycho.nsa.gov \
/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.