5 ms·
Personally, I’m weary of software written in languages without memory safety that are more likely to have long living exploits only known to certain government
by likeabbas 4y ago
Personally, I’m weary of software written in languages without memory safety that are more likely to have long living exploits only known to certain government authorities.
- VWWHFSfQ 4y agoJust because the OP didn't use unsafe {} anywhere in their code doesn't mean it's not used in any dependencies. Just glancing at some of the deps I can already see there is a lot of unsafe usage deep down that are "wrapped" in safe interfaces. Rust is not some kind of silver bullet for safety. It just makes it more explicit. Also, I'm less concerned about the memory safety than the _complete reimplementation of SSH_ from scratch. So give me OpenSSH any day for things that are actually important.
- throwaway2048 4y agoId trust old software written in a memory unsafe language that has a sterling track record over new software written in a safer language that has not much of a track record at all.
- politician 4y agoThe Rust authors condemned the world to play their stupid game of semantics when they created the `unsafe` keyword. The feature turns off extra compile time checks. That’s it. It doesn’t mean the program is correct. This program still allows potentially damaging things like `rm -rf /`. So, it’s not data safe. It’s unknown whether it’s secure safe either, since it’s not been audited and it’s still “alpha”.
- RTFM_PLEASE 4y agoPlease educate yourself. https://www.openbsd.org/security.html https://www.openbsd.org/security.html https://www.openssh.com/history.html https://www.openssh.com/history.html