The fastly/cloudflare issues will be looked at by the people who handle that.
But I can answer this piece: firmware.openbsd.org is not available via HTTPS. The tools only use them it via http, so your testing for https is a mistake. You are noticing that some of these machines are multiple-purpose and happen to have https, but not related to firmware downloads. > And right now I'm getting an invalid cert error for > https://firmware.openbsd.org. It resolves to 145.238.209.46 > (pond.obspm.bsdfrog.org) and 94.142.244.34. The certificate is only > valid for the following names: distfiles.bsdfrog.org, emma-en-quete.com, > ftp.fr.openbsd.org, pond.obspm.bsdfrog.org, pond.stats.bsdfrog.org, > portroach.openbsd.org, www.emma-en-quete.com. Not sure if it's a > configuration error of some mirror server or something else. > > I know that the firmware as well as all other files are checked with > signify so https is not strictly required for authenticity (though it > does for privacy) and I don't remember if this domain has ever worked > via https before, anyway just in case there's really some misconfiguration. > > Regards, > Anatoli >
