Re:This shouldn't have happened: A vulnerability postmortem
by josephg on Wednesday December 01, 2021 @10:14PM
(#29412108)
Sounds like a feature of the porting process. Not a bug. And I’d like to think that BoringSSL would be designed well enough internally to make that less of an issue.
I agree that this might slow down the process of porting the code though. I wonder how much by?
Converting code to Rust while keeping the logic one-to-one wouldn't work. Rust isn't ensuring memory safety by just adding some runtime checks where C/C++ aren't. It (the borrow checker) relies on static analysis that effectively tells you that the way you wrote the code is unsound and needs to be redesigned.