>Note that the setting is per-clone by default, so if you set up coreboot to be
>without sslVerify, that doesn't apply to the board_status repo unless you also
>used --global.
Yes, I have it configured globally using ~/.gitconfig file
[http]
sslVerify = false
proxy = http://<user>:<passwd>@<ip_host>:<port>/
[https]
sslVerify = false
proxy = http://<user>:<passwd>@<ip_host>:<port>/
Am Mo., 9. Dez. 2019 um 11:11 Uhr schrieb Jorge Fernandez Monteagudo
<[email protected]>:
>We moved the other thread off-list, but the issue was that there's a https
>proxy in the way that
>terminates SSL connections.
>
> I documented the approach to deal with that in
> https://review.coreboot.org/c/coreboot/+/37599
Hi,
I'm still stuck with the same error trying to push anything. Disabled
validating certs as pointed in
your change doesn't solve my issue. But it's related to my workstation or
company's proxy server
because the same user works at home and I can login and send patches...
Regards
Jorge
--
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]
