Jira (PUP-677) ssh_authorized_key can't handle numeric usernames

[Stefan Schulte (JIRA)]

Title: Message Title

Stefan Schulte commented on an issue   Re: ssh_authorized_key can't handle numeric usernames The manpage states Usernames must start with a lower case letter or an underscore, followed by lower case letters, digits, underscores, or dashes. They can end with a dollar sign. In regular _expression_ terms: [a-z_][a-z0-9_-]*[$]? So I don't think that numeric usernames is something puppet should be able to handle. Puppet will just assume it is a UID. Let's say you define user { "foo": uid => 100, gid => 100, } Now let's suppose if there is a group foo with gid 100 and also a group with the name 100? What should puppet do then? Add Comment   Puppet / PUP-677 ssh_authorized_key can't handle numeric usernames 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.