8 Jan
2026
8 Jan
'26
11:19 a.m.
On Jan 5, 2026, at 6:10 AM, Alan DeKok <alan.dekok@inkbridge.io> wrote:
Hmm... OK. I just tried it, I'm seeing the same thing. I'm not sure what changed.
After a quick look, it seems to be an OpenSSL issue. For some reason, the SHA256 code in OpenSSL isn't doing its job. Tracking that down will be more work. You might be able to fix it by updating the cipher_list to include SECLEVEL=1? That might re-enable SHA256. Alan DeKok.