From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: different selinux file-context root
Date: Tue, 10 Aug 2004 13:45:47 +0100 [thread overview]
Message-ID: <20040810124547.GC4647@lkcl.net> (raw)
In-Reply-To: <1092081142.29199.194.camel@moss-spartans.epoch.ncsc.mil>
On Mon, Aug 09, 2004 at 03:52:23PM -0400, Stephen Smalley wrote:
> On Mon, 2004-08-09 at 15:57, Luke Kenneth Casson Leighton wrote:
> > i'm thinking of doing installs of selinux systems and online
> > backups/restores from an initial ramdisk.
> >
> > e.g. modifying rsync to cope with selinux file contexts.
> >
> > e.g. there are several backup programs that create bootable CDs, that
> > then redo the entire system.
> >
> > what would make sense is for rsync, star etc. to have a context-"chroot"
> > under which the selinux file contexts get recreated relative to that
> > directory as the root filesystem.
> >
> > then i don't have to mess about ensuring that the entire filesystem
> > is correctly there and then doing something like this:
> >
> > chroot /mnt-point make -C /etc/selinux/src relabel
>
> setfiles has a -r rootpath option (contributed by the Gentoo folks) that
> causes it to strip the specified rootpath prior to matching against
> file_contexts.
great!
> Or, if using matchpathcon() directly, you can always
> have the caller strip the rootpath itself prior to invoking
> matchpathcon().
yukk :)
l.
--
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.
prev parent reply other threads:[~2004-08-10 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 19:57 different selinux file-context root Luke Kenneth Casson Leighton
2004-08-09 19:52 ` Stephen Smalley
2004-08-10 12:45 ` Luke Kenneth Casson Leighton [this message]
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=20040810124547.GC4647@lkcl.net \
--to=lkcl@lkcl.net \
--cc=sds@epoch.ncsc.mil \
--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.