Captain Obvious here with a public service announcement: Rust's safety guarantees dont extend to logic or protocol implementation problems or misconfigured security settings.the part of the article about service providers leaking creds or other info...Rust all the things and that will still happen. Some of this stuff is just too much. Also, why not work on lifetime and memory safety in a c based language? Rust looks…
https://hoverbear.org/2016/10/12/rust-state-machine-pattern/
https://blog.tarn-vedra.de/posts/phantom-types-for-safe-apis...
https://insanitybit.github.io/2016/05/30/beyond-memory-safet...
https://scribbles.pascalhertleif.de/elegant-apis-in-rust.htm...
Some libraries use such features to prevent certain kinds of nonce-reuse during encryption (one of the more common ways of screwing up encryption). These constraints are checked at compile-time.
Such guarantees are not possible with weaker type systems like that of C.