My current Buildroot configuration includes a package whose source is hosted on a GitLab server. Unfortunately this server has errors with its SSL certificate; when Buildroot reaches this package it tries to clone the repository, but Git throws an error regarding the SSL certificate and aborts.
This is reasonable behaviour, and the reasonable response would be to either:
- Fix the certificate
- Set up my machine to trust the certificate
Unfortunately, I'm also constrained by the following:
- I need an immediate workaround
- I don't have any administrator access to the server
- The workaround should work on machines without explicitly configuring them to trust this server
I think the GIT_NO_SSL_VERIFY
environment variable is the simplest solution. If I add this to Buildroot's EXTRA_ENV
variable, everything works as expected.
Unfortunately this disables SSL for all Git repositories cloned by Buildroot. Since there is only one Git repository with this issue, it feels wrong to disabled SSL for all Git repositories cloned through Buildroot.
It would be great if I could set EXTRA_ENV
to add GIT_NO_SSL_VERIFY
, but only for the package I'm having issues with. I can't find any suggestion that Buildroot supports this, but the documentation is sparse so I figured I'd ask here.
Thanks!