One more thing - Puppet will fail to set the password unless the libshadow gem is present, as this is required to work with shadow passwords.
The failures due to this being missing weren't obvious if I remember back - you only get a warning that the user provider isn't able to manage the passwords if you're running in debug mode. Ryan On Aug 3, 1:35 am, Len Rugen <lenru...@gmail.com> wrote: > You aren't sending the password, you are sending the "shadow". On one > system, set the desired password, get the shadow value, put that in puppet. > > [root@localhost ~]# passwd student > Changing password for user student. > New password: > BAD PASSWORD: it is too simplistic/systematic > Retype new password: > passwd: all authentication tokens updated successfully. > [root@localhost ~]# grep student /etc/shadow > student: > $6$PVOar6qN$WUTN7HG838PnAdzLYCB4HHVSzE/SX100VVdsiIYlBo7TM5c79R38gx942Lkm710 > v1HMRmS5VnPbHZ2MwY96wt0 > :15189:0:99999:7::: > [root@localhost ~]# > > In puppet, passwd => " > $6$PVOar6qN$WUTN7HG838PnAdzLYCB4HHVSzE/SX100VVdsiIYlBo7TM5c79R38gx942Lkm710 > v1HMRmS5VnPbHZ2MwY96wt0", > > This if from memory, so not syntax checked. That hash is for a password > that was simple and got the gripe. > > Of course, you will have to install and configure puppet on all of your > systems. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
