unauthenticated git protocol on port 9418 for shFlags

[jean-cedric-therond-koji]

Because the 11th january 2022 Github said:

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

So, You have to change the submodule origin, while users can perform the next command to avoid getting this error:

$ git config --global url."https://".insteadOf git://

[stuartherbert]

Thanks for the heads' up. I'll sort out a fix in the next couple of days.

[mikebronner]

So, You have to change the submodule origin, while users can perform the next command to avoid getting this error:

$ git config --global url."https://".insteadOf git://

@jean-cedric-therond-koji Do you have any recommendations on making this setting more specific to, as it breaks communication for other apps that communicate with git. Is there any way to make this setting specific to HubFlow as a work-around until HubFlow is fixed?

[jean-cedric-therond-koji]

Do you have any recommendations on making this setting more specific to, as it breaks communication for other apps that communicate with git. Is there any way to make this setting specific to HubFlow as a work-around until HubFlow is fixed?

@mikebronner Do the same but in the hubflow folder and without the --global flag:

$ git config url."https://".insteadOf git://

[ragnarok22]

Is this project deprecated? I saw the last commit was in 2018

[stuartherbert]

I've just released gitflow v1.5.4, which should fix this issue. Let me know if you still have any problems.

[mikebronner]

@stuartherbert Thanks for this, small item of feedback after upgrading (and verified that your change is in place):

╰─❯ git hf version
1.5.3 - upgrade available

I'm still testing if everything else works without all the work-arounds. Thanks! :)