Re: Something wrong at git?

On 5/26/25 12:53 PM, Bob Melson wrote:
> For the past several days all calls to git to update /usr/src or 
> /usr/ports have failed with the following error mesage:
>
> fatal: unable to access 'https://git.FreeBSD.org/src.git/': server 
> verification failed: certificate signer not trusted. (CAfile: none 
> CRLfile: none)
>
> or
>
> fatal: unable to access 'https://git.FreeBSD.org/ports.git/': server 
> verification failed: certificate signer not trusted. (CAfile: none 
> CRLfile: none)
>
>
> On the surface, this appears to indicate a problem at git, but it 
> could also be that I've screwed something up locally.


The Let's Encrypt cert offered up by git.freebsd.org went valid on 21 
April, so probably has been in place since then.  It's valid in any case.

Personally I'm looking a different surface than you appear to be:  
"server verification failed: certificate signer not trusted. (CAfile: 
none CRLfile: none)" sorta sounds more like you don't trust any certs 
since you've deleted, moved, or broken linkage to your root CA trust 
store.  Do other tools that speak HTTPS (curl, wget, what-have-you) on 
that machine trust certs from Let's Encrypt?  That might well narrow 
down what's broken.

BTW, going to one of those URLs from a random functional browser would 
have narrowed things down very quickly.


-- 
--Jon Radel
jon@radel.com