Re: Workaround for fetching files

[Alexander Kanavin <alexander.kanavin@linux.intel.com>]

On 05/30/2016 11:49 AM, Arno wrote:

> Its not the proxy, we don't have this. But we have some kind of
> firewall which seems to work also for https as man in the middle.
> With our company certificates installed in browser it works.
>
> If I do manually a git (via https) with  "export GIT_SSL_NO_VERIFY=1"
> this helps, but even if I do this before calling bitbake it will not
> help. Can this set global for the project?
>
> Doesn't the download files stored in a common folder, but there is
> also some hash, which I can't create manually.

You have what they call a 'transparent proxy'. When https is in use by 
git, you can probably add those rogue man-in-the-middle certificates to 
/etc/ssl/certs, but for native git protocol this isn't going to work, as 
your firewall simply blocks those connections out (the 'no route to 
host' thing).  [1]

You need to explain to your management that to do your job properly, you 
need a real internet connection, or a SOCKS proxy (for the git 
protocol). But then they wouldn't be able to spy on you.

[1] https://git-scm.com/book/no-nb/v1/Git-on-the-Server-The-Protocols


Alex