diff options
| author | drduh <github@duh.to> | 2022-08-21 11:26:36 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-08-21 11:26:36 -0700 |
| commit | 0f0e427ff1f539c4387ac640ddb6d09d42630afc (patch) | |
| tree | 74d25d736ee6fc9c782735f1601748a31eca117e | |
| parent | Merge pull request #320 from SeanOMik/fedora-required-software (diff) | |
| parent | Add explanation of a possible fix for the `signing failed: agent refused oper... (diff) | |
| download | YubiKey-Guide-0f0e427ff1f539c4387ac640ddb6d09d42630afc.tar.gz | |
Merge pull request #318 from pmengelbert/agent-refused-operation-fix
Possible fix for the 'signing failed: agent refused operation' error
| -rw-r--r-- | README.md | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -2727,6 +2727,8 @@ Before you unmount your backup, ask yourself if you should make another one just - If you still receive the error, `sign_and_send_pubkey: signing failed: agent refused operation` - edit `~/.gnupg/gpg-agent.conf` to set a valid `pinentry` program path, e.g. `pinentry-program /usr/local/bin/pinentry-mac` on macOS. +- If you still receive the error, `sign_and_send_pubkey: signing failed: agent refused operation` - it is a [known issue](https://bbs.archlinux.org/viewtopic.php?id=274571) that openssh 8.9p1 and higher has issues with YubiKey. Adding `KexAlgorithms -sntrup761x25519-sha512@openssh.com` to `/etc/ssh/ssh_config` often resolves the issue. + - If you receive the error, `The agent has no identities` from `ssh-add -L`, make sure you have installed and started `scdaemon`. - If you receive the error, `Error connecting to agent: No such file or directory` from `ssh-add -L`, the UNIX file socket that the agent uses for communication with other processes may not be set up correctly. On Debian, try `export SSH_AUTH_SOCK="/run/user/$UID/gnupg/S.gpg-agent.ssh"`. Also see that `gpgconf --list-dirs agent-ssh-socket` is returning single path, to existing `S.gpg-agent.ssh` socket. |