> Is the cloud-init configuration that requested a specific user with specific > password and sssd installed > but unconfigured a "correct" cloud-init configuration?
Sort of. The original scenario was an unattended server install via subiquity, and I simulated it with just cloud-init on a fresh system. The user was created via cloud-init, and sssd installed, but to be configured later in boot. So the sssd configuration would still happen, but after cloud-init, or via some cloud-init module or runcmd perhaps. In previous sssd versions, the call to sss_cache would also initialize the config.ldb database. Not anymore, hence the bug. I understand an important component of a security vulnerability is an adversary, and here I don't see one, but a bug that leaves a system vulnerable when triggered. -- 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
