On Aug 31, 4:06 pm, Andrew Shafer <and...@reductivelabs.com> wrote:
> git blame
>
> I am the culprit.
>
> The only provider that does passwords this way is user_role_add on
> Solaris. If you are not using Solaris, you are not running that code.
>
> The rational at the time was, useradd/mod do not support the password
> parameter on Solaris and libshadow for Ruby is an unmaintained
> project, difficult to build and without upstream support as a package
> on the platform.
>
> I might be naive about something, as this project was essentially my
> introduction to Solaris, but I had some input from others with more
> experience on Solaris.
>
> If someone can suggest 'OS utilities' that don't also introduce clumsy
> dependencies, I'd be happy to help integrate the change.
>
> Regards,
> Andrew
Andrew,
Makes sense, thanks.
I'm still a little baffled by where the actual shadow file management
is happening for non-Solaris OS's (we use Debian primarily). I'm even
more baffled by the dependency requirement for ruby_shadow to manage
this (regardless of its unmaintained state), if it's not being used.
If the dependency is there, and it is actually being used in some
capacity, then I'm hoping it should be relatively straight forward to
add one or two lines to set the last_changed parameter when calling
the libshadow function. Can you point me in the right direction?
Thanks,
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
