It's related to the Google thread because there may be people affected there who have been bitten by THIS issue as the backend is using OpenSSL 1.0.2, not the others. We just don't know.