Jira (PUP-2621) ssh_authorized_keys should not use the key 'comment' as a unique identifier (name)

[JIRA]

Title: Message Title

Paul Tötterman commented on an issue   Re: ssh_authorized_keys should not use the key 'comment' as a unique identifier (name) I ran into problems with this as well, trying to enable access using the same ssh key to different accounts: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Cannot alias Ssh_authorized_key[ldap_ssh_key_username_0] to ["usern...@domain.com"] at /etc/puppet/production/modules/users/manifests/admin.pp:22; resource ["Ssh_authorized_key", "usern...@domain.com"] already declared at /etc/puppet/production/modules/users/manifests/admin.pp:22 at /etc/puppet/production/modules/users/manifests/admin.pp:22 on node hostname Add Comment   Puppet / PUP-2621 ssh_authorized_keys should not use the key 'comment' as a unique identifier (name) Currently the ssh authorized keys provider uses the 'comment' section from an SSH public key as the 'name'. However, this implies that these comment strings must be unique, while SSH itself imposes no such restriction: in fact, it often happens that users generate both an RSA and a DSA key, which by default will have the same comment. A better 'name' f... 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.