From: Eric Paris <eparis@parisplace.org>
To: vin@netwosix.org
Cc: Stephen Smalley <sds@tycho.nsa.gov>, SELinux@tycho.nsa.gov
Subject: Re: SELinux and LFS
Date: Thu, 15 Feb 2007 15:56:20 -0500 [thread overview]
Message-ID: <1171572980.18488.30.camel@localhost.localdomain> (raw)
In-Reply-To: <1171572168.5239.0.camel@desk.netwosix.org>
On Thu, 2007-02-15 at 21:42 +0100, Vincenzo Ciaglia wrote:
> Il giorno gio, 15/02/2007 alle 15.34 -0500, Stephen Smalley ha scritto:
>
> > Targeted policy doesn't support user roles; it only confines specific
> > programs, primarily focused on system services. Strict policy is what
> > you want if you need user roles. In the future, we hope to reduce the
> > divergence between them so that you can have a targeted system with some
> > limited user roles.
>
> Of course Netwosix will use "strict" policies. So i'm going to start
> working on it.
>
> I'll keep you updated.
>
> Thank you,
>
Taking a look at your post at netwosix.org I think you should know that
you most likely still have some serious filesystem labeling problems.
Yours:
# ls -Z
drwxr-xr-x root root system_u:object_r:file_t bin
drwxr-xr-x root root system_u:object_r:file_t boot
drwxr-xr-x root root system_u:object_r:file_t cdrom
drwxr-xr-x root root system_u:object_r:tmpfs_t dev
Mine:
#ls -Z
drwxr-xr-x root root system_u:object_r:bin_t bin
drwxr-xr-x root root system_u:object_r:boot_t boot
drwxr-xr-x root root system_u:object_r:device_t dev
Maybe someone else can chime in with the best way to try this again
since it doesn't look to me like the make relabel really got everything
you needed (and I have no idea if you rc.sysinit is patched to pay
attention to /.autorelabel)
-Eric
--
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.
next prev parent reply other threads:[~2007-02-15 20:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 17:38 SELinux and LFS Vincenzo Ciaglia
2007-02-14 18:08 ` Christopher J. PeBenito
2007-02-14 18:17 ` Christopher J. PeBenito
2007-02-14 20:34 ` Karl MacMillan
2007-02-14 22:10 ` Vincenzo Ciaglia
2007-02-15 13:55 ` Vincenzo Ciaglia
2007-02-15 18:41 ` Stephen Smalley
2007-02-15 19:35 ` Vincenzo Ciaglia
2007-02-15 19:48 ` Stephen Smalley
2007-02-15 17:16 ` Vincenzo Ciaglia
2007-02-15 19:12 ` Stephen Smalley
2007-02-15 19:23 ` Vincenzo Ciaglia
2007-02-15 19:31 ` Stephen Smalley
2007-02-15 19:58 ` Vincenzo Ciaglia
2007-02-15 20:03 ` Stephen Smalley
2007-02-15 20:23 ` Vincenzo Ciaglia
2007-02-15 20:34 ` Stephen Smalley
2007-02-15 20:42 ` Vincenzo Ciaglia
2007-02-15 20:56 ` Eric Paris [this message]
2007-02-15 20:59 ` Stephen Smalley
2007-02-15 21:53 ` Vincenzo Ciaglia
2007-02-15 21:01 ` Vincenzo Ciaglia
2007-02-15 21:47 ` Vincenzo Ciaglia
2007-02-16 12:16 ` Vincenzo Ciaglia
2007-02-16 15:13 ` Stephen Smalley
2007-02-16 16:44 ` Vincenzo Ciaglia
2007-02-16 17:04 ` Stephen Smalley
2007-02-16 17:52 ` Vincenzo Ciaglia
2007-02-16 17:55 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2003-05-07 16:02 Nick Gray
2003-05-07 17:43 ` Russell Coker
2003-05-07 19:03 ` Richard Troth
2003-05-07 18:09 ` Keith Bottner
2003-05-07 21:01 ` ccallen
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=1171572980.18488.30.camel@localhost.localdomain \
--to=eparis@parisplace.org \
--cc=SELinux@tycho.nsa.gov \
--cc=sds@tycho.nsa.gov \
--cc=vin@netwosix.org \
/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.