Bob Proulx wrote: > Simon Josefsson wrote: > > Thanks for the upgrade! If anyone except me was greeted by the > > following strange error after the upgrade: > > > > jas@kaka:~/src/gnulib$ git pull > > sign_and_send_pubkey: signing failed for ED25519 "cardno:FFFE42315277" from > > agent: agent refused operation > > j...@git.sv.gnu.org's password: > > > > The reason is that you are running a too old GnuPG version. Alas > > Trisquel 11 (and therefor Ubuntu 22.04) is shipping this old version, so > > many may be affected. See bug report here: https://dev.gnupg.org/T5931
Having read through the linked bug tickets I am thinking this is a client side upgrade issue. Are you running Arch? Did you upgrade recently and move to a newer version of OpenSSH on your system? Because Arch is a rolling release system quite often problem reports end up finding that there are Arch system client side upgrade issues. It happens so routinely with ssh particularly that when problems like these arise I just ask if this is an Arch client side upgrade problem right up front now. I tested using Debian Unstable's OpenSSH_9.8p1 and gpg 2.2.43 and could not reproduce any errors using either of those versions. I am using the OpenSSH ssh-agent and the gpg-agent is not involved in the git+ssh:// protocol interacting with the upstream git repository server. I am not using a hardware auth token but the linked bug reports referenced USB hardware tokens. If it is associated with a USB hardware token then I am going to be unable to reproduce the problem here. I'll repeat the server side versions in use here just to help clarify what versions are where. vcs2 is the old and now once again currently production server. vcs3 was running when you made your report. You can force a local /etc/hosts override to select vcs3 in order to test that software combination again. vcs2 <- git currently - Trisquel 9 (Ubuntu 18.04) - gpg (GnuPG) 2.2.4 - OpenSSH_7.6p1 vcs3 <- git when you made your report - Trisquel 11 (Ubuntu 22.04) - gpg (GnuPG) 2.2.27 - OpenSSH_8.9p1 I am afraid I will need more help and information in order to understand what is happening any further than this. Since you are the only one (so far) reproducing this problem I am afraid I will need your help with it. Any help you can give debugging this would be great! Bob
