Re: git clone issues on 15.1-RELEASE on arm64
"Nenhum_de_Nos" <[email protected]> Sat, 01 Aug 2026 19:41:54 +0000
| Newsgroups | gmane.os.freebsd.stable |
|---|---|
| Message-ID | <[email protected]> |
--ca6a8c89-ae5e-4840-8ef9-f0d5a872ca86-1 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable August 1, 2026 at 12:51 PM, "Karl Denninger" <[email protected] mailto:k= [email protected]?to=3D%22Karl%20Denninger%22%20%3Ckarl%40denninger.net%3= E > wrote: >=20 >=20Chase the certificate chain for the FreeBSD certificate and see wheth= er or not you've got the root and any required and immediate signing cert= ificates for it.=20=20 >=20=20 >=20There have been a couple of updates to root certificates recently. Th= e ones that are being used now to issue the new actual SSL certificates i= n the case I ran into date from 2022. But if your root store is sufficien= tly old it may not have the chain in it. I've run into that with a couple= of people on my forum that have older out of support devices that were g= etting errors on the certificate being untrusted when it really isn't and= that particular site had its certificate rollover within the last week.= =20 >=20=20 >=20=20 >=20 >=20=20 >=20 > >=20 >=20>=20 >=20> >=20 Hi=20Karl, I have quite no clue on how to do that, but I will try to figure out how = to do that later today. When I read your mail my first thought was the date and time of the box. = But that was ok, I just double checked. thanks, matheus --ca6a8c89-ae5e-4840-8ef9-f0d5a872ca86-1 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <!DOCTYPE html><html><head><meta http-equiv=3D"Content-Type" content=3D"t= ext/html; charset=3Dutf-8"></head><body><div><br><br></div><p>August 1, 2= 026 at 12:51 PM, "Karl Denninger" <<a href=3D"mailto:[email protected]= t?to=3D%22Karl%20Denninger%22%20%3Ckarl%40denninger.net%3E" target=3D"_bl= ank" tabindex=3D"-1">[email protected]</a>> wrote:</p><blockquote><di= v><span dir=3D"ltr" style=3D"margin-top: 0px; margin-bottom: 0px;">Chase = the certificate chain for the FreeBSD certificate and see whether or not = you've got the root and any required and immediate signing certificates f= or it. </span> <br> <br><span dir=3D"ltr" style=3D"margin-top: 0px; margin-bottom: 0px;">Th= ere have been a couple of updates to root certificates recently. The ones= that are being used now to issue the new actual SSL certificates in the = case I ran into date from 2022. But if your root store is sufficiently ol= d it may not have the chain in it. I've run into that with a couple of pe= ople on my forum that have older out of support devices that were getting= errors on the certificate being untrusted when it really isn't and that = particular site had its certificate rollover within the last week.</span> <br> </div><div> </div><div><br></div><div> </div><div><blockquote style=3D"margin: 0px; border-left: 3px solid r= gb(204, 204, 204); padding-left: 10px;"> </blockquote> </div></blockquote><div>Hi Karl,</div><div><br></div><div>I have quite = no clue on how to do that, but I will try to figure out how to do that la= ter today.</div><div><br></div><div>When I read your mail my first though= t was the date and time of the box. But that was ok, I just double checke= d.</div><div><br></div><div>thanks,</div><div><br></div><div>matheus</div= ></body></html> --ca6a8c89-ae5e-4840-8ef9-f0d5a872ca86-1--