Hello! Okay, I tried setting that variable, and it did not show me anything. I also looked at the page you suggested. Interesting, I suspect I'd need to do that should I go ahead and want to contribute.
As for updating certificates, the big problem is that is a WSL prebuilt image, and someone else built it, and deliberately broke the methods SuSe uses to update things. ----- Gregg C Levine [email protected] "This signature fought the Time Wars, time and again." On Thu, Sep 30, 2021 at 3:37 PM Patrick Georgi <[email protected]> wrote: > > Hi Gregg, > > Am Do., 30. Sept. 2021 um 21:16 Uhr schrieb Gregg Levine > <[email protected]>: >> >> fatal: unable to access 'https://review.coreboot.org/coreboot.git/': >> SSL certificate problem: certificate has expired > > > Given the timing, I wonder if > https://techcrunch.com/2021/09/21/lets-encrypt-root-expiry/ might be the > cause: We serve a pretty complete certificate chain but if your client > doesn't support the root certificate that we now rely on exclusively (because > the other path using the more popular root has expired), your client won't > like any of our certs. > > You could try changing the environment to carry GIT_CURL_VERBOSE=true to see > what's going on, or maybe just look at updating the ca-certificate store of > your system. > > Alternatively you could set up the SSH based access method to access the > server, as outlined in > https://doc.coreboot.org/tutorial/part2.html#step-2a-set-up-rsa-private-public-key > but you might run into more issues with certs going forward on other servers > if the cert store is old. > > > All the best, > Patrick > -- > Google Germany GmbH, ABC-Str. 19, 20354 Hamburg > Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: > Hamburg > Geschäftsführer: Paul Manicle, Halimah DeLaine Prado _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
