search for: pwunconv

...that they need to know about, in the sense of, "if you understand these commands, you should be fine." regarding user/group admin, my tentative list of commands would be: * user{add,mod,del} * group(add,mod,del} * passwd, gpasswd * chage, chsh, chfn * pwck, grpck * pwconv, pwunconv not sure what i'm missing here, i just typed those off the top of my head. rather than scatter all of that over an entire chapter, are there any official centos/rhel reference sheets like that? if not, i can just write my own and post them at my wiki. thanks for any pointers. rday -- ==...

...undef PAM_TTY_KLUDGE */ /* #undef HAVE_OLD_PAM */ /* #undef HAVE_PAM_GETENVLIST */ /* #undef HAVE_PAM_PUTENV */ Some more info on the PAM_LDAP library used on the system. When Shadow password bundle is installed on the system, shadow file enable and disable command is installed on "/usr/sbin/pwunconv" and "/usr/sbin/pwconv". PAM_LDAP library checks this and particularly when "/usr/sbin/pwunconv" is removed, LDAP auth works. Is there any chance that the problem is in checking the return status of the PAM APIs in 3.7.1p2? I have attached the "sshd -ddd" file w...

If shadow passwords are already in use, and new entries are appended to /etc/passwd that include password hashes, is it still possible to use pwconv to generate /etc/shadow entries for just the few newly appended accounts? Regards, Eugene

So on a virtual server the root password was no longer working (as in I couldn't ssh in anymore). Only I and one other know it and neither of us have changed it. No other account had the correct privileges to correct this so I'm wondering, if I had mounted that vdi as a secondary device on another VM, browsed the file system and delete /etc/shadow would this have wiped all users passwords