Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
kzolnowski
3 years agoOccasional Contributor
ssh-agent stopped working
Hi,
After last nigthly update ssh-agent stopped working with error:
sign_and_send_pubkey: signing failed for ED25519 "SSH key ed25519 private" from agent: agent refused operation
Here's a log...
mjec
3 years agoNew Contributor
I too am seeing this error trying to use ssh-agent forwarded over an ssh connection:
1password.desktop[84193]: INFO 2022-10-28T13:04:20.199 tokio-runtime-worker(ThreadId(2)) [1P:foundation/op-sys-info/src/process_information/linux.rs:367] no GUI info available to determine top level parent
1password.desktop[84193]: WARN 2022-10-28T13:04:20.199 tokio-runtime-worker(ThreadId(2)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 40121
PID 40121 is my ssh connection to $remote
. I can run ssh-add -L
successfully on $remote
, but any attempt to use the key fails with the above appearing in debug logs.
This happens only when using agent forwarding.
Versions:
* 1Password for Linux 8.9.8 (80908001) running swaywm on Linux 6.0.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 15 Oct 2022 14:00:49 +0000 x86_64 GNU/Linux.
* Local ssh: OpenSSH_9.1p1, OpenSSL 1.1.1q 5 Jul 2022
* Remote ssh: OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017
I can reproduce consistently with that setup, but things work fine when remote ssh version is OpenSSH_9.0p1, OpenSSL 1.1.1q 5 Jul 2022. This is surprising to me.
Let me know if I can be of further assistance in debugging; I can reliably reproduce, and am happy to run debug builds etc if that's helpful.