From: Murray McAllister <mmcallis@redhat.com>
To: russell@coker.com.au
Cc: Daniel J Walsh <dwalsh@redhat.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: user guide drafts: Archiving Files with tar/star
Date: Fri, 10 Oct 2008 12:08:28 +1000 [thread overview]
Message-ID: <48EEB91C.4080205@redhat.com> (raw)
In-Reply-To: <200810101251.30094.russell@coker.com.au>
Russell Coker wrote:
> On Friday 10 October 2008 10:30, Murray McAllister <mmcallis@redhat.com>
> wrote:
>>> tar xvf file.tgz | restorecon -f -
>>>
>>> Would reset the file context on disk after the extraction.
>> Does this only apply to the tar file itself, not the files in it? On
>> rawhide the extracted files (that have extended attributes) inherit the
>> type of the directory they are being extracted in.
>
> The "v" option of tar causes it to list on stdout all the files it extracts.
>
> The -f- option of restorecon makes it take a list of files to relabel on
> stdin. So it relabels all files extracted from the tar file.
>
> The inheriting of file contexts from a directory (in the absence of policy
> rules specifying otherwise) has AFAIK always been the design of SE Linux.
When would "tar | restorecon -f -" be used if files inherit contexts
from parent directories (if policy has not be changed)? Sorry, I am a
bit slow :)
--
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:[~2008-10-10 2:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 7:08 user guide drafts: Archiving Files with tar/star Murray McAllister
2008-10-09 11:49 ` Daniel J Walsh
2008-10-09 23:30 ` Murray McAllister
2008-10-10 1:51 ` Russell Coker
2008-10-10 2:08 ` Murray McAllister [this message]
2008-10-10 2:36 ` Russell Coker
2008-10-10 12:57 ` Stephen Smalley
2008-10-11 6:13 ` Murray McAllister
2008-10-13 18:07 ` Daniel J Walsh
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=48EEB91C.4080205@redhat.com \
--to=mmcallis@redhat.com \
--cc=dwalsh@redhat.com \
--cc=russell@coker.com.au \
--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.