The idea behind setting /etc/shadow permissions to 000 is to protect that file from being accessed by daemons, even when running as root, by ensuring that access is controlled by the DAC_OVERRIDE capability. Since Fedora 12 and RHEL 6, Fedora-based systems run daemons without DAC_OVERRIDE, but grant DAC_OVERRIDE to administrator login sessions (so that the ...
The “setting” is that root and toor have user id 0, which is what determines that it’s the superuser.
This is alluded to by the title of this FreeBSD FAQ entry, “What is this UID 0 toor account? Have I been compromised?”
Your user's PATH environment variable does not contain the path where these files are located. When you use su -, root's environment variables get loaded into your session. See man su:
-, -l, --login
Start the shell as a login shell with an environment similar
to a real login:
o clears all the environment variables ...
You can either add this to /etc/bash.bashrc or edit /etc/profile/
if [ "$LOGNAME" = root ] || [ "`id -u`" -eq 0 ] ; then
and you will get a prompt that looks like this. If you use a white ...
Make sure every user has a unique user ID, and all the environment variable definition scripts are not set to overwritte user ID.
Compare the outputs of id user1 and id user2.
Check the folders where environment variables are defined.
Edit /etc/passwd and /etc/group files if permission/ID issues show up. Make sure to read the docs of both files. Docs at: /...
Okay, so after twinkering with the system, I managed to get it running.
This is what I did:
Entered in recovery mode (I am using VM)
From then, I opened nano /etc/passwd (I dont know why it let me edit it, because It still wouldn't let me enter my password). I will be thankfull if someone explained that to me.
Root access queired to something q: (which was ...