Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-7600

user type accepts numeric usernames, but ssh_authorized_key does not

    Details

    • Type: Bug
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: sshkeys_core
    • Labels:
      None
    • Environment:

      CentOS 6.3 with PE 3.0.1

      Description

      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.

      [root@monkey ~]# puppet resource user 1970 ensure=present managehome=true
      Notice: /User[1970]/ensure: created
      user { '1970':
        ensure => 'present',
      }
      [root@monkey ~]# puppet resource ssh_authorized_key 1970 key='blah' type=ssh-rsa user=1970
      Notice: /Ssh_authorized_key[1970]/ensure: created
      Error: /Ssh_authorized_key[1970]: Could not evaluate: User '1970' does not exist
      Error: Could not run: No such file or directory - /home/1970/.ssh/authorized_keys
      [root@monkey ~]# ls -lhd /home/1970
      drwx------ 2 503 503 4.0K Nov  5 22:40 /home/1970
      

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Stefan Stefan Schulte
                Reporter:
                ben.ford Ben Ford
              • Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Zendesk Support