when i run CSF security check i get
Check /tmp ownershipWARNING/tmp should be owned by root:root
the /tmp seems to be set to nobody:nobody
Is it a Security Risk.?
Other options are set fine on /tmp
Check /tmp permissionsOK
Check /tmp is mounted as a filesystemOK
Check /tmp is mounted noexec,nosuidOK
running centos + cpanel and Apache 1.3.x
Does anyone here know who owns Rackedge NL? Are they a member of this forum? I am having a real bad problem, that certainly defy's logic and reason and i can’t seem to get any replies from either member McRox or the Support team.
Rather than posting wildly around the net about them and this issue, I would prefer to first ensure this isn’t just a big misunderstanding, so any details anyone can offer on this.
There is only 3 people i have been in contact with in this company
McRox (Member of this forum)
Tony Deeman (Support)
John de Groot (Sales)
I have it setup and have a user created that can upload files to my website.
The problem that I am running in to is that the files that this user uploads are owned by him not the cpanel website user. Thus when I try to view the page in my browser I get a server 500 error since the site is set to only serve up pages that are owned by the cpanel website user.
When using FTP in the same way we did not have this problem as the file that was uploaded would automatically be owned by the cpanel website user.
i got a unmanaged vps and i do not know why i often see folders and files ownership belonging to apache instead of myself and i have to manually reset ownership via directadmin file manager or ssh in to do it....can anyone advise me how to fix this problem as in anything i can do to stop all these apache ownership problem...
Another thing about directadmin, i select all folders and files at once trying to reset ownership but i always get an error and have to reset ownership one by one wasting time....
One of my customers wants me to change the ownership to nobody and group to apache in a directory created in the home directory of his website. I want to know whether doing so will pose any security problem. Also is there any advantage of changing the owner to nobody and group to apache?
View 11 Replies View RelatedFreeBSD 7.0
Apache 2.2
PHP5
Mysql 5.1
I have been battling this for a while. A user will setup a CMS like joomla, e107, etc and every time the CMS changes files either with user interaction on the website or the admin changing things in their cms admin web page, apache takes ownership of the files.
I have tried installing suPHP, FastCGI, and most recently suexec. I am not having any luck with this. I really don't know what I am doing with these recent additions but meanly going on suggestions. Does anyone know of a walk through to fix this permission problem? Anyone with some good advise? Surely not everyone is having to write a script to chown each user's dir and run a cronjob every 5 minutes.
I'm Running (just) Direct Admin On a Centos 4.3
Due to a typo at the comand line as Root, ive manages to change the owner ship of unknown mounts of files.
The command that was processed (Before it was complete)
chown -R reseller:reseller /
I managed to stop the process ctr+c
and these were the last files to see fly past.
The last one in the list is where it stopped at.
Code:
chown: changing ownership of `/proc/11566/task/11566': Operation not permitted
chown: changing ownership of `/proc/11566/task/11566/fd/0': No such device or address
chown: changing ownership of `/proc/11566/fd/0': No such device or address
chown: changing ownership of `/proc/11572': Operation not permitted
chown: changing ownership of `/proc/11572/task/11572': Operation not permitted
chown: changing ownership of `/proc/11572/task/11572/fd/4': No such file or directory
chown: changing ownership of `/proc/11572/task/11572/cwd': Operation not permitted
chown: changing ownership of `/proc/11572/fd/4': No such file or directory
chown: changing ownership of `/proc/11572/cwd': Operation not permitted
chown: changing ownership of `/etc/X11/X': No such file or directory
chown: changing ownership of `/dev/core': Operation not permitted
chown: changing ownership of `/usr/local/include/libpng/libpng12':
Too many levels of symbolic links
At the moment the server is still running and it seems only to be log in issues with Direct admin. All user / reseller / Admin accounts can no longer log in.
Error after logging in : Unable to determine Usertype user.conf needs to be repaired
No images or nothing
I have to mass change the ownership of accounts and I find "Change Owner of Multiple Accounts" tedious.
I found a bash script but I'm not sure if this works
Quote:
#!/bin/bash
IFS="$"
cd /var/cpanel/users
if [ $# = 2 ]; then
replace "OWNER=${1}" "OWNER=${2}" -- /var/cpanel/users/*
else
echo "USAGE: ./${0} <old reseller login> <new reseller login>"
fi
If that works, how can I tweak it so that the change in ownership of accounts will be based in the hosting package and not in the old reseller account?
When I have checked the 'Current CPU Usage' in root WHM there was a stranger IP with root ownership and command: whostmgrd - serving xxx.xxx.xxx.xxx
Also there was my IP with this ownership and command, like every time I am viewing the WHM.
I have blocked this IP with apf immediately, and the root password is changed.
Does it mean someone was in root WHM?
I have a dedicated server with cpanel on centos 4.6 / chkrootkit and rkhunter / all of server's softwares are up to date / compilers disabled for users / php open base dir is enabled and my users do not have SSH access.
Am I correct the r1soft does not preserve permission/ownership?
View 5 Replies View RelatedI have a software program on my home PC that writes to files on my remote VPS every few minutes.
The only way I can accomplish this is to CHMOD the files to 777 and give the whole world write priveledges.
Is there a way I can give my external (home) IP address write priveledges to certain files on my VPS without CHMODing them as 777?
I run the latest version of cPanel and WHM on my VPS.
run a command on /var/git to set rights and onwer without being cautious enough.I have run chown git:git .* -R which did not only run direction downwards the tree but upwards as well :-(
Any way to reset permissions and ownership for the directories back to standard?I tried /usr/local/psa/bin/repair already. Did lot of the fixes, but not all is in line yet.