Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Agent refused operation when launching multiple requests #532

Open
dmedlin-git opened this issue Feb 19, 2024 · 5 comments
Open

Agent refused operation when launching multiple requests #532

dmedlin-git opened this issue Feb 19, 2024 · 5 comments

Comments

@dmedlin-git
Copy link

When attempting to use an app like csshX to launch SSH connections to multiple hosts at once only one of the connections is allowed to request access to the agent at a time, the rest are denied and present the below error. I have confirmed it happens in both 2.4.1 as well as 2.4.0. Downgrading to 2.3.1 restores ablility to use csshX to launch multiple connections again.

"sign_and_send_pubkey: signing failed for ECDSA "ecdsa-sha2-nistp256" from agent: agent refused operation"

@dmedlin-git
Copy link
Author

I think the github ci/cd job failed on this one. Adding a comment to try and get it to run again.

@walthowd
Copy link

Same issue here -- Can recreate on >= 2.4.0 with something like that tries three concurrent SSH connections -- In this example, only the last server (server3) connects. This same command works fine on 2.3.1

$ printf "%s\0" server1 server2 server3 | xargs -0 -I {} -P3 ssh {} id
sign_and_send_pubkey: signing failed: agent refused operation
root@server1: Permission denied (publickey).
xargs: ssh: exited with status 255; aborting
sign_and_send_pubkey: signing failed: agent refused operation
root@server2: Permission denied (publickey).
uid=0(root) gid=0(root) groups=0(root)

@palandine
Copy link

Experiencing the same issue. This used to work however. I recall being able to log in using csshX followed by endless finger tapping on the sensor due to the many sessions I was opening. I can't pinpoint the version that changed this behaviour however. It feels like a bit under one year orso.

@walthowd
Copy link

It works under 2.3.1 for me, upgrading past that breaks it

@palandine
Copy link

So probably these two commits were the cause:
#497

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants