4 ms·
I hate to be that guy, but _damn_ does PAM seem ripe for being rewritten in Rust. Maybe it's the PTSD speaking, but seeing vanilla C string operations in a secu
by AceJohnny2 6y ago
I hate to be that guy, but _damn_ does PAM seem ripe for being rewritten in Rust. Maybe it's the PTSD speaking, but seeing vanilla C string operations in a security-critical library makes my hair stand on end.
Searching around, the best I can find is one 0.1 crate that hasn't seen activity since 2017:
https://crates.io/crates/librustpam https://crates.io/crates/librustpam
- Foxboron 6y agoNothing about this CVE was related to the language though. It's a configuration issue along with nullok.
- yencabulator 6y agoPlease, instead, let's have something that isn't a shared library loaded into everything. Something usable by contained/isolated/sandboxed software just by giving them a unix domain socket to talk to, with no need to share /etc/shadow.
- edgyquant 6y agoYou should definitely write an MVP and come back with one. Or write a blog post explaining what parts would benefit and why it is a clear cut case for a rewrite and then post it here.