[SOLVED] Authentication failure for root logins (Fedora 12)
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Authentication failure for root logins (Fedora 12)
Hey everyone,
I just got Fedora 12, and I used su root to change the bin ownership to my primary developer account. For some reason, though, all subsequent attempts to log in as root have had authentication failure, be it through su or through the startup login screen. This does NOT occur for adminstrator tools such as Groups and Users. Any ideas why this might be happening?
root login in fedora AND Gnome have been disabled on BOTH for the GUI
login as a normal user and use "su -" in the terminal
fedora DOSE need you to use " su -" and NOT " su " to use the root account .This is VERY well documented in the fedora docs http://docs.fedoraproject.org/
Don't change that ownership. If your 'primary dev' acct needs access, add that to his $PATH and/or add him to the relevant group.
You'll want this to reset the perms correctly: http://www.cyberciti.biz/tips/reset-...ermission.html
su root //Now I know that was a bad move!
chmod 775 /bin
The plot thickens, though: I reformatted the computer, and logged in as root again (this was before I posted the question.) This time, I didn't edit anything (just
Code:
su
'd into the computer), and then logged out. Interestingly, I was locked out of both
Code:
su root
and
Code:
su -
. What should I do to correct this, short of rebooting the whole machine?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.