
steve_zr wrote:It looks as though its a complete lockout, i cannot logon to the root account locally or remotely
I could try, how would i su or sudo?
I do apologize as i am a complete noob
Code: Select all
$ su -Code: Select all
$ sudo /bin/bashthat is what su is forsteve_zr wrote:Well unfortunately I haven't been given the su password so i cant do that, is there a way of upgrading another account to a root without the need for the root account or am i in trouble. We have a web page running on that server but i am unable to restart apache to get it running, can i do this without the root account?
does /usr/bin/rssh exist? and is it a valid shell..?steve_zr wrote:When i try using su it gives me a permission denied message, is this due to a wrong password or it is because of the /etc/passwd file for the root has been changed to /usr/bin/rssh instead on /bin/bash ?
Code: Select all
$ su -s /bin/basheasier than running su with a working shell and fixing it from there..?Hu wrote:The easiest way to fix this is to halt the machine, boot a LiveCD, and modify /etc/passwd using the LiveCD environment. You will be down for the duration, but it is straightforward and much less trouble than trying to find a security flaw in the current configuration.
Which will only workdowner wrote:easier than running su with a working shell and fixing it from there..?
true, but it is a good place to start, rather than bringing out the big guns at once, right?schachti wrote:Which will only work
* if there is another user account on that machine,
* if he knows the password of this account, and
* if this account is member of the wheel group.
I got the impression that he at least is able to login as a normal user, meaning the first 2 points are not really an issue and if he was following the install guide chances are the user is in wheel.Well unfortunately I haven't been given the su password so i cant do that, is there a way of upgrading another account to a root without the need for the root account or am i in trouble.
He is not following the installation guide. He has inherited a fully installed system. He does not have the root password. He does not have sudo access, as far as we know. The only way he can attain superuser access is to get the root password, to get into an account with sudo access, or to find some security flaw that can be exploited for a privilege escalation attack. I presume that he cannot get the root password or he would have done so by now. Similarly, I presume that sudo is not enabled for any user or he would have mentioned it.downer wrote:true, but it is a good place to start, rather than bringing out the big guns at once, right?schachti wrote:Which will only work
* if there is another user account on that machine,
* if he knows the password of this account, and
* if this account is member of the wheel group.
from what steve_zr wrote:I got the impression that he at least is able to login as a normal user, meaning the first 2 points are not really an issue and if he was following the install guide chances are the user is in wheel.Well unfortunately I haven't been given the su password so i cant do that, is there a way of upgrading another account to a root without the need for the root account or am i in trouble.
//D
Well, maybe the person who set it up did..? Someone gave him access to the computer, and we don't know if he has sudo access or not (from the looks of it, asking how to use sudo or su implies that he does not know himself), thus simply typing "su -" or "sudo bash" seemed like a logical first step to see if it worked, if it doesn't by all means, reboot the system.Hu wrote:He is not following the installation guide. He has inherited a fully installed system. He does not have the root password. He does not have sudo access, as far as we know. The only way he can attain superuser access is to get the root password, to get into an account with sudo access, or to find some security flaw that can be exploited for a privilege escalation attack. I presume that he cannot get the root password or he would have done so by now. Similarly, I presume that sudo is not enabled for any user or he would have mentioned it.
Finally, the fact that root is using rssh instead of sh or bash is not a good sign, and may impact his ability to administer the system even if he managed to run a shell as root. Therefore, I suggested using the LiveCD so that he could fix the shell at the same time as he changes the root password.