Le 08/06/2020 à 21:08, Bob Proulx a écrit :
[...]
> I have upgrade the CA certificate bundle on our three machines that
> were needing it, download0, vcs0, mgt0. Testing shows that the
> previous certificates that were previously invalid are now validating.
> I am going to wait and let the mirmon
Ian Kelling wrote:
> Awesome. Onto server upgrades! I just decommissioned a debian lenny
> machine this last weekend.
Lenny! He was a good chap. Always kept his eyes open!
:-)
Bob
Bob Proulx writes:
> Bob Proulx wrote:
>> All of those seem to be the outdated CA list and openssl on
>> download0. All but one of the above were issued by Comodo. Which is
>> the mostly common thread among them. They apparently have a newly
>> issued trust anchor.
>
> It turns out that this
Bob Proulx wrote:
> All of those seem to be the outdated CA list and openssl on
> download0. All but one of the above were issued by Comodo. Which is
> the mostly common thread among them. They apparently have a newly
> issued trust anchor.
It turns out that this was a pretty widely felt expire
Ian Kelling wrote:
> Related, on https://savannah.gnu.org/maintenance/Mirmon/ there is a
> broken link, which also has a bad cert
>
> $ curl https://dl.sv.gnu.org/releases-noredirect/00_MIRRORS.html
> curl: (51) SSL: no alternative certificate subject name matches target host
> name 'dl.sv.gnu.or
I manually curled 2 of the bad mirrors listed here
https://download.savannah.gnu.org/mirmon/allgnu/, and there is a cert
error. I'm pretty sure, the issue is that the ca-certs needs updating on
the machine running mirmorn. The os itself could use an update too. Bob,
you there?
Related, on https://
