I am running appache httpd-2.0.54-10.3 on a Fedora Core 4 with SELinux enabled. As root, I just installed some new files on my server. I was surprised to notice that the files had their permissions set like this:
-rw-r--r-- 1000 users rootbject_r:httpd_sys_content_t some_file.php

This is not the default apache user and I am not familiar with this user / group. What should be the default settings for a file I untar as root in my httpd root directory? For example, is their a safe command that I could use to conveniently like chcon -t httpd_sys_content_t /var/www/html/*

To troubleshoot this problem on my own, I did the following:

I did a find / -uid 1000 > 1000.txt. My results included an error message like this

Except for this error message, these files returned were all created in the account where I am allowed to login into my box and then su as root (no remote root logins are allowed). The UID, however, is not the UID of the user that is able to login (as I expected) and I know that root's ID is 0.

I did searched for this UID like this:
cat /etc/passwd |grep "/bin/bash" |grep "[0-9][0-9][0-9][0-9]" |cut -d: -f1

It returned my allowed login user.

cat /etc/passwd |grep "1000" |grep "[0-9][0-9][0-9][0-9]" |cut -d: -f1

It returned no results.

Any help would be appreciated.

Fedora 4 and RHEL4 both come configured for Security Enhanced Linux (SELinux) out of the box. SELinux offers much greater security than standard Linux permissions but it's more of a pain to set up as well. It also uses different users than the standard Linux versions. Both permissions have to allow something to happen or it can't. So if SELinux says you can read and standard Linux permissions says you can read/write you can only read. SELinux uses mandatory access controls and runs almost all services in sandboxes. It offers a ridiculous amount of permissions you can set and you can set permissions on processes that spawn so they have their own access rights even after being started by another service. Almost like passing it off. I don't however know enough about SELinux to really help you out, but outside of servers I don't believe it's necessary.