[opensuse] changing a user passwd via root (13.2: Authentication token manipulation error (?))
Having an odd experience here, in that I wanted to create another userid to test something with. Noticed I already had a testid for that purpose, tried to use it but password was invalid. So went to reset it with sudo passwd testuser and expected it to ask for new passwd and to repeat it. Instead I got: passwd: Authentication token manipulation error passwd: password unchanged Anyone know why I might get this and how it should be fixed? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 2016-10-30 03:09, L. A. Walsh wrote:
Anyone know why I might get this and how it should be fixed?
The procedure I use is:
su - passwd someuser
Tried that as well, same same... :-( -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 30/10/2016 à 07:21, Linda Walsh a écrit :
Carlos E. R. wrote:
On 2016-10-30 03:09, L. A. Walsh wrote:
Anyone know why I might get this and how it should be fixed?
The procedure I use is:
su - passwd someuser
Tried that as well, same same... :-(
may be this user was not or is no more correctly setup. AFAIK, the user setup is in /etc/passwd, /etc/shadow and /home. As a poor fix, you can probably remove this user lines in these two files. If the user folder in /home do not exists, simply recreate the user. If you have the folder in /home, list the UID of this user and recreate it with the same UID. dirty but may work :-( jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd wrote:
As a poor fix, ... dirty but may work :-(
I was able to work around the problem, but that doesn't explain why passwd would fail or how it *could* fail. If I am root, how can it fail before anything is typed? Looking around on the web, I only see references to that message w/r/t a user typing the wrong passwd to change their own password -- amusingly, it was said that becoming root could be used to fix the problem if the user's password didn't work or had been forgotten, since such a problem can't affect root which should never get the error. ??? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 30 Oct 2016 03:14:52 -0700 Linda Walsh wrote: 8< - - - - - trimmed - - - - - >8
I was able to work around the problem, but that doesn't explain why passwd would fail or how it *could* fail. If I am root, how can it fail before anything is typed?
Looking around on the web, I only see references to that message w/r/t a user typing the wrong passwd to change their own password -- amusingly, it was said that becoming root could be used to fix the problem if the user's password didn't work or had been forgotten, since such a problem can't affect root which should never get the error.
???
Wrong permissions (ACLs?) or corrupted file, or filesystem corruption underlying a corrupted file? :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zondag 30 oktober 2016 07:37:39 schreef jdd:
Le 30/10/2016 à 07:21, Linda Walsh a écrit :
Carlos E. R. wrote:
On 2016-10-30 03:09, L. A. Walsh wrote:
Anyone know why I might get this and how it should be fixed?
The procedure I use is:
su - passwd someuser
----
Tried that as well, same same... :-(
may be this user was not or is no more correctly setup.
AFAIK, the user setup is in /etc/passwd, /etc/shadow and /home.
Also /etc/group is involved. Did you try the yast module for user accounts?
jdd
-- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
L. A. Walsh wrote:
Having an odd experience here, (what else is new?)
Compiled the file w/debug and traced it -- died with bogus error message when it tried to verify the user in winbind. Cause -- user was in /etc/passwd, group/ shadow, but the were not in samba's DB, so it didn't recognize the user as a valid user, even though other parts of pam recognized the userid (thus the weird error messages)... Adding the user to samba (w/ net rpc user add 'username') was the main "correction"... after that a bit of cleanup (like reseting the UID/GID to previous values, unlocking account, and setting old PW...etc. "good as new" ;-))... Sigh.. been a while since I added a user and forgot samba's requirements... Thanks for the brainstorming & ideas...got me to install all the related debug and go that route, since I didn't really know where, exactly, it was failing... Thanks again! -linda -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Carl Hartung -
Carlos E. R. -
Freek de Kruijf -
jdd -
L. A. Walsh -
Linda Walsh