On Apr 18, 2019, at 5:05 PM, Bill Cole
wrote:
> Is there some approach that I'm not seeing to build against the new version
> while leaving services that use the old version (and spawn worker children
> while running) up and functional?
I think your best bet is to wait for that PR to be
It's about time to get everything off the soon-to-be-EOL'd OpenSSL 1.0.2
and onto 1.1.1, particularly with so-called 'security scanners' scolding
for lack of TLSv1.3 support. I was happy to see the advent of openssl10
and openssl11 ports which purport to simplify migration, but it's not
clear
