Sshole
Points and comments are a snapshot, not live.
A bug in musl's crypt() lets any password over 256 chars unlock accounts locked with *.
Since 2016, OpenSSH on musl Linux (Alpine, OpenWrt, etc.) without PAM accepts any password longer than 256 characters for accounts with a * password field (root, key-only users, LDAP users). The chain: musl's crypt() returns * instead of NULL on failure; OpenSSH's 2016 fix for CVE-2016-6210 hashes passwords even for *-locked accounts; Alpine uses * for root since 2022. This means accounts intended to be password-locked accept any 257-1024 character password. Alpine's official cloud images have a default alpine user with passwordless doas, making the exploit grant root access.
Update to OpenSSH 10.6p2 or disable PasswordAuthentication.
What commenters are saying
Several commenters note that Docker containers rarely run sshd, reducing real-world exposure. Some debate whether musl's decision to return * instead of NULL was reasonable, given POSIX spec requires NULL on error. One camp argues musl accommodated buggy callers at the cost of security; another notes that failing loudly would have surfaced the bug earlier. A few point out the fix is straightforward: update or disable password auth. The writing style and scroll-triggered animations divide readers, with some finding the explanation clear and others distracted.