Joshua Liebow-Feeser

I'm not actually the one who made the decision to use RustCrypto (not to say that I'm opposed to it or anything), so I'll have to get back to you...

Asked about this internally, and got this response: > We have confidence in RustCrypto's maintainers, their testing discipline, and the resulting code quality.

I would absolutely be interested in this! I'm particularly interested in (2) and (3), as I expect I should be able to pre-generate `crypto/err_data.c` at code commit time. Also, if...

IIUC, we'll still need (1) in order to fully remove the dependency on Go, even if we remove CMake and drive the compilation manually from the build script. @davidben, correct...

Thanks for the detailed analysis! I think I can answer most of your questions, but let me know if I've missed anything: - Our current MSRV policy is just that...

@jswrenn I've confirmed locally that this doesn't have the same bug as #810.

Reopening per #811.

> Would it be practical to factor out the safe transmutation aspect of zerocopy from the rest of it? My understanding is that zerocopy is trying to do many things...

> I think we may need to do more experiments in _ring_ to see how we can statically guarantee panic-free-ness and safety with the help of zerocopy. Can you say...

@Kestrer, do you know if it's sufficient to instead emit `::zerocopy`? My assumption is that, even if zerocopy is reexported by another crate, it still has to be available to...