When building dropbear statically and linking against glibc, dropbear claims every user is nonexistant. During the build messages like using 'xyz' in statically linked applications requires at runtime the shared libraries from glibcversion used for linking. Even though these are available on the system, calls to getspnam() fail and dropbear assumes the username is nonexistant. Reproducible: Always
For the sake of completeness, I built a glibc with static nss. This eleminates the messages about the DSO that need to be in place during runtime, but auth still keeps failing. Rebuilding dropbear with -static fixes the problem. Can this be related to an upgrade of glibc or shadow?
you must provide `emerge --info` with every bug report *** This bug has been marked as a duplicate of bug 509748 ***