Ssh no such file or directory windows

Damir’s Corner .

Using Git with SSH in Windows 10

Although Git can be used over HTTPS with username and password authentication, it’s much more convenient to use over SSH. Even with Git Credential Manager for Windows being bundled with Git for Windows.

First, generate your SSH key. Although you can transfer key files between computers, I suggest generating a new one on each computer you use.

Then, associate the generated key with your Windows login by adding it to the OpenSSH Authentication Agent service.

In my case, the service was disabled and the command failed with the following error:

Error connecting to agent: No such file or directory

The documentation suggested trying to start the service:

For me, it just failed with a different error:

Start-Service : Service ‘OpenSSH Authentication Agent (ssh-agent)’ cannot be started due to the following error: Cannot start service ssh-agent on computer ‘ .’.

To resolve the issue, I had to change the service startup type from Disabled to Automatic in its properties dialog (and start the service then).

With that, the command-line Git client is ready to be used with SSH.

UI clients will typically require additional configuration which is application dependant. In my favorite UI client Fork, this can be done in the File > Configure SSH Keys dialog.

Of course, the contents of the generated SSH public key file (with .pub extension, e.g. id_rsa.pub ) must be added to your account for the Git service provider. Add the same key to all services, if you use multiple.

The location of the relevant settings differs between the Git services:

• In GitHub, it’s in the SSH and GPG keys section of Personal settings.
• In GitLab, it’s in the SSH Keys section of User Settings.
• In Bitbucket, it’s in the SSH keys section of your Bitbucket settings. URL is different for different users.
• In Azure DevOps, it’s in the SSH public keys section of User settings. URL is different for different users.

Make sure that you use the SSH URL instead of the HTTPS one when cloning new repositories (it’s the one not starting with https ).

Источник

How do I make ssh-add recognize the running ssh-agent service with Microsoft’s OpenSSH?

In the course of trying to accomplish a more complicated task (involving hardware security keys and GPG keys for SSH authentication), I have run into an ornery ssh-add utility on my Windows 10 machine. Quite simply, my ssh-add fails to connect to the agent, while all other ssh functions work fine.

When I run ssh-add -L on Powershell 7.0.3, I get the following output:

However, my ssh-agent service seems to be running just fine:

Furthermore, I have my standard public/private SSH keypair in the default location ( C:Users[me].sshid_rsa , C:Users[me].sshid_rsa.pub ). I’ve used this key extensively on GitHub, and ssh itself still works fine in Powershell:

So, given every other aspect of OpenSSH seems to be working fine, why would ssh-add be misbehaving?

Things I have tried to repair it:

