sshole, or when are we finally going to get rid of C?
Summary
The piece discusses a Linux/OpenSSH vulnerability caused by musl libc's crypt returning '*' for long passwords, enabling unauthenticated access on Alpine-based systems. It uses this example to argue that C's lack of advanced type systems fosters risky in-band signaling, whereas Rust's approach would require explicit error handling. The article links to advisories and reflects on engineering norms, community standards, and broader implications for security in systems programming.