Installing the latest version of 1Password fixed it for me!

I'm now running 1Password 8.10.8, Git 2.41.0 and OpenSSH_9.3p1, OpenSSL 3.0.9 30 May 2023

I am receiving the same error in the same situation. Is there a remedy for this problem yet?

I get this occasionally with the VSCode Git integration, though if I try again after it fails it usually works. I don't use the Git CLI very much but I don't think I've had the issue there, but could be wrong.

I am on macOS Ventura with 1Password for Mac 8.10.7 (81007041).
Git version: 2.41.0
OpenSSH version: OpenSSH_9.0p1, LibreSSL 3.3.6

Correct. op-ssh-sign gives that whole buffer error.

And the error message you're getting with op-ssh-sign, is that error: failed to fill whole buffer as well?


git version 2.40.1
OpenSSH_9.3p1, OpenSSL 3.0.9 30 May 2023


Which versions of Git and OpenSSH are you using? git --version && ssh -V

Running this:

SSH_AUTH_SOCK=~/.1password/agent.sock ssh-add -L | grep "$(git config user.signingkey)"

returns nothing, even though the output of SSH_AUTH_SOCK=~/.1password/agent.sock ssh-add -L:

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAeqrr+kvXVWD+BdrP49t8ul/wvKQyXQ/bavjT5JJoLK JumpCloud
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIODV5S21+jV0900ubPoYvdHol/xfbJjVhxayuMEFuPKo GitHub signing key

clearly contains the output of "$(git config user.signingkey)":

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIODV5S21+jV0900ubPoYvdHol/xfbJjVhxayuMEFuPKo

And with the shim for ssh-keygen:
```
git commit --allow-empty -m "foo" -S

error: Signing file /tmp/.git_signing_buffer_tmpNpihD5
Couldn't sign message (signer): communication with agent failed?
Signing /tmp/.git_signing_buffer_tmpNpihD5 failed: communication with agent failed?

fatal: failed to write commit object
```

Just checking to make sure: does this command return your signing key?

SSH_AUTH_SOCK=~/.1password/agent.sock ssh-add -L | grep "$(git config user.signingkey)"


And it could be useful to get your ssh-keygen -v logs. To add the -v flag, I believe you'll have to create a shim for the ssh-keygen command:
```

!/bin/sh

ssh-keygen -v "$@"
```

And run:

chmod +x /path/to/shim
git config gpg.ssh.program /path/to/shim


Yes, SSH_AUTH_SOCK is set. I can't see anything related to this in the logs, unfortunately...