Workaround for fetching files

Workaround for fetching files

[Arno]

My question: Can I download some files that gives errors fetching during the build process and a new bitbake will recognise it? Probably it is not so simple, due to all this fancy stuff with timestamps .....
But - is there a way?

I am in a company network, due to strict rules I am often faced with problems fetching file.
So I am not able to use git protocol, most http(s) is the workaround.

Sometimes I can access files by browser (sources.openembedded.org/git2_git.yoctoproject.org.yocto-kernel-tools.git.tar.gz)
but the yocto build process can't and gives errors.

Either there is a problem with certificates (and even "export GIT_SSL_NO_VERIFY=1" before calling bitbake doesn't help") or there is "No route to host"

ERROR: Fetcher failure: Fetch command failed with exit code 128, output:
fatal: unable to access 'https://github.com/Xilinx/linux-xlnx.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none


DEBUG: Fetcher failure: Fetch command failed with exit code 128, output:
fatal: unable to connect to git.yoctoproject.org:
git.yoctoproject.org[0: 140.211.169.56]: errno=No route to host

Best regards
Arno

Re: Workaround for fetching files

[Alexander Kanavin]

On 05/27/2016 04:48 PM, Arno wrote:
> My question: Can I download some files that gives errors fetching during the build process and a new bitbake will recognise it? Probably it is not so simple, due to all this fancy stuff with timestamps .....
> But - is there a way?
>
> I am in a company network, due to strict rules I am often faced with problems fetching file.
> So I am not able to use git protocol, most http(s) is the workaround.
>
> Sometimes I can access files by browser (sources.openembedded.org/git2_git.yoctoproject.org.yocto-kernel-tools.git.tar.gz)
> but the yocto build process can't and gives errors.

Did you study this?
https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy

Alex

Re: Workaround for fetching files

[Arno]

> Gesendet: Freitag, 27. Mai 2016 um 15:59 Uhr
> Von: "Alexander Kanavin" <alexander.kanavin@linux.intel.com>
> An: poky@yoctoproject.org
> Betreff: Re: [poky] Workaround for fetching files
>
> On 05/27/2016 04:48 PM, Arno wrote:
> > My question: Can I download some files that gives errors fetching during the build process and a new bitbake will recognise it? Probably it is not so simple, due to all this fancy stuff with timestamps .....
> > But - is there a way?
> >
> > I am in a company network, due to strict rules I am often faced with problems fetching file.
> > So I am not able to use git protocol, most http(s) is the workaround.
> >
> > Sometimes I can access files by browser (sources.openembedded.org/git2_git.yoctoproject.org.yocto-kernel-tools.git.tar.gz)
> > but the yocto build process can't and gives errors.
> 
> Did you study this?
> https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy
> 
> Alex
> 

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.

Regards
Arno

Re: Workaround for fetching files

[Alexander Kanavin]

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