From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Sam Gandhi <samgandhi9@gmail.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: Is there difference betweek sefiles and restorecon in terms of labels
Date: Fri, 29 Apr 2011 10:01:44 -0400 [thread overview]
Message-ID: <4DBAC4C8.5050909@tresys.com> (raw)
In-Reply-To: <BANLkTi=23O4bO-mDgKectp3_xXpCOXFxmw@mail.gmail.com>
On 04/27/11 18:59, Sam Gandhi wrote:
> Looking at man pages of sefiles and restorecon , both mention that
> they initialize security context database ( extended attributes) on
> one or more filesystems.
>
> There are certainly differences between command line arguments, but
> can these programs be used interchangeably as far as extended
> attributes they assign to files?
They both use the system's file context specification from the policy
and should set the same file context on any given path (if not, its a
bug). The only difference between the two is their command line
arguments. Setfiles, and correspondingly its command line arguments, is
primarily for initializing a filesystem's labels. Restorecon is
oriented towards resetting the label on a file or a directory tree.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
--
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:[~2011-04-29 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 22:59 Is there difference betweek sefiles and restorecon in terms of labels Sam Gandhi
2011-04-27 23:30 ` Guido Trentalancia
2011-04-27 23:36 ` Guido Trentalancia
2011-04-29 14:01 ` Christopher J. PeBenito [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=4DBAC4C8.5050909@tresys.com \
--to=cpebenito@tresys.com \
--cc=samgandhi9@gmail.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.