Beta Git client and SSH keys

Hi all,

Has anyone managed to get SSH keys working in the beta Git client?

I generated a key on my MacBook and added it to my ROOL GitLab account. All good. I can check-out from ROOL.

I tried with GitHub, and I get an error about the encryption type being deprecated. Is anyone using the Git client with GitHub? Is there some magic I need to do to generate a key with a newer encryption type, but still in the old format which the Git client will accept?

Has anyone managed to get SSH keys working in the beta Git client?

Can’t speak for “anyone” but I tried a while back and got the same result as you. I did report the problem (informally) to the ROOL stand at the SouthWest Show.
In the meantime I continue to use Git command line for everything on RISC OS. So far it has been faultless.

I tried with GitHub, and I get an error about the encryption type being deprecated

Untested by me, but if you want to beef up the encryption but still write out as a PEM file (PEM isn’t “old” as far as I can tell) try

ssh-keygen -t ecdsa -m PEM

or

ssh-keygen -t rsa -b 4096 -m PEM

I did report the problem (informally) to the ROOL stand at the SouthWest Show.

I wrote down the question and passed it on on 25-Feb-2024 to ROOL’s Git expert, I think you got a reply (which I was copied on) to the effect that you’d used an ancient version of ssh-keygen from riscos.info from circa 2014 and that didn’t generate keys with enough bits by default for GitHub’s requirements. ie. it wasn’t that the Git client was doing something odd, merely passing along a SHA-1 key which they don’t accept now.

Ah-ha! I was assuming that someone here had been there and got the t-shirt, but actually, your magic untested incantation of options there has done the trick! So thank you very much for that.

For anyone else doing the same, then you want:

ssh-keygen -t ecdsa -m PEM

Also, the git client StrongHelp file has the Public/Private key filenames mixed-up.