I have read that although chained root ssl certificates can be more difficult to install they are actually more secure since the root certificate cannot be compromised, only the intermediary.
Is this true? It looks like both google and amazon both use chained SGC certs.
what is difference working as root and su root in SSH.?
Many recommend disabling logging as root, but lot many commands ( service, adduser, ifconfig and ...) are not working on the commandline under when logged as su. i feel like my hands are tied working as su root and many commands are not available.
why is it like that? is there any way i can feel comfortable logging as su similar like root login.
I just recently had someone from this forum install CentOS for me with ISPconfig and required modules to successfully run PHPmotion. However, the only FTP I can access are the ones I create FTP for in ISPconfig, such as web1_admin, web1_testuser, etc.
When installing a CentOS server with ISPconfig, isn't there a root to log into the FTP?
With the FTP accounts that I have, I cannot access public and home directory such as /var/www directories.
Is there suppose to be an account for FTP so I can succcessfully overlook the whole server?
I want to take a look at all the websites I have such as /var/www/www.test1.com, /var/www/www.test2.com, etc. all through FTP. However, I cannot do this. It's almost like I have no Admin power over my server.
He did not provide me with a root FTP account or any super admin FTP account. I am not sure if something suspicious is going on or not. Please help. I do not want to get hacked in and stolen files.
I have a problem that after i su to root, i can't use some commands:
Quote:
Last login: Fri Jul 13 10:38:55 2007 from 10.10.0.1 [admin@server ~]$ su Password: [root@server admin]# runlevel bash: runlevel: command not found [root@server admin]# service httpd restart bash: service: command not found [root@server admin]# service apf restart bash: service: command not found
But when i come to that machine and log in, i can use those commands just fine. That machine is about 20 fts away from my desk.
I got into my root and i created a CS server BUT after closing my root from my home the cs server goes down. can u tell me how to fix this ? i cant keep my root open for a life time, how much bandwitch does a ful 20 man Pub use in a month average?
I have a server that I have a few domains on, and I have a question about the root domain. I initially picked any old domain, so now all of my name servers are pointing to this one random domain. I have since purchased a few more premium domains, and am wondering if I should change the nameservers to be the more premium domains? Does this matter? Should I have my "main site" be the root domain? Just trying to understand what the implications could be for me.
I have a VPS and have a problem regarding the SSL certificate cPanel uses for secure connections (webmail, WHM etc..) my original hostname was set to server.simschr.co.uk but then I changed it to another name. However on the SSL certificate it states the old hostname, which I have been told is a bit of a pain. I wondered if there was anyway to change the common name, maybe by editing the certificate on the server?
I set it to forward those emails to my email, it's not sending any. Does anyone have a clue why? I'm able to receive other emails from the server without any problems.
Am am running through a checklist of to-do's on a new VPS I just received. I haven't used it in a production environment yet.
While doing a root kit check I got these lines back that perturb me.
Checking `bindshell'... INFECTED (PORTS: 465) Checking `lkm'... You have 103 process hidden for readdir command chkproc: Warning: Possible LKM Trojan installed
how serious the implications are of those lines? And should I expect this on a machine that has no traffic and is a fresh install?
I have purchased a new domain name (.info) and am using a GoDaddy account to host it.
Currently I have a vBulletin forum on this account and the URL (.com) takes people directly to the forum index page as it should.
However, I have installed a new site for .info and it appears to be in root for the new domain (I guess this as the ftp client shows nothing in it when I connect to ftp.newdomain.info) but to access the new site I have to use:-
mysite.info/mysite/index.php
I don't want this, I want it to just be mysite.info to lead to the new site.
Can anyone help me with this please, my access to the ftp/host has been granted by my new partner, so prehaps he has set up my access incorrectly, but I just need to install the site into the root of the new .info domain.
I am just wondering whether my idea will work for the google search engine.
Basically, I have my official VPS root (home/admin/public_html/) and this is where my main website will be hosted. However, since my VPS will be used for additional website, I will direct additional domains to it.
My second site hosted on this VPS may have a document root of (home/admin/public_html/advertising/). And my domain will then be setup to have that as its document root.
However, when google searches for my second site (e.g. advertising.com) will it go 'below' the domain root? For example, will it also creep the files under /public_html/ for this domain, even though the domains root is /public_html/advertising/?
edit: Or do people host multiple sites differently? Is this an appropriate method?
This account is currently locked out because a brute force attempt was detected. Please wait 10 minutes and try again. Attempting to login again will only increase this delay. If you frequently experience this problem, we recommend having your username changed to something less generic.
direct root logon to a server is disabled; using another login, obviously. However, I need to be able to SFTP files from my computer to a directory on the server using said login - yet it does not have correct permissions, evidently, and therefore can't even see the directory I need to be able to SFTP files to.
Tried CHOWNing the directory with that usename, giving it 777 permissions, etc.
I'll try to make this long story short, but this morning I logged into one of my servers and it showed a read-only filesystem, which I thought my server guys could fix easily. So I put in a ticket. 6 hours later, they tell me that they think the OS is corrupted and I need a new install. They give me KVM over IP so I can go in and 'do' things. I tried to log in as root and it wouldn't let me, so they finally booted in single mode and I can get in and such. When I try to su - root, it tells me that user root can't be found. I also tried to ftp into and out of the server with no luck. I really need this box back up. If not, I need to get all the accounts saved off so that I can build a new box. Everything is there, so I don't want to give up yet.
I'm still trying to figure this one out. I got an email last night about 10:30pm that a weird IP had logged with root. I thought it was a guy that helps with tech things but I ran the IP... it came back from Korea and I knew I was in trouble. I immediately logged into WHM and changed the root password then sent the server down for a reboot. He was only in there for about 3 minutes before I nailed him. I've banned the IP from the server and have been watching it for nearly 12 hours now and they haven't came back yet.
Now comes the task of trying to figure out how he got the password. This is mind boggling to me. He knew the password, like someone gave it to him... there were no incorrect guesses or brute force. The password was a series of random letters, both upper and lower case. Is it possible he got it through getting to /etc/passwd via a PHP script? I have open basedir restrictions in place, can they get around that? I noticed at the time he logged in there were several IPs trying to exploit PHP scripts on my server, you know, setting the parameters to txt files but I assumed with shell functions disabled (except exec) and with open basedir this wouldn't be possible. Is there a hole in cpanel / PHP / kernel recently I may have missed?