• Removing other SSH utilities from my PATH (e.g. those added by Git installation).
• Disabling/re-enabling the Windows optional feature «SSH Client» (and its «SSH Server» counterpart, which I don’t think I need).
• Installing a more recent version of OpenSSH via Chocolatey (https://chocolatey.org/packages/openssh), and pointing all commands to that installation via PATH modification.
• Backing up and removing my .ssh folder, generating a new key (via ssh-keygen ), and starting from scratch.
• Changing the startup type of the ssh-agent service between automatic, manual, and disabled

None of the aforementioned activities seemed to have any effect whatsoever. All other ssh tools worked fine (assuming the optional feature was enabled, and service was running), but ssh-add did not.

What other recommendations do others have for diagnosing this ornery utility?

Источник

Can no longer use ssh-add: Error connecting to agent #1781

Purpose of the issue

• Bug report (encountered problems/errors)
• Feature request (request for new functionality)
• Question

Description of the issue

Can no longer add ssh keys using ssh-add. Instead I’m thrown the following error:

Error connecting to agent: No such file or directory

I believe this has started happening since the latest Windows update.

My set-up
I’m currently booting an ssh-agent at startup, having un-commented before:

• Windows 10
• Latest preview/alpha
  

Further debugging
I took a look at the environment variables set:

• SSH_AUTH_SOCK: /tmp/ssh-yzpgZ44bVaMU/agent.17940
• SSH_AGENT_PID: 4304

Which correctly creates into:

I tried setting, SSH_AUTH_SOCK to the full windows path above, however at this point I then get:

Could not add identity «.sshid_rsa»: invalid format

Apologies if this is an issue with ConEmu, I’m not knowledgeable enough to be able to separate the two cleanly.

The text was updated successfully, but these errors were encountered:

Same issue here after the latest Windows update :/
(with ConEmu version 161206)

Same issue, with latest version (180506)

try which ssh-agent Windows 1803 comes with their own OpenSSH version by default now, you probably want to remove that from PATH

Thanks @Stanzilla! I removed %SYSTEMROOT%System32OpenSSH from my PATH and it’s working fine now 🙂

Thanks @Stanzilla ! Works for me.

Yep that’s worked for me as well. Cheers @Stanzilla!

@Stanzilla Thanks, that’s worked for me.

Another option (possibly better than using another copy of openssh) is to use the Windows ssh agent. Check status in powershell:

If the service is disabled, start it and set to manual:

If there’s a reason to use a git version of openssh instead of the windows-installed version, that would be good to know.

We need to support older versions of Windows as well

Instead of removing %SYSTEMROOT%System32OpenSSH from your path, merely add the following to your user-profile.cmd file.

It will add gitusrbin to your path again, but this time it comes before the %SYSTEMROOT%System32OpenSSH entry, which allows the ssh-agent calls to work again.

If you are using default ssh client, you can switch git to use it too (answer was found here):
git config —global core.sshCommand «‘C:WindowsSystem32OpenSSHssh.exe’»

@Stanzilla maybe you could use feature detection to set up default ssh for Windows version that support it or let that be the default and downgrade for non-native ssh?

Instead removing %SYSTEMROOT%System32OpenSSH from you path, merely add the following to your user-profile.cmd file.

This seems like a much better solution than removing native OpenSSH from Windows path, which could have lots of consequences

Thanks @Stanzilla! I removed %SYSTEMROOT%System32OpenSSH from my PATH and it’s working fine now 🙂

where did you remove it. how did it got added in the first place?? by cmder?? why do that if it’s wrong?? why do i need to spend 3 hours to get ssh-agent working with this software??

why do i need to google to many different github issues or PR or whatever to get any insight to enable this. as you might notice i’m going quite mental on this, at least it’s a terrible and experience full of anger

Источник

Error connecting to agent: no such file or directory — adding key to ssh agent

I am trying to add key that I have generated to the ssh agent. Below are my steps

After the key is generated, I am starting the ssh agent and adding it

7 Answers 7

VonC is probably right, in that you need to fix your path, but I was facing the same problem despite using the correct one. In my case, I needed to start ssh-agent for the command to work.

Running the sample commands from GitHub was not working, but, since I had installed OpenSSH, I simply started the pre-installed «OpenSSH Authentication Agent» service, on the Services app, as described in this answer.

This problem is maybe because you have two types of ssh-agent.exe , you can see them in task-manager , one ssh-agent will be from git and other one would be from OpenSSH.

Fix

1. End all ssh task from task-manager
2. Go to the directory where the key is in your case C:repokey this should be your working directory and then run start-ssh-agent will automatically add your private key to the ssh and you won’t need the ssh-add command .

Imp

1. start-ssh-agent will use the ssh from git
2. start ssh-agent will use the ssh from OpenSSH

So there can be inconsistencies between the version of ssh you’re using and your keys are added/generated with

Источник

ssh-add returns with: «Error connecting to agent: No such file or directory»

ssh-add alone is not working:

How should I use that tool?

4 Answers 4

You need to initialize the agent first.

You can do this in multiple ways. Either by starting a new shell

or by evaluating the variables returned by ssh-agent in your current shell.

I suggest using the second method, because you keep all your history and variables.

In Windows PowerShell (run as admin):

Check the current status of ssh-agent:

Get-Service | ? <$_.Name -like ‘*ssh-agent*’>| select -Property Name, StartType, Status

Enable the Service if it is disabled:

Set-Service -Name ssh-agent -StartupType Manual

Start the Service:

Add your key as before:

The SSH agent is not running, or the environment variables that it sets are not available in the current environment (most importantly SSH_AUTH_SOCK ), or they are set incorrectly (pointing to a dead agent).

You could start the agent in the current shell session using

or start a new shell session through the agent using

(replace fish with whatever shell you are using). But since you say that you used to be able to use ssh-add without this, it leads me to believe that you’ve accidentally killed the agent (or it has terminated due to some other reason). The error message makes me think that the SSH_AUTH_SOCK environment variable is actually set, but that ssh-add can’t find a valid communication socket at that path.

It would not surprise me if your usual way of doing things would work again if you completely logged out and logged in again, or rebooted the machine.

Источник

Problem: bastion host IP mismatch on ~/.ssh/known_hosts

I had the known_hosts file old as the IP address of the bastion changed…

$ ssh 10.82.49.24
ssh_exchange_identification: Connection closed by remote host

Did not give me any information. Looking at the verbose output leads to the same thing:

$ ssh -v 10.82.49.24
OpenSSH_7.4p1, LibreSSL 2.5.0
debug1: Reading configuration data /Users/mdesales/.ssh/config
debug1: /Users/mdesales/.ssh/config line 1: Applying options for 10.82.*.*
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Executing proxy command: exec ssh -q -W 10.82.49.24:22 ec2-user@bastion-vpc-xxxxxx.config-yyyyyyy.com -i ~/.ssh/xxxconfig-xxxx.pem
debug1: key_load_public: No such file or directory
debug1: identity file ~/.ssh/xxxconfig-xxxx.pem
debug1: key_load_public: No such file or directory
debug1: identity file ~/.ssh/xxxconfig-xxxx.pem-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.4
debug1: permanently_drop_suid: 1647059022
ssh_exchange_identification: Connection closed by remote host

At this point, since it is a proxy to another host through the bastion, I could see the bastion being a problem:

$ ssh ec2-user@bastion-vpc-xxxxxx.config-yyyyyyy.com -i ~/.ssh/xxxconfig-xxxx.pem
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:Z8X1UlIgQ94BKJ7NA/oQi7v0NL4IlFeO7Ou4j76Zphk.
Please contact your system administrator.
Add correct host key in /Users/mdesales/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /Users/mdesales/.ssh/known_hosts:238
ECDSA host key for ec2-user@bastion-vpc-xxxxxx.config-yyyyyyy.com has changed and you have requested strict checking.
Host key verification failed.

Solution

Removing the entry on line 238 solved the problem… I could ssh to the bastion and I could ssh to the hosts.

$ vim /Users/mdesales/.ssh/known_hosts

$ ssh ec2-user@bastion-vpc-xxxxxx.config-yyyyyyy.com -i ~/.ssh/xxxconfig-xxxx.pem
The authenticity of host 'ec2-user@bastion-vpc-xxxxxx.config-yyyyyyy.com (34.x.x.y)' can't be established.
ECDSA key fingerprint is SHA256:Z8X1UlIgQ94BKJ7NA/oQi7v0NL4IlFeO7Ou4j76Zphk.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'ec2-user@bastion-vpc-xxxxxx.config-yyyyyyy.com -i ~/.ssh/xxxconfig-xxxx.pem,34.213.y.x' (ECDSA) to the list of known hosts.
********************************************************************************
This is a private computer system containing information that is proprietary
and confidential to the owner of the system.  Only individuals or entities
authorized by the owner of the system are allowed to access or use the system.
Any unauthorized access or use of the system or information is strictly
prohibited.

All violators will be prosecuted to the fullest extent permitted by law.
********************************************************************************
Last login: Wed Aug  2 20:35:55 2017 from 10.81.31.115
[ec2-user@ip-10-82-50-142 ~]$