Matt Caswell

From the NOTES.WINDOWS file I previously referred to: ```` 2. Install NASM 3. Make sure both Perl and NASM are on your %PATH% ````

It doesn't explain your main problem, but your config file attempts to load some providers into the default library context, and this: ```` /* Disallow falling back to the default...

> The default provider can be loaded by a so called fallback if there is no provider loaded yet into a libctx and you try to fetch an algorithm. The...

There should only be a very small number of locations in the library where we actually need to init with `OPENSSL_INIT_LOAD_CONFIG`. Basically anywhere that we read a global (or default...

> Hmm, it is questionable whether this is something we would want to "fix" in 3.0 branch. It can be seen as a (mis)feature. It could certainly be that people...

**OTC Question: This issue is a clear bug, but it could be that people are relying on this behaviour. Should it be fixed and if so in which branches?**

I suspect that there may be another variant of this bug: if you load the *same* config file in the default libctx and another libctx, and then you free the...

> Can I look at fixing this if required? @mattcaswell Note also that @sebastianas is working in this area in #19244 (and it was reviewing that PR that led me...

I'd personally put it on the "bug" side of the line. I'd be happy to see a PR for it. Adding the missing `ssl_log_secret` call seems a reasonable approach.

> I could see explicitly logging the subsequent traffic keys being useful if you start capturing a stream halfway through. Even if you are logging from the beginning it is...