Jira (PUP-229) User provider password_max_age attribute is flawed under Solaris

[Adrien Thebo (JIRA)]

Title: Message Title

Adrien Thebo commented on an issue   Re: User provider password_max_age attribute is flawed under Solaris Verified: Against 3.6.2: bash-3.2# bundle exec puppet apply /foo.pp --verbose Notice: Compiled catalog for solaris-10u11-i386-vbox4210-nocm in environment production in 2.32 seconds Info: Applying configuration version '1408395629' Notice: /Stage[main]/Main/User[vagrant]/password_max_age: password_max_age changed '' to '-1' Notice: Finished catalog run in 0.22 seconds Against 9953b2c67009013894dcd0bcd5fb11409be16f02: bash-3.2# bundle exec puppet apply /foo.pp --verbose Notice: Compiled catalog for solaris-10u11-i386-vbox4210-nocm in environment production in 2.44 seconds Info: Applying configuration version '1408395694' Notice: Finished catalog run in 0.11 seconds Add Comment   Puppet / PUP-229 User provider password_max_age attribute is flawed under Solaris A user reported this, and did an excellent write up of the issue and a possible fix, so I'm just going to paste that: The password_max_age logic is flawed on Solaris. At first, it seems to work: {noformat} # tail -1 /etc/passwd foobar:x:911:911::/home/foobar:/bin/sh # tail -1 /etc/shadow foobar:GI2XGzW0DitJk:15931::182:28::: {noformat} E... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.