Changes between Version 3 and Version 4 of Ticket #13049


Ignore:
Timestamp:
Jan 29, 2024, 1:01:07 PM (7 months ago)
Author:
kataba
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #13049 – Description

    v3 v4  
    2929Edit 2:
    3030
    31 I use ohmyzsh with a couple common plugins. I found out I had the ssh-agent plugin enabled. After disabling it, it stopped asking me for passphrase, but also ssh-agent doesn't get started when I open my terminal. When I add my keys it doesn't ask me for a passphrase, which by itself is what I would expect, based on my config. I am still not sure what caused the bad passhphrase error though.
     31Here is my `~/.ssh/config` file content:
    3232
    33 With the ssh-plugin plugin disabled, when I boot/restart my system, an ssh-agent doesn't get started on boot (I think it's like that by default; the ssh-agent plugin didn't change this, it was only responsible for automatically starting an ssh-agent when I open my terminal). Then I open my terminal. Then when I run the `ssh` command to ssh into a server, automatically an ssh-agent gets started and my private key gets imported without asking for a passphrase. I hope this is how it should work based on my config.
     33    Host *
     34      AddKeysToAgent yes
     35      UseKeychain yes
     36      IdentityFile ~/.ssh/id_ed25519
     37   
     38    Host website.com
     39      HostName xx.xxx.xx.xxx
     40      Port 1500
     41      User user
     42
     43I use ohmyzsh with a couple common plugins. I found out I had the ssh-agent plugin enabled.
     44
     45With the ssh-plugin plugin disabled, when I boot/restart my system, an ssh-agent doesn't get started on boot (I think it's like that by default; the ssh-agent plugin didn't change this, it was only responsible for automatically starting an ssh-agent when I open my terminal). Then I open my terminal. Then when I run the `ssh` command to ssh into a server, automatically an ssh-agent gets started and my private key gets imported without asking for a passphrase.
    3446
    3547By default, there is an environment variable `$SSH_AUTH_SOCK` set to a temp folder location and `$SSH_AGENT_PID` is empty. The ssh-plugin was starting a new ssh-agent instance and overwriting the `$SSH_AUTH_SOCK` variable to its own socket, and this way shadowing the existing ssh-agent instance that used the default socket location (if there is one running), and this led to two different ssh-agent instances running at the same time and listening on different sockets.