Jira (PUP-677) user type accepts numeric usernames, but ssh_authorized_key does not

[Stefan Schulte (JIRA)]

Title: Message Title

Stefan Schulte commented on an issue   Re: user type accepts numeric usernames, but ssh_authorized_key does not I agree that the user type should do stricter validation. But there is also the possibility that you create the user manually - and obviously some useradd implementations allow you to create a users that the man page states are invalid - and you now stumble across the ssh_authorized_key type that cannot handle the ssh keys of your manually created user. So while we cannot ensure that you don't have users that are purely numeric, I think we should not try to handle these cases. Again: I have nothing against stricter validations for the user type but I don't now if the "user should be non numeric" applies for all platforms (windows?) Add Comment   Puppet / PUP-677 user type accepts numeric usernames, but ssh_authorized_key does not A purely numeric username is a bit ridiculous, but it actually came up in a training class. A student assigned himself the username of '1970' and things blew up. Testing indicates that this resource type or provider cannot handle a numeric username. {code} [root@monkey ~]# puppet resource user 1970 ensure=present managehome=true Notice: /User[1970]/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/groups/opt_out.