Re: user guide drafts: Maintaining SELinux Labels

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Clarkson, Mike R (US SSA) wrote:

-----Original Message-----
From: owner-selinux@xxxxxxxxxxxxx [mailto:owner-selinux@xxxxxxxxxxxxx]
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
I've changed the first paragraph. How about:

When files and directories are copied, they inherit the SELinux context of the parent directory they are copied to[1]. This helps ensure files and directories are labeled with the correct SELinux context after being copied. Also, when a file is copied over an existing file, the existing file's context is maintained. On systems running the MLS policy, when files are copied, they inherit the type from the parent directory they are being copied to, and the level from the process that copied them.

Is the last sentence, is "the level from the process that copied them" correct? Should it be "from the process or user that..."?

[1] By default, the type is copied from the parent directory. This behavior can be overridden by using type_transition statements in custom SELinux policies.

I've included an example at the end of the section to show copying a file over an existing one.

Thanks for your feedback.

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.

[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux