Comment 8 for bug 1869277

> The keys are written in a more machine friendly way also.

I'm looking at (a focal lxd) console, and the two ways I see the host keys written are (each of which is repeated per key type):

  Apr 07 20:23:54 unique-filly cloud-init[320]: Generating public/private dsa key pair.
  Apr 07 20:23:54 unique-filly cloud-init[320]: Your identification has been saved in /etc/ssh/ssh_host_dsa_key
  Apr 07 20:23:54 unique-filly cloud-init[320]: Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub
  Apr 07 20:23:54 unique-filly cloud-init[320]: The key fingerprint is:
  Apr 07 20:23:54 unique-filly cloud-init[320]: SHA256:lCiVjNhfVGOMNEHdXwI3Cx+ljhI+LwuXBxHaGayVHQA root@unique-filly

which is repeated per key type, and the output being discussed here:

  Apr 07 20:24:09 unique-filly ec2[1215]: 1024 SHA256:lCiVjNhfVGOMNEHdXwI3Cx+ljhI+LwuXBxHaGayVHQA root@unique-filly (DSA)

To my eyes, the latter output is much more machine friendly, because it's all contained in a single line.

Am I missing another way of getting the host keys emitted to the console? (Perhaps you were thinking of cc_ssh_authkey_fingerprints, which is for authorised keys?)