Posted by Solar Designer on Nov 15 Hi, I'm sorry I'm late to comment in this thread, but I feel a few aspects are still misunderstood by a lot of people here. Kind of, and that's indeed embarrassing, but it misses important detail. musl's crypt(3) only returns "*" when the setting (aka salt) string
Briefing
Written from the coverage below · deepseek-v4.1-flash
OpenSSH on systems using musl libc allows password authentication bypass for accounts whose hash field is '*', because musl's crypt(3) returns an unexpected value that OpenSSH mishandles. A password longer than 257 characters logs in to such accounts.
Why it mattersAny musl-based host exposing sshd with locked or invalid password hashes may accept arbitrary logins, enabling remote access without credentials.
ActionUpgrade OpenSSH to a release with the musl crypt(3) '*' fix, or ensure no accounts have a password hash field of '*'.
Coverage
2 articles