2024-04-23 - Discovery of SSL_select_next_proto memory unsafety while rewriting it in rust.
jbp.io/2024/06/27/cve-2024-5535-openssl-memor...242
u/SelfDistinction
* zero-cost abstractions
* move semantics
* guaranteed memory safety
* threads without data races
* trait-based generics
* pattern matching
* type inference
* minimal runtime
* efficient C bindings
Since you asked for blog posts, and I already read many of them that didn't share my concerns, here is my take.
In 2017, I wrote some Rust code for a job listing. My job was to create a backbone for an Android app, and since it was a computationally heavy backend, and the communication with the frontend was through https, I chose Rust for the job. It went fairly well.
Additionally, I'm using Rust for DNA processing, stuff like building De Bruijn graphs, sequence alignment, etc.
On the job, I wrote something resembling this pattern:
for data in rx.into_iter() {
let validated_data = valid
You've reached the end of this feed.