This can also be done by booting in to runlevel 1. Just a '1' to the and of the kernel line in grub or at the grub prompt,
CC On Sat, Feb 27, 2010 at 7:18 AM, Keith Bailey <[email protected]> wrote: > Thank you very much! > > That did the job. > > On Fri, Feb 26, 2010 at 4:52 PM, Brian Wheeler <[email protected]> wrote: >> >> On Fri, 2010-02-26 at 16:45 -0600, Keith Bailey wrote: >> > I've been setting up ssh key authentication for our development server >> > and managed to configure a normal linux user account to work with two >> > client machines in the office. >> > >> > For enhanced security I locked the normal account with "passwd -l >> > user" so I could only access the account with ssh key authentication. >> > But I also unwittingly did the same for root. >> > >> > Now I'm unable to access the root user and can only access the normal >> > user through ssh key authentication. >> > >> > Is there a solution for this without a total re-install? >> >> One way to do it is to boot the rescue cd and chroot to your install. >> Once you're there you can run passwd to fix your file. >> >> >> >> >> > _______________________________________________ >> > rhelv5-list mailing list >> > [email protected] >> > https://www.redhat.com/mailman/listinfo/rhelv5-list >> >> >> _______________________________________________ >> rhelv5-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/rhelv5-list > > > _______________________________________________ > rhelv5-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/rhelv5-list > > -- RHCE#805007969328369 _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
