The unauthenticated git protocol on port 9418 is no longer supported

by

First, this error message is indeed expected on Jan. 11th, 2022.
See “Improving Git protocol security on 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.

Second, check your package.json dependencies for any git:// URL, as in this example, fixed in this PR.

As noted by Jörg W Mittag:

There was a 4-month warning.
The entire Internet has been moving away from unauthenticated, unencrypted protocols for a decade, it’s not like this is a huge surprise.

Personally, I consider it less an “issue” and more “detecting unmaintained dependencies”.

Plus, this is still only the brownout period, so the protocol will only be disabled for a short period of time, allowing developers to discover the problem.

The permanent shutdown is not until March 15th.

For GitHub Actions:

As in actions/checkout issue 14, you can add as a first step:

    - name: Fix up git URLs
      run: echo -e '[url "https://github.com/"]\n  insteadOf = "git://github.com/"' >> ~/.gitconfig

That will change any git://github.com/ into https://github.com/.

For local projects

For all your repositories, you can set:

git config --global url."https://github.com/".insteadOf git://github.com/

You can also use SSH, but GitHub Security reminds us that, as of March 15th, 2022, GitHub stopped accepting DSA keys. RSA keys uploaded after Nov 2, 2021 will work only with SHA-2 signatures.
The deprecated MACs, ciphers, and unencrypted Git protocol are permanently disabled.

So this (with the right key) would work:

git config --global url."[email protected]:".insteadOf git://github.com/

That will change any git://github.com/ (unencrypted Git protocol) into [email protected]: (SSH URL).

More Related Contents:

  1. Push to origin from GitHub action
  2. Automatically Deploy From GitHub To Server On Push
  3. How can I remove a commit on GitHub? [duplicate]
  4. Git commands that could break/rewrite the history
  5. Git submodules in .gitmodules not initialized
  6. git ahead/behind info between master and branch?
  7. GitHub “fatal: remote origin already exists”
  8. Github: error cloning my private repository
  9. How to update a pull request from forked repo?
  10. Git’s famous “ERROR: Permission to .git denied to user”
  11. GitHub clone from pull request?
  12. GitHub: Permission denied (publickey). fatal: The remote end hung up unexpectedly
  13. Why does “git push main” work on GitHub when “git push master” does not? Also what is difference between “Main branch” and “Master branch”?
  14. Git push hangs when pushing to Github?
  15. Delete local Git branches after deleting them on the remote repo
  16. Issue pushing new code in Github
  17. What is “git remote add …” and “git push origin master”?
  18. How to sync changes on my local server with the ones on the remote one without commiting?
  19. Why are connections to GitHub over SSH throwing an error “Warning: Remote Host Identification Has Changed”?
  20. Git : fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists
  21. Squash all my commits into one for GitHub pull request [duplicate]
  22. Permission denied error on Github Push
  23. “Cannot spawn ssh” when connecting to Github, but ssh -T [email protected] works?
  24. How to pull a pull request quickly locally
  25. Git – How to auto push changes in a directory to another branch
  26. How to clone git repository from its zip
  27. git push error: src refspec main does not match any on linux
  28. How to install/setup TortoiseGit to work with GitHub
  29. How can I reduce the ever-increasing time to push a subtree?
  30. GitHub Api download zip or tarball link

Leave a Comment