Perhaps an acceptable solution could be to write the file only if cloud- init needs to overwrite the value to "no", but if the value is "yes", the openssh default, it shouldn't create the file. This would allow continuing to use the .d directory, but would prevent confusion which results in password authentication being enabled contrary to expectations.
-- 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/ubuntu/+source/cloud-init/+bug/2088207/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
