Is the cloud-init configuration that requested a specific user with specific password and sssd installed but unconfigured a "correct" cloud- init configuration?
I'd naively expect a cloud-init config for a system that is going to run sssd to also install sufficient sssd configuration for it to be fully functional before it is necessary. A user without a password should be rejected by default configurations of sshd, but how about login via getty? Someone 'local enough' to interact with a console should probably be considered root-ish (since they can boot with "init=/usr/bin/bash" etc) but I could also see some argument for a passwordless login being unexpected. I'm not entirely sure if this should be treated as a security issue or not. I'm leaning towards an SRU but might be convinced the other way around. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2153951 Title: no config.ldb file under /var/lib/sss/db in 26.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2153951/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
