> the most technically advantageous and correct way to configure ssh Agreed
> How is cloud-init making sure another file in sshd_config.d isn't superseding its config? It isn't. I just filed an upstream bug to track this as an issue - and linked it above. > sshd -T should be consulted, instead of trying to mimic what sshd -T does Agreed, however ssh -G is more robust since -T is more likely to have failing tests. > I'm adding the openssh package to this bug Thanks! That approach sounds good to me. Since the cloud-init (ubuntu) project exists to track issues in cloud- init on Ubuntu, I'm going to mark it as invalid for now. Feel free to change that back if you believe this to still be an issue with cloud- init. ** Bug watch added: github.com/canonical/cloud-init/issues #5879 https://github.com/canonical/cloud-init/issues/5879 ** Also affects: cloud-init via https://github.com/canonical/cloud-init/issues/5879 Importance: Unknown Status: Unknown ** Changed in: cloud-init (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2088207 Title: cloud-init enables ssh password auth in an unexpected config file To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2088207/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
