From: James Antill <jantill@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: gnuTAR support for SELinux context (beta)
Date: Tue, 01 Aug 2006 15:02:19 -0400 [thread overview]
Message-ID: <1154458939.2103.69.camel@code.and.org> (raw)
In-Reply-To: <1154456909.3582.139.camel@moss-spartans.epoch.ncsc.mil>
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
On Tue, 2006-08-01 at 14:28 -0400, Stephen Smalley wrote:
> On Tue, 2006-08-01 at 13:27 -0400, James Antill wrote:
> >In a similar vein
> > you can ignore any selinux context information by using --no-selinux
> > when you extract, or --no-xattrs to ignore all xattr information.
> What about just saving the selinux contexts by default if they are
> present on the files being archived (and likewise extracting them by
> default if present in the archive)? Otherwise, users have to take
> explicit action to save and restore the file contexts and will continue
> to "lose" them by default.
Note that --xattrs is on by default for extracting, you have to use the
--no-* varients to not extract that info. from the archive. So if you
pass --selinux or --xattrs on the create command line, it just works.
There are backwards compatibility concerns with enabling even --selinux
by default for creating archives (older versions of GNUtar will spew
warnings, and give error exit codes).
It's also not obvious it should happen, consider files created in /tmp
and tar'd ... extracting them with tmp_t is probably not what you want.
Dito things like untar'ing an archive of html in /var/www/html (on the
other hand, untar'ing php will only ever work if it has the right
context in the archive).
--
James Antill <jantill@redhat.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-08-01 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 17:27 gnuTAR support for SELinux context (beta) James Antill
2006-08-01 17:40 ` Stephen John Smoogen
2006-08-01 18:28 ` Stephen Smalley
2006-08-01 18:50 ` Stephen John Smoogen
2006-08-01 19:19 ` James Antill
2006-08-01 19:02 ` James Antill [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=1154458939.2103.69.camel@code.and.org \
--to=jantill@redhat.com \
--cc=sds@tycho.nsa.gov \
--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.