4 replies to this topic

[foxbob]

I run compilation and immediately an error

sttools"; export HOME="/home/foxbob"; git -c core.fsyncobjectfiles=0 ls-remote git://github.com/LraiZer/RadiotimesXmltvEmulator.git  failed with exit code 128, output:
fatal: remote error: 
  The unauthenticated git protocol on port 9418 is no longer supported.
Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.

A source:https://github.blog/...ecurity-github/

Now git:// -does not work, must be changed to http://

Or is it just me.

[WanWizard]

I think it depends on whether you have github authentication active or not. If I (or our buildservers) access that URL, it sends the local ssh key which is known to github.

 

But I agree, since it is used read-only, all git:// should be changed to https:// to avoid forcing everyone to create github accounts and upload ssh keys.

[A.A.]

The issue is really nasty, see OE:

 

https://lists.openem...re/message/1327

[foxbob]

I updated my SSH keys on github.com which expired after a month and the build continued.

[WanWizard]

The issue is really nasty, see OE:

 

Yup, I've already started on it for meta-openpli, but I made a mistake (can't test atm, in the middle of a house move).

 

I'm going to revert in a minute, and try again.

 

What is really nasty, is what will happen with all the legacy? i.e. the older branches? Is OE going to update them all?