241–242 of 242 posts
Earlier quoted context omitted.
> you need to run it in it's own process Assuming that you can detect OOM in userspace at all, which usually isn't the case on Linux (or any other system with overcommit).
huh? you'd notice your child process was exited with SIGABRT.
Earlier quoted context omitted.
Does the OpenSSL library allow/plan for an Rust reimplementation (possibly side-by-side for a while) of the C bits? Seems that would be best practice - assuming the goal is make everything safe Rust.
In theory that's just copying the Rust bridge code and using that as the frontend API for a rewrite. So yes it's possible, you "just" need to rewrite the rust-openssl-sys library. I think the hesitation there is that everyone has gotten it beaten into your head that writing new crypto libraries is dangerous. It's probably safer to use a library that has tons of eyes on it, but at some point we should do it.
But maybe for openssl staying close to the original API is useful, then one could maybe put a C API on top and use it also outside Rust.