On 02/05/2020 16:39, Sam Roberts wrote: > On Sat, May 2, 2020 at 12:31 AM Richard Levitte <levitte@xxxxxxxxxxx> wrote: >> No. When DSO support is turned off, the legacy provider code becomes >> part of libcrypto, in an inaccessible state (in other words, you still >> have to "load" it). > > Using OSSL_PROVIDER_load(NULL, "legacy")? > > My first try after a static only build (and delete of all .so files) > got an error from that, but if its the correct way, I'll investigate > more. Yes, that is the correct method. Matt
