How to correctly handle CA bundle update?

luis jury <[email protected]> Tue, 26 Jun 2018 12:05:58 -0400
Newsgroups gmane.comp.web.curl.php
Message-ID <CAHvF5s1eg65yQLVicRpzSvC+WuSd7h8x_Y7fXb6weXnWpuJjuQ@mail.gmail.com>
--===============2049491715==
Content-Type: multipart/alternative; boundary="0000000000001de827056f8dade5"

--0000000000001de827056f8dade5
Content-Type: text/plain; charset="UTF-8"

Hi guys,

The last week there was a change in the CA bundle, so, we had to update the
bundle on our servers (we use guzzle). We lost some time between the change
in the certificate and when we knew we had some processes failing because
of this.

I was wondering, what would be the correct way to handle what I describe
here?. I had used `update-ca-certificates` in my building scripts before to
avoid problems with the change of the bundle, but it doesn't feels good.

--0000000000001de827056f8dade5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi guys,<br><br>The last week there was a change in the CA=
 bundle, so, we had to update the bundle on our servers (we use guzzle). We=
 lost some time between the change in the certificate and when we knew we h=
ad some processes failing because of this.<br><br>I was wondering, what wou=
ld be the correct way to handle what I describe here?. I had used `update-c=
a-certificates` in my building scripts before to avoid problems with the ch=
ange of the bundle, but it doesn&#39;t feels good.<br><br><br></div>

--0000000000001de827056f8dade5--

--===============2049491715==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KaHR0cHM6Ly9j
b29sLmhheHguc2UvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL2N1cmwtYW5kLXBocAo=

--===============2049491715==--