Sergey "Shnatsel" Davidoff

Address, memory, leak and thread sanitizers all work. Undefined behavior sanitizer does not, it seems to be too closely coupled with C/C++. See https://github.com/japaric/rust-san I have left this target to...

I've fuzzed `WebSocket::read_message` in both client and server modes with afl.rs and cargo-fuzz, and found no crashes. cargo-fuzz was also run with address sanitizer. This is literally the first crate...

Just put whatever you want to attach in triple backticks: put ``` before and after the text

I'm pretty sure point 1 can be refactored using `u32::from_ne_bytes(buf[..4].try_into().unwrap())` instead of unaligned reads. Since the length is known in advance, the optimizer should elide bounds checks and the unreachable...

I'm reopening the issue to indicate that this is something we're interested in, and also to better track it. For finer-grained updates see https://github.com/rust-secure-code/cargo-repro/

There are trivial violations of validity invariants in private functions, so it warrants a closer look. Example: https://github.com/seanmonstar/httparse/issues/58

A few pull requests with safety improvements have landed recently and should ship in version 3.0: https://github.com/actix/actix-net/pull/158 https://github.com/actix/actix-net/pull/161 https://github.com/actix/actix-web/pull/1614 https://github.com/actix/actix-net/issues/91 However, some unsafe code remains and still needs to be...

Unsound Cell impls allow multiple mutable references to the same data, which may lead to pretty much arbitrary memory corruption, including use-after-free. However, it requires somewhat contrived code on the...

actix-web 3.0.0 with notable safety fixes has been released today. Here's a list of the actix-* crates that still use unsafe code: - actix-http: 13 unsafe blocks, all are commented...

Versions in the latest git have even less unsafe code than the 3.0 release