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

[Alan Stebbens (JIRA)]

Title: Message Title

Alan Stebbens commented on PUP-2621   Re: ssh_authorized_keys should not use the key 'comment' as a unique identifier (name) This misfeature also prevents from being able to add the same sshkey to different authorized_keys files. For example, if users joe need to have ssh access to a utility ops account, then joe's public key needs to be added to his own ~joe/.ssh/authorized_keys file, as well as to the ~ops/.ssh/authorized_keys file. Currently, the key names under the ssh_authorized_keys: stanza need to be made unique. So, when inserting joe's public key for his own account, the ssh key name might be "j...@mydomain.com". But, to use the same ssh key under the ops account, that same key name cannot currently be used, even though the public key is, in fact, the same key. Instead, there should be a single, "master" definition of a given public key, and then there should be a way to reference (for insertion) copies of that same key. The current syntax for defining an ssh key is: ssh_authorized_keys: key_name: j...@mydomain.com type: ssh-rsa key: .... SSHKEYSTRING ... then, to reference a key already defined, perhaps allow a new attribute: use_key to mean something similar to key_name: ssh_authorized_keys: - use_key: j...@mydomain.com - use_key: sa...@mydomain.com Add Comment   This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.