Easiest fix is to just use SSH for your git connections. change https:/// github.com/DragonFlyBSD/DragonFlyBSD.git to [email protected]:DragonFlyBSD/DragonFlyBSD.git and you won't have that issue.
On Sun, Apr 30, 2017 at 10:13 AM, PeerCorps Trust Fund < [email protected]> wrote: > Same issue here. Running on 4.9-DEVELOPMENT DragonFly > v4.9.0.223.g4f0ea-DEVELOPMENT. Also after a pkg upgrade. > > Michael > > > On 04/30/2017 05:28 PM, Tim Darby wrote: > >> I did a pkg upgrade at the same time, so I wonder if libressl is to blame. >> >> Tim >> >> On Sun, Apr 30, 2017 at 7:16 AM, Tim Darby <[email protected]> wrote: >> >> I just updated to the latest master and noticed this: >>> >>> % git clone https://github.com/DragonFlyBSD/DragonFlyBSD.git >>> Cloning into 'DragonFlyBSD'... >>> fatal: unable to access 'https://github.com/DragonFlyB >>> SD/DragonFlyBSD.git/': >>> SSL certificate problem: unable to get local issuer certificate >>> >>> I've never had to tell git where to find its CA certs: >>> >>> % git config --global http.sslCAinfo /etc/ssl/certs/cert.pem >>> % git clone https://github.com/DragonFlyBSD/DragonFlyBSD.git >>> Cloning into 'DragonFlyBSD'... >>> remote: Counting objects: 508865, done. >>> remote: Compressing objects: 100% (52/52), done. >>> >>> Tim >>> >>> >> -- Sincerely, Zachary Crownover
