maybe cellebrite should have rewritten their code in rust

@be yeah, i've fuzzed a fair bit of rust code recently, and never found a memory corruption bug.

not that I don't find problems, but it's controlled panics and infinite loops rather than memory corruption.

turns out just bounds checking by default fixes a lot of problems

@be though shoutout to that rust project that basically wrote

`fn uninit<T>() -> T` as a public function (or let you construct this pretty trivially)

yes that gives you an uninitialised T

i've made a report about it but was told it wasn't an issue which like ???

so whatever i'm not salty

Sign in to participate in the conversation
☠️ librepunk ☠️

a friendly general instance for coders, queers, and leftists!