Richard Levitte

Mind you, it _is_ possible to use several engines, _as long as they don't compete on the supported algorithms_.

> But actually, I have a better workaround for OpenSSL That workaround only falls down on 1.1 where the keys are opaque. If you give us an accessor for `RSA_set_engine()`...

You're thinking that `crypto/pkcs11` would become an alternative to the ENGINE API, right? I do agree with that motion, have been thinking along those lines for a while. That would...

Which means that we really need to write a storage wrapper that will accept URIs, parse them and dispatch them to different routines depending on the URI schema.

We're getting very off topic, by the way

I think that the conclusion of all this is: - that [openssl#1644](https://github.com/openssl/openssl/pull/1644) is necessary for your planned hacking of the keys for the OpenSSL 1.0.2 series. - that your planned...

> The PR is not working. I create a fork to openSSL ([Ludea@05f7de4](https://github.com/Ludea/openssl/commit/05f7de472d996dfbbb5415f578dcbfcac989016a)) with modification, update all dependencies to use my fork , restart CI and still get issue: https://github.com/Ludea/tauri-mobile/actions/runs/3065602681/jobs/4949864965#step:15:593...

> Can anyone trigger the workflows? Done

> - I guess this would mean OpenVMS support should create a MMS ("Module Management System") description? Yes. MMS is very much like make, so anyone used to that should...

> @kroeckx > > > Note that there are plenty of platforms you've never heard about, where OpenSSL is currently used. > > Do you know of any off hand...