GitHub SSH issues on Debian

pgooch
pgooch
Community Member
in SSH

I had all this working previously but I re-installed the OS and now I can't get it working again.

I followed the guide here: https://developer.1password.com/docs/ssh/get-started/

The first time I followed the guide I skipped a few steps because I already had an SSH key in my 1password from the last time it was working and I had confirmed it was still in GitHub so I didn't think it would be required. When I was having issues with it I decided to create a new key and try again step by step from the beginning but it still is giving me permission errors - never even asking 1password to prompt me for my password.

phillip@Debian-Penguin:~/Sites/phillip-gooch$ git push
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I've tried searching about this a bit and haven't found anything that has fixed it. I did find something that seems like it might have some relation though - it appears that 1password might need sudo permissions for some reason (I don't remember that being a thing last time).

phillip@Debian-Penguin:~/Sites/phillip-gooch$ ssh -Tvvv git@github.com
OpenSSH_9.6p1 Debian-4, OpenSSL 3.1.5 30 Jan 2024
debug1: Reading configuration data /home/phillip/.ssh/config
debug1: /home/phillip/.ssh/config line 1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
... Shorted due to character limit ...
debug3: ssh_get_authentication_socket_path: path '/home/phillip/.1password/agent.sock'
debug1: get_agent_identities: ssh_get_authentication_socket: Permission denied
debug1: Will attempt key: /home/phillip/.ssh/id_rsa 
debug1: Will attempt key: /home/phillip/.ssh/id_ecdsa 
debug1: Will attempt key: /home/phillip/.ssh/id_ecdsa_sk 
debug1: Will attempt key: /home/phillip/.ssh/id_ed25519 
debug1: Will attempt key: /home/phillip/.ssh/id_ed25519_sk 
debug1: Will attempt key: /home/phillip/.ssh/id_xmss 
debug1: Will attempt key: /home/phillip/.ssh/id_dsa 
debug2: pubkey_prepare: done
debug1: Trying private key: /home/phillip/.ssh/id_rsa
debug3: no such identity: /home/phillip/.ssh/id_rsa: No such file or directory
debug1: Trying private key: /home/phillip/.ssh/id_ecdsa
debug3: no such identity: /home/phillip/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /home/phillip/.ssh/id_ecdsa_sk
debug3: no such identity: /home/phillip/.ssh/id_ecdsa_sk: No such file or directory
debug1: Trying private key: /home/phillip/.ssh/id_ed25519
debug3: no such identity: /home/phillip/.ssh/id_ed25519: No such file or directory
debug1: Trying private key: /home/phillip/.ssh/id_ed25519_sk
debug3: no such identity: /home/phillip/.ssh/id_ed25519_sk: No such file or directory
debug1: Trying private key: /home/phillip/.ssh/id_xmss
debug3: no such identity: /home/phillip/.ssh/id_xmss: No such file or directory
debug1: Trying private key: /home/phillip/.ssh/id_dsa
debug3: no such identity: /home/phillip/.ssh/id_dsa: No such file or directory
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
git@github.com: Permission denied (publickey).

Any insight would be appreciated, I would rather get this working that go back to manually setting things up (not that that's a big deal but the idea of being able to swap machines and still quickly and easily use the same SHH keys is might attractive as I swap distros on a whim).

1Password Version: 8.10.28
Extension Version: Not Provided
OS Version: Debian Trixie
Browser: Not Provided

Comments

  • david.m_1P
    david.m_1P

    Hi @pgooch,

    Thanks for reaching out, and my apologies for not being in touch sooner.

    If you're still experiencing this issue, in order to assist you further, can you send us an email addressed to support+forum@1password.com and include the following in the email:

    • A link to this thread, along with your username.
    • Your ~/.ssh/config file as an attachment. If there are any sensitive IPs or domains therein, please be sure to mask them before sending it in.
    • Confirmation as to whether or not the SSH Key is saved in a custom vault.

    After sending the email, you’ll receive a reply from BitBot, our friendly robot assistant with a Support ID that looks something like [#ABC-12345-678]. Post that here, and I’ll be able to locate your message.

    I look forward to hearing from you!

    -David