This seems relevant:<p>Future of Memory Safety
Challenges and Recommendations
<a href="https://advocacy.consumerreports.org/wp-content/uploads/2023/01/Memory-Safety-Convening-Report-1-1.pdf" rel="nofollow">https://advocacy.consumerreports.org/wp-content/uploads/2023...</a><p>"""
Case Studies
1. The Python cryptographic authority is one of the most widely used cryptography libraries
in the Python ecosystem. Many of the tools are largely built on OpenSSL. The popular
cryptography library is written in C. About two years ago, the maintainers started the
process of migrating some of their dependence on OpenSSL away from that to their own
Rust code, particularly starting with areas around certificate parsing and parsing of other
structures. These are some of the most classical places to find memory safety
vulnerabilities in C libraries, and they wanted to mitigate the risk that they were having by
relying on OpenSSL.<p>Another benefit was getting huge performance improvements, because the greater
safety guarantees they were getting from the language allowed them to be more
aggressive in doing things like not copying memory. Specifically, the safety guarantees
of Rust mean that one can easily represent structures like X.509 certificates as an array
of bytes, and then a parsed structure containing pointers into the original array. ...
"""