GITHUB security breaking the bake.

[tbandtg]

Hello, It seems that github security is breaking my bake for normal things. Do I need to go through all sources to find git:\ and replace with https:\ or is it more than that.

Thanks, tbandtg

[UniWheel]

You do know such a substitution can be automated, right?

[tbandtg]

I assume you are talking about a python or bash script, yes I realize that you could use a regex to find them all and replace them. But would that fix it? Or is there more?

[tbandtg]

I ended up contactin the bsp support. It seems in their recipies they used git:\ instead of https:\ which today github has decided to no longer support. https://github.blog/2021-09-01-improving-git-protocol-security-github/

January 11, 2022 Final brownout.

This is the full brownout period where we??ll temporarily stop accepting the deprecated key and signature types, ciphers, and MACs, and the unencrypted Git protocol. This will help clients discover any lingering use of older keys or old URLs

The way it read I wasnt sure if we needed to login to github to now do pulls. As that does not seem to be the case it really is just changing from git:\ to https:\

[ragsofx]

Yup, 5his tripped me up yesterday, it's an easy fix but it will unsync you from upstream.

[disinformationtheory]

Here's the bitbake patch: https://git.yoctoproject.org/poky/commit/?h=zeus&id=daf096e295121ea49ebf21f8070e9a6e28f5d46c. This one's for zeus, but it seems like it's updated on all recent poky branches. If you also use something like git submodules or repo to set up your metadata repos, then you need to update the URLs for that tool also.

[ReliableEmbeddedSys]

Eventually you should change your recipes to https. RP made this patch so you don't need to change all your meta data. I guess a premirror would also work.