When Rust isn't safe
Kenneth Porter <[email protected]>
| Newsgroups | gmane.comp.encryption.openssl.user |
|---|---|
| Message-ID | <F4A230DE59AEBF494D59B325@[10.96.7.39]> |
An interesting crash analysis of a Rust application that traces into openssl_probe's use of the C library's setenv to discover that it's not thread-safe. <https://www.edgedb.com/blog/c-stdlib-isn-t-threadsafe-and-even-safe-rust-didn-t-save-us> Migitations are in place now in Rust and glibc: <https://github.com/rust-lang/rust/issues/124866> <https://github.com/bminor/glibc/commit/7a61e7f557a97ab597d6fca5e2d1f13f65685c61> -- You received this message because you are subscribed to the Google Groups "openssl-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-users/F4A230DE59AEBF494D59B325%40%5B10.96.7.39%5D.