The agent has no identities (Archlinux/KDE)

jstnchristian
jstnchristian
Community Member
edited June 2023 in SSH

Hi all,

I've been going around the forums trying to figure this out, to no avail. I went through the setup guide, and all I'm getting at the end is:

$ ssh -T git@github.com

git@github.com: Permission denied (publickey).


$ ssh-add -l
The agent has no identities.

Config Screenies for verification:

What I've done (in order):

  • Cleared out my ssh config so it only contains:
$ cat ~/.ssh/config 
Host *
  IdentityAgent ~/.1password/agent.sock
  • Verified that ~/.1password/agent.sock exists:
$ cd ~/.1password && file agent.sock
agent.sock: socket
  • Ran ssh-add -l with explicitly passing SSH_AUTH_SOCK:
$ SSH_AUTH_SOCK=./agent.sock ssh-add -l
The agent has no identities.
  • Checked for SSH errors in the logs:
$ grep -i error ~/.config/1Password/logs/1Password_rCURRENT.log | grep -i ssh && echo "Found SSH" || echo "No SSH Errors"
No SSH Errors
  • Done the restart 1Password, reboot computer, etc. dance.

At this point, I'm kinda stuck. This is also happening on my Windows box (haven't done any troubleshooting there), so I have a guess that the keys are not being seen by 1P. I have a family account with a Shared vault, but all of my keys exist in my "Personal" vault (unless I'm misunderstanding the nature of a Personal vault in a family account). Example:

here's my public github key if anyone wants to give me access to their boxes ;

This seems to be a similar issue to https://1password.community/discussion/140536/, just on Linux.

Any help at all would be appreciated!

1Password Version: 8.10.7
Extension Version: 2.10
OS Version: Archlinux w/KDE
Browser:_ Firefox

Comments

  • jstnchristian
    jstnchristian
    Community Member

    I just tried seeing if the socket was open via lsof ~/.1password/agent.sock, and it doesn't look like anything is opening the socket.

  • jstnchristian
    jstnchristian
    Community Member

    Hey folks, any ideas on where/what to look for?

  • floris_1P
    floris_1P

    @jstnchristian Could you try upgrading to the latest 1Password version? There was a related bug we fixed that may solve your issue.

  • jstnchristian
    jstnchristian
    Community Member
    edited June 2023

    @floris_1P confirmed that upgrading to 8.10.8-45 did the trick. Thanks!

    Edit: Is there a way to mark the post as [SOLVED] ?

This discussion has been closed.