Adam Michalik
Adam Michalik
https://drive.google.com/file/d/1TmWZ72rw5cTFEx9pOelAR9jOq5Y3T4mL/view?usp=sharing sorry, I couldn't upload it to github. You might be able to repro it using my deployment/service above. I reproed it in multiple separate EKS clusters.
(I uploaded sysdump above)
Sorry, I'm not sure what else you need, exactly. Can you be more specific? I'll be happy to provide it.
I saw other discussion on this topic, and I understand that the current design is crucial to making builder implementation simple and consistent. What do you think about having a...
I think that leveraging generics is definitely viable. It would be hard to make this change in a backward-compatible way, though. `x509_cert` is still on `0.x.x` version, so it would...
@tarcieri would you (or some other RustCrypto developer/maintainer) be interested in contracted work for delivering this "X.509 certificates for no_std, no alloc environment" functionality? My organization is very interested in...
OK, so if someone wants to use RustCrypto primitives as providers for the `rustls-webpki` crate for X.509 certificate path validation in a context completely and wholly unrelated to TLS (for...
OK, so if we make ED25519, X25519, P-384, and RSA support optional (as they're not required by TLS 1.3), and keep just AES, SHA-2, and P-256 as required, would that...
(and RSA as required, I forgot that TLS 1.3 requires it as well)
Alternatively, what if you simply hide TLS support itself behind a (default) feature? Basically, if you enable `tls` feature, you get what the crate currently does (with optional support for...