CloudConfig.setup_user_keys should not hardcode the authorized_keys location
Bug #731849 reported by
mrkschan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: cloud-init
CloudConfig.
Related branches
Changed in cloud-init (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Triaged |
To post a comment you must log in.
This bug was fixed in the package cloud-init - 0.6.1-0ubuntu9
---------------
cloud-init (0.6.1-0ubuntu9) oneiric; urgency=low
* sync with trunk (rev 404) ssh/authorized_ keys configurable forwarding, no-agent- forwarding, no-X11- forwarding'
* make metadata urls configurable, to support eucalyptus in
STATIC or SYSTEM modes (LP: #761847)
* support disabling byobu in cloud-config (LP: #797336)
* guarantee that ssh_config runs before sshd starts (LP: #781101)
* make prefix for keys added to /root/.
and add 'no-port-
to the default (LP: #798505)
* make 'cloud-config ready' command configurable (LP: #785551)
* make fstab fields used to 'fill in' shorthand mount entries configurable
(LP: #785542)
* read sshd_config to properly get path for authorized_keys (LP: #731849)
-- Scott Moser <email address hidden> Fri, 17 Jun 2011 12:18:34 -0400