[clue-tech] should'a seen that coming...

[David L. Willson]

Actually couldn't authenticate as 'kadmin', the new username, or
'k3admin', the old username.  'kadmin' didn't have an entry
in /etc/shadow ('k3admin' did, but he had no entry in /etc/passwd),
therefore no hashed password, therefore no way to authenticate, unless
I'd setup password-less logins over ssh, or something, which I hadn't.

Not that 'kadmin' was in the 'admin' group that was in sudoers, either,
but that was a failure level I never got to reach.  Rebooting it was,
and then I ran into the group-membership problem, and then I backed the
change out because I was tired of the fun, at least on a production
system.

Maybe I'll try it on my laptop, instead...  :-)

On Thu, 2007-09-13 at 21:23 -0600, David L. Anselmi wrote:
> David L. Willson wrote:
> > I type 'sudo vipw' to change my username, the system prompts me that I
> > probably want to 'sudo vipw -s' to make /etc/shadow consistent
> > with /etc/passwd, so I do... or rather, I don't, because now my username
> > in one is different than in the other, so I can't authenticate any more.
> 
> I'd guess that it's not a problem with passwd and shadow, but that your 
> new user name isn't in sudoers.
> 
> Normally you'd use root to fix something like that.  But you turned root 
> off, didn't you?
> 
> So then you've got the usual getting around being locked out of root, 
> that probably require a reboot.  Unless you have another user in sudoers.
> 
> Good luck.
> Dave
> _______________________________________________
> clue-tech mailing list
> clue-tech at cluedenver.org
> http://www.cluedenver.org/mailman/listinfo/clue-tech