The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:

Bug #1753

ssh_authorized_key chokes on keys without a comment

Added by Sam Quigley over 7 years ago. Updated over 7 years ago.

Status:DuplicateStart date:11/17/2008
Priority:NormalDue date:
Assignee:Brice Figureau% Done:

0%

Category:ssh
Target version:0.24.7
Affected Puppet version:0.24.5 Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com


Description

We have a user with an ssh key that doesn’t have a comment. (Ie, the format of the line is just “ssh-rsa \n”). when attempting to manage authorized_keys for that user, puppet explodes:

err: Got an uncaught exception of type ArgumentError: Field ‘name’ is required

This appears to be a perfectly legitimate syntax for that line — for example, one of the examples in http://www.openbsd.org/cgi-bin/man.cgi?query=sshd&sektion=8 doesn’t have a comment — and openssh doesn’t seem to mind, so I don’t think puppet should mind, either.


Related issues

Duplicates Puppet - Bug #1531: ssh_authorized_keys should not use the key 'comment' as a... Accepted 08/25/2008

History

#1 Updated by James Turnbull over 7 years ago

  • Category set to ssh
  • Status changed from Unreviewed to Accepted
  • Assignee set to Brice Figureau
  • Target version set to 0.24.7

#2 Updated by Brice Figureau over 7 years ago

  • Status changed from Accepted to Duplicate

I’m afraid it is unfixable for the moment.

The comment is used as the namevar (title) of the ressource. If there is none, then that means the resource has no title which is impossible in Puppet.

This is a variation of bug #1531, hence I changed the status to duplicate.

Also available in: Atom PDF