Back

@bagder Yep, though they've at least fixed the CURLOPT_SSL_VERIFYPEER, so it wasn't all for nothing.

The CURLOPT_SSL_VERIFYHOST stayed at false (coerced to 0), though, but I feel it's the lesser evil of the two (would that be a correct conclusion?).