tree 5c218d16e791428c8f92f72a07011336bec2e55b
parent 369ce38ac1dacd16a87f91694a05c5c143e18d80
author Johannes Schindelin <johannes.schindelin@gmx.de> 1587157454 +0200
committer Daniel Stenberg <daniel@haxx.se> 1587366947 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQFDBAABCgAtFiEEJ+3q8i86vOtQ25oSXMkI/bceEsIFAl6dTF4PHGRhbmllbEBo
 YXh4LnNlAAoJEFzJCP23HhLClCMIAKxYHhB63ygBnkatcNCcIgm+eKjtQ4U1fLg2
 TAczDapu3aRQgxh7Hu0wG0ivorgq8AnNRipQq7TXstZmHefbT1ePx92Rhzw5PWue
 W32kYjQy5kRSijG7+2Yr2QgxH6IlG4/ifEDUKig4OZ+8wRBe6GxqckwxHWFNXPoR
 zSn28USflssl/1sadrAKZHuRa44kDhhx2uJvPDq2m+LqDT1d1z1LY38p60U4hfSB
 sIn+9/0Yz/E/mMob64zrd2bFg7UQ0N8+aZeEQIw3HWqyM1FdnbbGH65XvP6Z0vX/
 3MigqSbU+liOErFKRn0ktWLz1J3FqPreHhUFJYakEuawR/xCE1I=
 =bLIQ
 -----END PGP SIGNATURE-----

multi-ssl: reset the SSL backend on `Curl_global_cleanup()`

When cURL is compiled with support for multiple SSL backends, it is
possible to configure an SSL backend via `curl_global_sslset()`, but
only *before* `curl_global_init()` was called.

If another SSL backend should be used after that, a user might be
tempted to call `curl_global_cleanup()` to start over. However, we did
not foresee that use case and forgot to reset the SSL backend in that
cleanup.

Let's allow that use case.

Fixes #5255
Closes #5257
Reported-by: davidedec on github
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>