This bug was originally filed in Launchpad as LP: #1877869
Launchpad details
affected_projects = []
assignee = None
assignee_name = None
date_closed = 2020-08-25T19:31:34.374731+00:00
date_created = 2020-05-10T15:27:12.475125+00:00
date_fix_committed = 2020-08-25T19:31:34.374731+00:00
date_fix_released = 2020-08-25T19:31:34.374731+00:00
id = 1877869
importance = undecided
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1877869
milestone = None
owner = imrehg
owner_name = Gergely Imreh
private = False
status = fix_released
submitter = imrehg
submitter_name = Gergely Imreh
tags = ['bitesize']
duplicates = []
Launchpad user Gergely Imreh(imrehg) wrote on 2020-05-10T15:27:12.475125+00:00
I have an ssh key generated for Yubikey, with "ssh-keygen -t ecdsa-sk ..." which results in an ssh public key of "sk-ecdsa-sha2-nistp256@openssh.com ...."
When I add that key to "ssh_authorized_keys", it doesn't get added to the authorized_keys file, even though other, regular "ssh-rsa" keys are added. For example this config:
#cloud-config
ssh_authorized_keys:
- "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC2qSqrC6lsKqpY6fKF2LDxET/DuCJcKGTFnpFHPWj0yqVsvqooUIDKXCgEXx0rOJaqUpnnXWfij0/Yr4l8GxmJGr9hpkG+MXhwYehDvbZHrP5C/MPyyOCqjPlr3d4touBAhCTNJapFSHYnoQfguuGbZDS8Nfvu6JYS0ODvbgp8z5BnZVVFW4J7ms2QQwHIyvc5kk6sUvlL1xqRu+2mLz4vPxTqGPPLDdfbSOapCI5i4yZxLziIWSOdPBUlAnFRV4ONKT7m3/pT2wUkObprCKZAMH+bL52GYxOToUXm6EaFUGR+ptiMWbQXHIxiZfxtinp6LfZouRJz9/+vKQoTBPXJ"
- "sk-ecdsa-sha2-nistp256@openssh.com AAAAInNrLWVjZHNhLXNoYTItbmlzdHAyNTZAb3BlbnNzaC5jb20AAAAIbmlzdHAyNTYAAABBBIofALjMlvK/KmwHVhzqIV4HTylBjos4xQqRE+GKQqe1a/LOKTGluhneCq3WE5L9578ZLQENWPrqIoUWjg/XcxAAAAAEc3NoOg=="
results in only "ssh-rsa" key being added, (I've also tried specifying them in different order and the same outcome).
Tested on Ubuntu 20.04, on AWS.
This bug was originally filed in Launchpad as LP: #1877869
Launchpad details
Launchpad user Gergely Imreh(imrehg) wrote on 2020-05-10T15:27:12.475125+00:00
I have an ssh key generated for Yubikey, with "ssh-keygen -t ecdsa-sk ..." which results in an ssh public key of "sk-ecdsa-sha2-nistp256@openssh.com ...."
When I add that key to "ssh_authorized_keys", it doesn't get added to the authorized_keys file, even though other, regular "ssh-rsa" keys are added. For example this config:
#cloud-config
ssh_authorized_keys:
- "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC2qSqrC6lsKqpY6fKF2LDxET/DuCJcKGTFnpFHPWj0yqVsvqooUIDKXCgEXx0rOJaqUpnnXWfij0/Yr4l8GxmJGr9hpkG+MXhwYehDvbZHrP5C/MPyyOCqjPlr3d4touBAhCTNJapFSHYnoQfguuGbZDS8Nfvu6JYS0ODvbgp8z5BnZVVFW4J7ms2QQwHIyvc5kk6sUvlL1xqRu+2mLz4vPxTqGPPLDdfbSOapCI5i4yZxLziIWSOdPBUlAnFRV4ONKT7m3/pT2wUkObprCKZAMH+bL52GYxOToUXm6EaFUGR+ptiMWbQXHIxiZfxtinp6LfZouRJz9/+vKQoTBPXJ"
- "sk-ecdsa-sha2-nistp256@openssh.com AAAAInNrLWVjZHNhLXNoYTItbmlzdHAyNTZAb3BlbnNzaC5jb20AAAAIbmlzdHAyNTYAAABBBIofALjMlvK/KmwHVhzqIV4HTylBjos4xQqRE+GKQqe1a/LOKTGluhneCq3WE5L9578ZLQENWPrqIoUWjg/XcxAAAAAEc3NoOg=="
results in only "ssh-rsa" key being added, (I've also tried specifying them in different order and the same outcome).
Tested on Ubuntu 20.04, on AWS.