Signing Failed : Agent refused operation
I just tried setting up an SSH key with PGP signing following the instructions. When I do a git pull
from Gitlab I get this:
sign_and_send_pubkey: signing failed for ED25519 "GitLab" from agent: agent refused operation
However, it still worked. I can only assume it's using one of my existing SSH Keys task?
1Password Version: 1Password for Mac 8.10.6 (81006027)
Extension Version: 2.10.0
OS Version: macOS Ventura 13.3.1 (a) (22E772610a)
Browser:_ Chrome 113.0.5672.92 (Official Build) (arm64)
Comments
-
I have the same error reporting will trying to access a server via SSH, however my connection will not succeed. Eager to get a solution for this, as I think I am going to love this ssh feature!
I get:
lucas@MacBook-Pro ~ % ssh root@68.xx.xx.xx sign_and_send_pubkey: signing failed for ED25519 "DigitalOcean" from agent: agent refused operation root@68.xx.xx.xxx: Permission denied (publickey).
0 -
Hey @lucas1122 and @bradleyrobertson.
Thanks for reporting this!Are you still encountering this issue? If so could you try reproducing it and looking at the logs? You can find the logs under 'Help' -> 'Troubleshooting' -> 'Open Logs folder' ->
1Password_rCURRENT.log
Please let me know if you see any logs related to the ssh agent.
Thanks,
Márton0 -
It worked after restarting my computer
0 -
@MartonS1P After support from Dayton it worked following these steps:
Thanks so much for your reply! Could you try the steps below, and let me know if the SSH agent works for you
Open the 1Password desktop app and sign in.
Click the account/vault selector in the top-left corner of the app, then click Settings from the dropdown.
Switch to the Developer tab, and expand the Security section.
Change Ask approval for each new to a different option, then back to the original selection. For example, if you have it set to Application, then change it to Application and terminal session, then back toApplication.
Lock 1Password, then unlock it again.
Attempt an SSH action in your terminal.0 -
@lucas1122 -- wow, that worked for me too. Spent way too much time trying to figure out what I had set up wrong.
0 -
Messsge gone 🥲
0 -
@mitchblank please be assured. You didn’t do anything wrong. It’s a bug which will be fixed in one of next releases.
0 -
Indeed. Sorry about the bug @mitchblank, it should already be fixed on the latest nightly and beta.
0