Alex Gaynor

I'm having a lot of trouble following your message, you seem to say that the error your indicated above was caused both by linking against your custom openssl, and by...

It sounds to me like your copy of OpenSSL 3.0.13 is somehow broken. `apps\lib\http_server.c` is a file from OpenSSL itself, so if it's trying to reference `OSSL_TRACE_CATEGORY_HTTP` that means you...

Again, there is no reason for you to be doing anything with vendored, that's not necessary to use a custom OpenSSL, and in fact does the opposite of that. As...

Using featured = vendored causes rust-openssl to use it's own copy of OpenSSL. It is not doing what you want at all. On Thu, Aug 29, 2024 at 6:27 AM...

I guess as a starting point: What would your desired behavior be :-) I'm _guessing_ it's something like: if `openssl-provider-legacy` is installed, use it, if it's not, ignore it. Never...

It occurs to me that this will also impact _our_ non-wheel users. If distros are going to be switching legacy to not be installed by default, I guess we'll probably...

I would not assume that. AFAIK legacy provider is needed for several algorithms that are widely used in PEM and PKCS#12 encryption. (These algorithms are garbage are people shouldn't use...

@xnox You should re-consider your approach, both maintainers of this library had _extremely_ negative reactions to your comment. And the reason for that is that you've failed to understand how...

As a general purpose cryptography library, we don't really know what our users are going to use us for, which makes it more challenging to only load it when required....

It also simply wouldn't work. RC2 decryption is handled by OpenSSL as part of the PKCS#12 parse-and-decrypt process, there's not an entrypoint for us to _only_ do that RC2 encryption.