On Tue, Mar 29, 2022 at 10:01:26PM -0500, Jacob Bachmeyer via cfarm-users wrote: > Jeffrey Walton via cfarm-users wrote: > >fatal: remote error: > > The unauthenticated git protocol on port 9418 is no longer supported. > > While this does not help you, the root of this latter problem seems to > be that GitHub has decided to deliberately break compatibility with one > of Git's standard features using "security" as an excuse. This is, of > course, ridiculous for public repositories, since public repositories > are, well, public.
It is very inconvenient indeed, given that https:// has many problems of its own. The reasoning for it is that the git:// protocol has no protection against tampering. This is comparable to the motivation behind the http:// to https:// by default switchover we had years ago. But there is a huge difference: that was default only, and http:// still works on most systems: if the client decides to use it, the server side doesn't interfere. It of course took years of pain before many things decided it is not their place to make up policy for others. Maybe github will have more sane behaviour in a few years, too. Segher _______________________________________________ cfarm-users mailing list [email protected] https://lists.tetaneutral.net/listinfo/cfarm-users
