Isn't this all already handled by: https://git.openembedded.org/openembedded-core/commit/?id=abb8895d5b42a5dc171360a261a2652acd14ee7e ?

<richard.purdie@...> wrote: I understand that, however, the reality is that organizations have IT teams which are catering to a wider set of security needs and have been

Some servers out there (e.g. our own git.yoctoproject.org) have slightly different git and https urls so this isn't as simple as you'd think. The security offered by https isn't as great as it first

Can we change bitbake fetcher to default to https instead git anonymous protocol as fallback? this will be good security measure too. <richard.purdie@...> wrote:

wrote: I've sent out a couple of patches for bitbake, one which does the remapping and a second which adds the warning. Testing would be appreciated before I merge them (I need to focus on master

I think we put a warning on master and forwards but not older bitbakes. Cheers, Richard

I totally agree with that. I still think we should also warn out so we don't have to maintain this magic quirk forever. Andrei

The brownouts are already happening, got 20+ failed jenkins jobs over night, because they failed to fetch various metadata layers over git:// from github. And hopefully my understanding of the

Thanks for reporting this, it helps to know this is happening as we'll probably start seeing odd error reports for the brownouts. I've updated the conversion script I mentioned earlier in this thread

The difference is that only few upstream repos are renaming master to main while removing the master branch completely and the change of the default branch to main affects only newly created repos on

The issue I think is the size of it. When you consider just the main branch for oe-core, this isn't an issue, but with all the release branches people are still on, with all the various layers some

Hi, OnTue, 2 Nov 2021, at 10:49, Andrei Gherzan wrote: And by GitLab I meanGitHub. Andrei

Hi, I don't think this is a bigger issue because I don't see this warranting a default change. It is just an upstream protocol support change and we will update the respective recipes. If we don't,

There is even bigger issue with git repos from github.com now: https://github.blog/2021-09-01-improving-git-protocol-security-github/#no-more-unauthenticated-git bitbake git fetcher uses git://

Yes, exact timing to be determined but hopefully sooner than later (before April release). Cheers, Richard

Although the situation is a bit unfortunate I like the proposal and the script will likely make the transition less painful. Are you planning to turn the warning into an error at some point?

We've had concerns about the default behaviours of tools like git and how they'll handle the default branch names going forward. There are also concerns about what providers like github may do, and

All, Our next OpenEmbedded Happy Hour is on October 27 for Asia/Pacific timezones @ 2100/9pm UTC (5pm ET / 2pm

Thanks, there might be that gizmo added then in the not too distant future :) Alex

Yes, I believe that was the intended usage: $ git clone git://git.yoctoproject.org/meta-lts-mixins -b dunfell/kernel meta-lts-kernel-mixin $ git clone git://git.yoctoproject.org/meta-lts-mixins -b