From: Daniel J Walsh <dwalsh@redhat.com>
To: sds@tycho.nsa.gov
Cc: Valdis.Kletnieks@vt.edu, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Changes to policycoreutils.
Date: Mon, 20 Mar 2006 09:51:47 -0500 [thread overview]
Message-ID: <441EC183.6000404@redhat.com> (raw)
In-Reply-To: <1142862355.16487.7.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Sat, 2006-03-18 at 11:54 -0500, Daniel J Walsh wrote:
>
>> The answer is that is, if the file is created by a confined domain it
>> will be instantly. SELinux
>> aware application also create it instantly. This is more for the non
>> SELinux aware applicaitons.
>> So the example of the user creating the public_html directory.
>>
>> It happens very fast, as a matter of fact you can try this command to see it
>>
>> rmdir public_html; mkdir public_html; ls -ldZ public_html
>> drwxrwxr-x dwalsh dwalsh user_u:object_r:httpd_sys_content_t
>> public_html
>>
>> This should not be considered a failsafe security measure, but more of a
>> usability issue.
>> If you have an file that is of critical secuirty you might not want to
>> use this tool on it.
>>
>
> It shouldn't be applied to any directory writable by an untrusted entity
> (e.g. ~/public_html) unless you are taking some kind of safeguards to
> prevent it from being used as a way to relabel files outside the user's
> control via links.
>
>
Not sure what you mean. It is taking into account the users homedir.
And the file. If public_html was not a directory it would be labeled
user_home_t. I don't know how someone could cause the relabel to be a
problem. I guess if the administrator was to start to add files in
/tmp or ~/subdir/subdir/SecretFile. This could be a problem.
--
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 prev parent reply other threads:[~2006-03-20 14:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 21:39 Changes to policycoreutils Daniel J Walsh
2006-03-18 5:32 ` Valdis.Kletnieks
2006-03-18 16:54 ` Daniel J Walsh
2006-03-20 13:45 ` Stephen Smalley
2006-03-20 14:51 ` Daniel J Walsh [this message]
2006-03-20 15:51 ` Stephen Smalley
2006-03-20 17:25 ` Stephen Smalley
2006-03-21 19:12 ` Daniel J Walsh
2006-03-20 20:27 ` Russell Coker
2006-03-20 20:47 ` Stephen Smalley
2006-03-20 20:11 ` Stephen Smalley
2006-03-20 21:23 ` Daniel J Walsh
2006-03-20 21:45 ` Stephen Smalley
2006-03-21 13:56 ` Stephen Smalley
2006-03-21 16:13 ` Daniel J Walsh
2006-03-20 21:26 ` Stephen Smalley
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=441EC183.6000404@redhat.com \
--to=dwalsh@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=sds@tycho.nsa.gov \
--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.