Skip to contentSkip to conversation

fileutils

DISCUSSION Russell Coker 2 participants 2 messages Jul 27, 2002 – Jul 29, 2002 SELinux security module

lore
Share & tools
lore
#0 lore raw

I've put a new version of fileutils on
http://www.coker.com.au/selinux/fileutils/ . It is based on the latest version of fileutils, and I've made a few changes. I made cp and mv not try to preserve the context unless you specify it with -c for either program (cp also takes --preserve=context).

Also I updated the man page auto-generation to generate a manpage for chcon(1).

One final thing, I think that copy_s() in copy.c should be changed to use open_secure() instead of just calling the regular function. If we really want the context set on copy then the current setup allows for a race condition where a large file could potentially be read by an unauthorised process while it's being copied. Also could there be situations in which the user has permission to create a file in a particular type via open_secure() but not have permissions to change it to that type later?

Signature · 3 lines
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
Quoted 1 line

From field.

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.

#1 lore raw
Quoted 7 lines · Russell Coker

One final thing, I think that copy_s() in copy.c should be changed to use open_secure() instead of just calling the regular function. If we really want the context set on copy then the current setup allows for a race condition where a large file could potentially be read by an unauthorised process while it's being copied. Also could there be situations in which the user has permission to create a file in a particular type via open_secure() but not have permissions to change it to that type later?

I agree, and yes, the latter is a possible situation.

--
Stephen D. Smalley, NAI Labs
[email protected]

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.