From: "Clarkson, Mike R \(US SSA\)" <mike.clarkson@baesystems.com>
To: "Glenn Faden" <Glenn.Faden@sun.com>,
"Daniel J Walsh" <dwalsh@redhat.com>
Cc: "Murray McAllister" <mmcallis@redhat.com>,
"SE Linux" <selinux@tycho.nsa.gov>
Subject: RE: user guide drafts: Maintaining SELinux Labels
Date: Wed, 8 Oct 2008 10:05:43 -0700 [thread overview]
Message-ID: <738m08$no37d@dmzms99802.na.baesystems.com> (raw)
> -----Original Message-----
> From: owner-selinux@tycho.nsa.gov [mailto:owner-selinux@tycho.nsa.gov]
On
> Behalf Of Glenn Faden
> Sent: Wednesday, October 08, 2008 8:46 AM
> To: Daniel J Walsh
> Cc: Murray McAllister; SE Linux
> Subject: Re: user guide drafts: Maintaining SELinux Labels
>
> Daniel J Walsh wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Murray McAllister wrote:
> >
> >> Hi,
> >>
> >> The following are the first few drafts of the "Maintaining SELinux
> >> Labels" sections. Any comments and corrections are appreciated.
> >>
> >> Cheers.
> >>
> >> Copying Files and Directories
> >>
> >> When files and directories are copied, they inherit the SELinux
context
> >> of the parent directory they are copied to. This helps ensure files
and
> >> directories are labeled with the correct SELinux context after
being
> >> moved. The following example demonstrates copying a file from a
user's
> >> home directory to /var/www/html/, which is used by the Apache HTTP
> >> Server. Since the file is copied, it inherits the correct SELinux
> context:
> >>
> Is this true when using MLS policy? Assuming the policy allows a
subject
> to create a file in a directory, shouldn't the newly created file's
> SELinux context have the same sensitivity as the subject who wrote it?
> Or is the new file's type copied from the directory and the
sensitivity
> copied from the subject?
You are correct, the type is copied from the directory and the level is
copied from the subject. It might also be worth mentioning that the type
is copied from the directory as default behavior, which can be
overridden with type_transition statements.
>
> --Glenn
>
> --
> 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.
--
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 reply other threads:[~2008-10-08 17:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 17:05 Clarkson, Mike R (US SSA) [this message]
[not found] <737og9$5vh3i@dmzms99902.na.baesystems.com>
2008-10-09 0:26 ` user guide drafts: Maintaining SELinux Labels Murray McAllister
2008-10-10 12:55 ` Stephen Smalley
2008-10-11 4:15 ` Murray McAllister
2008-10-11 11:17 ` Russell Coker
2008-10-11 23:44 ` Murray McAllister
2008-10-12 2:02 ` Russell Coker
2008-10-14 14:18 ` Stephen Smalley
2008-10-14 19:46 ` Russell Coker
2008-10-14 19:53 ` Stephen Smalley
2008-10-12 6:18 ` Murray McAllister
2008-10-14 14:15 ` Stephen Smalley
2008-10-15 1:30 ` Murray McAllister
2008-10-15 12:45 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2008-10-08 2:45 Murray McAllister
2008-10-08 14:54 ` Daniel J Walsh
2008-10-08 15:46 ` Glenn Faden
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='738m08$no37d@dmzms99802.na.baesystems.com' \
--to=mike.clarkson@baesystems.com \
--cc=Glenn.Faden@sun.com \
--cc=dwalsh@redhat.com \
--cc=mmcallis@redhat.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.