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
SSH: Agent Refused Operation #105
Comments
There was a recent upgrade to the |
I'm in the same boat, as a temporary workaround run:
|
i got two devices
YubiKey NEO
i have tested with the |
Hi, same issue here with a Yubikey 5 NFC. Firmware is 5.4.3. systemctl --user status yubikey-agent show this error :
It did work when I set it up... :/ |
After some test, reboot doesn't solve the issue, but disabling and re-enabling yubikey-agent service seems to work ?! I'll try to do more in depth testing :). |
Same issue here, restarting & disable/enabling the yubikey-agent did not solve the problem. |
I've built from
|
Try this : open a terminal, unplug your Yubikey, replug, wait a few second and replug. It works for me. It was GPG agent that was hijacking the key |
If |
I'm running into this issue only when running yubikey-agent using systemd. If I stop the systemd service and run
to the systemd service. Not sure why it wasn't able to pick that up automatically or if there's a cleaner way to solve the issue. Probably also related to #92. |
I get the error even when running
|
this have solve my issue |
My workaround (WSL2 + Ubuntu on Windows) for this issue (or a related one, I also got the
|
Hello, I encountered the same errors ( In my case, yubikey-agent worked fine after enabling/disabling the service or a restart of the service after a reboot. I came to the conclusion that some ressource seems not to be available at the start of the service. I tried However, the following line in the service file helped:
After that everything works fine. I don't understand what resource might be missing as the yubikey-agent service starts in user context, so everything else should already be started. |
I have the following two devices:
My laptop is running Manjaro Linux (Kernel 5.10.70).
Steps taken:
yubikey-agent -setup
on each hardware device. No problems, received a public key for each..ssh/authorized_keys
file onremoteserver
IdentityAgent /run/user/1000/yubikey-agent/yubikey-agent.sock
to the.ssh/config
entry forremoteserver
on my laptop.yubikey-agent
is running and bound to the above socket.I'm on Manjaro, and the
yubikey-agent
logs are getting dumped into the syslogs. Is there a way to configure where the logs go?With
journalctl | grep yubikey-agent
I see:I'm not really sure what else to do with this. Did I miss a step? At what point is it supposed to ask me for pin entry? I'm surprised also that it is using ECC with the 5.12 firmware device which is said not to support ECC. I'm not sure how the key generation succeeded there.
The text was updated successfully, but these errors were encountered: