Re: Rectify agent/client mismatch 2.2.27/2.3.3

2024-10-14 Thread John Soo via Gnupg-users
Hi there! Thank you for following up - after wiping the forwarded ~/.gnupg directory and trying again this was fixed. Could this be related to the keyboxd change? --- John ___ Gnupg-users mailing list Gnupg-users@gnupg.org https://lists.gnupg.org/mailma

Re: Rectify agent/client mismatch 2.2.27/2.3.3

2024-10-08 Thread Werner Koch via Gnupg-users
Hi! On Mon, 7 Oct 2024 12:28, John Soo said: > there a way for me to put this client into an accessibility mode so > that the older agent will recognize the IPC commands? It is very hard > for me to upgrade either client or agent in this case. Without being able to update the cleint it will be

Rectify agent/client mismatch 2.2.27/2.3.3

2024-10-07 Thread John Soo via Gnupg-users
Posted on discourse but seems like the list is the right place to ask: I have a client at 2.3 and a gpg-agent at 2.2.27 connected via ssh remote forwarding. However I cannot list secret keys (see detail). Is there a way for me to put this client into an accessibility mode so that the older agent w

Rectify agent/client mismatch 2.2.27/2.3.3

2024-10-07 Thread John Soo via Gnupg-users
Posted on discourse but seems like the list is the right place to ask: I have a client at 2.3 and a gpg-agent at 2.2.27 connected via ssh remote forwarding. However I cannot list secret keys (see detail). Is there a way for me to put this client into an accessibility mode so that the older agent w