Github changes

[Justin C. Walker]

This is somewhat off-topic, but I just ran into an issue with GitHub, and I am not sure how to handle it.

I use this command to “git” the sage tree when Volker announces a new one:
git clone git://github.com/sagemath/sage.git

I now get an immediate response:
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.

I looked at the web page mentioned, and, if I understand what is described (not entirely clear), I just need to replace “git:” with “https:”. But the next paragraph mentions that they have removed support for passwords over HTTPS.

So I’m a bit confused. Was this discussed on Sage lists?

Thanks for pointers or hints!

Justin

PS: the change happened in the last day or so; I had cloned the tree a day or two ago on other systems without problems

--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Absorption of Federal Funds
--------
If you're not confused,
You're not paying attention
--------

[Dima Pasechnik]

On Tue, Jan 11, 2022 at 8:52 PM 'Justin C. Walker' via sage-release
<sage-r...@googlegroups.com> wrote:
>
> This is somewhat off-topic, but I just ran into an issue with GitHub, and I am not sure how to handle it.
>
> I use this command to “git” the sage tree when Volker announces a new one:
> git clone git://github.com/sagemath/sage.git
>

try

git clone https://github.com/sagemath/sage.git

HTH
Dima

> I now get an immediate response:
> 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.
>
> I looked at the web page mentioned, and, if I understand what is described (not entirely clear), I just need to replace “git:” with “https:”. But the next paragraph mentions that they have removed support for passwords over HTTPS.
>
> So I’m a bit confused. Was this discussed on Sage lists?
>
> Thanks for pointers or hints!
>
> Justin
>
> PS: the change happened in the last day or so; I had cloned the tree a day or two ago on other systems without problems
>
> --
> Justin C. Walker, Curmudgeon-At-Large
> Institute for the Absorption of Federal Funds
> --------
> If you're not confused,
> You're not paying attention
> --------
>
>
>

> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/2A4C9EF3-7F24-4E1B-B549-B1E878CE0E53%40mac.com.

[Justin C. Walker]

> On Jan 11, 2022, at 12:55 , Dima Pasechnik <dim...@gmail.com> wrote:
>
> On Tue, Jan 11, 2022 at 8:52 PM 'Justin C. Walker' via sage-release
> <sage-r...@googlegroups.com> wrote:
>>
>> This is somewhat off-topic, but I just ran into an issue with GitHub, and I am not sure how to handle it.
>>
>> I use this command to “git” the sage tree when Volker announces a new one:
>> git clone git://github.com/sagemath/sage.git
>>
>
> try
>
> git clone https://github.com/sagemath/sage.git

D’oh! I would have tried that if I could spell.

Thanks, Dima, worked like a champ.

Justin

[David Coudert]

I experienced the same issue and did git clone  https://github.com/sagemath/sage.git.

It’s working fine now.

Git trac is still working well so far.

David.

-- 
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/0AF4E63D-6F64-4B5A-8A59-2D3B62C95940%40mac.com.