On Wed, Jan 29, 2014 at 11:08 AM, Sean McArthur <[email protected]>wrote:
> Considering the effort to break up libextra into multiple crates in > #8784[1], could rust-crypto[2] be moved back into rust as libcrypto? > As it were, ruby-core is now talking about extracting OpenSSL into a separate library packaged independently from the standard distribution. They are not cryptographic domain experts, don't want to be responsible for it, and having it in the standard library limits their agility around incident response when security problems are discovered. Some comments on the issue deviated about whether crypto should written > *in* Rust, or just be bindings. As a user, I don't care how they are > implemented, as long as the exposed API is Rust-like. > rust-crypto is a brand new implementation of a bunch of crypto which hasn't been well-audited. That alone should worry you. I would definitely not be a fan of a non-battle hardened crypto library being in core Rust. -- Tony Arcieri
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
