Comment 6 for bug 1832659

Yes, we have to use 2016 salt due to in house modules that need to be updated. If salt 2016 was updated, we would still have quite a bit of work to do. The fix in upstream works, in fact just removing OPENSSL_INIT_NO_LOAD_CONFIG works. But, it also worked before the openssl update. And I think that is really only a work around. I suspect others will hit similar issues separate from Salt, like mentioned in the upstream bug. I'm wondering, why did you use 1.1.1 instead of 1.1.1c?