Issue with git signed commits: ssh-keygen error

[Ricky Olivier (ricky-lv426)]

I'm trying to commit changes to the my local git branch but I get the following error:

[ricky-lv426@puma2 lfric_apps]$ git commit -m "Merge in original fcm branch changes"
error: ssh-keygen -Y sign is needed for ssh signing (available in openssh version 8.2p1+)
error: unknown option -- Y?

Any suggestions on how to get around this problem? Its the first time I'm trying this.

[Jenny Hickson (jennyhickson)]

Hi Ricky,

Have you worked through the instructions for getting commit signing setup? https://metoffice.github.io/simulation-systems/WorkingPractices/gh_authorisation.html#verified-commits

[Ricky Olivier (ricky-lv426)]

Hi Jenny, yep I went through all of that. It looks like it's a ssh-keygen error pointing to an unknown --Y option. I am using a pretty old key.

[Ricky Olivier (ricky-lv426)]

Ah, looks like the OpenSSH version on puma2 is older than 8.2p1, that's probably the issue.

[Ricky Olivier (ricky-lv426)]

I'll try Archer2 instead which has version 8.4p1. If it works on Archer2, it might we worth flagging this up in the documentation?

[Ricky Olivier (ricky-lv426)]

Jenny Hickson (@jennyhickson) Just to be explicit, I can confirm it works on Archer2 which has a later version of OpenSSH.

[Yaswant Pradhan (yaswant)]

Ricky Olivier (@ricky-lv426) Yes, you will need minimum OpenSSH 8.2 (OpenBSD) or 8.2p1 (Portable) or higher for signed commits. We will add a note to the working practices FAQs.