All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: russell@coker.com.au
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: restorecon -R default
Date: Mon, 30 Jan 2012 11:11:05 -0500	[thread overview]
Message-ID: <1327939865.23069.10.camel@moss-pluto> (raw)
In-Reply-To: <201201290001.10792.russell@coker.com.au>

On Sun, 2012-01-29 at 00:01 +1100, Russell Coker wrote:
> http://www.youtube.com/watch?v=ZThVfm3JXdM
> 
> A few years ago Paul Wayper gave an excellent introductory lecture about SE 
> Linux (see the above URL).  He notes that he habitually uses -R for restorecon 
> every time.
> 
> It seems to me that the case where -R is not desired will be extremely rare.  
> It seems most uncommon that someone will have a directory with the wrong 
> label, a subdirectory tree that is either too big to scan quickly (and which 
> is known to have the correct labels) or which has labels which by design don't 
> match the file contexts.
> 
> Therefore I think we should make the common case be the default and require 
> that anyone who doesn't want that functionality specifically request it.  
> chcon uses the -h flag for changing the context of a sym-link instead of the 
> target, that might be a reasonable option to use for consistency.

Seems like it might prove surprising to users, both given the prior
default behavior of restorecon and the default behaviors of similar Unix
commands like chown/chmod.  I don't think we can/should change it.

-- 
Stephen Smalley
National Security Agency


--
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.

  reply	other threads:[~2012-01-30 16:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-28 13:01 restorecon -R default Russell Coker
2012-01-30 16:11 ` Stephen Smalley [this message]
2012-01-30 18:32   ` 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=1327939865.23069.10.camel@moss-pluto \
    --to=sds@tycho.nsa.gov \
    --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.