*sshole, or when are we finally going to get rid of C?
Web page · https://sunshowers.io/posts/sshole
First seen by Oriel on .
AI summary
The article uses an OpenSSH authentication vulnerability on musl systems to argue that Rust’s type system and community norms prevent error-handling patterns that C permits.
- musl crypt returned "*" for oversized passwords, colliding with Unix’s sentinel for locked accounts and enabling unauthenticated shell access on systems without PAM.
- The vulnerability was a logic error rather than a memory-safety issue, arising after musl deviated from POSIX because some callers failed to check NULL.
- Rust result types would encode an oversized password as an error variant and compel callers to handle it, unlike C’s unchecked return conventions.
- The author acknowledges Rust’s compile-time and portability costs but argues distributions should prioritize security-oriented engineering norms for most users.
- LLM agents do not erase language differences because generated code inherits community libraries, training patterns, and invariants encoded by each language’s type system.
#c #rust #openssh #software security
Generated by gpt-5.6-sol. Check the original for details.
Metric trends
Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained
Points
Score reported by the source.
- Lobsters: 60, latest observation ; +58 over observed period since
Comments
Comment count reported by the source.
- Lobsters: 83, latest observation ; +83 over observed period since
Aliases
| Source | External ID | URL |
|---|---|---|
| Lobsters | owsnms | https://sunshowers.io/posts/sshole/ Read discussion |