All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erich Schubert <erich@debian.org>
To: "J. Simonetti" <jsimonetti@denit.net>,
	"SELinux@tycho.nsa.gov" <SELinux@tycho.nsa.gov>
Subject: Re: rsync resetting contexts in /var/www
Date: Wed, 05 Apr 2006 23:36:57 +0200	[thread overview]
Message-ID: <1144273018.19128.68.camel@wintermute.xmldesign.de> (raw)
In-Reply-To: <1144259773.25790.102.camel@moss-spartans.epoch.ncsc.mil>

Hi,
> issue or not.  In the absence of -X, rsync should just be creating the
> new files with the default behavior, i.e. they should just inherit from
> the parent directory.

rsync writes data to temp files first, then renames them to their final
name IIRC. So even if you replace files with files from a remote machine
they'll probably get the default contexts again, just by not replacing
the existing ones, but actually being "moved in place" of the old files.
That is a sane behaviour, since network connections might be unstable
and you'll have intact files all the time that way. You could maybe
patch rsync to restore the old files label onto the new file, but I'm
not sure if that is the right way to do it.
I'm not a selinux "behaviour" expert, so what I just wrote might be
incorrect.

best regards,
Erich Schubert
-- 
   erich@(vitavonni.de|debian.org)    --    GPG Key ID: 4B3A135C    (o_
                Friends are those who reach out for                 //\
                  your hand but touch your heart.                   V_/_
      Alles verändert sich, sobald man sich selber verändert.



--
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:[~2006-04-05 21:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-05 10:50 rsync resetting contexts in /var/www J. Simonetti
2006-04-05 17:56 ` Stephen Smalley
2006-04-05 21:36   ` Erich Schubert [this message]
2006-04-06  7:58     ` J. Simonetti

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=1144273018.19128.68.camel@wintermute.xmldesign.de \
    --to=erich@debian.org \
    --cc=SELinux@tycho.nsa.gov \
    --cc=jsimonetti@denit.net \
    /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.