<p><strong>Original answer using git’s start-ssh-agent</strong></p>
<p>Assurez-vous you have Git installed and have git’s <code>cmd</code> folder in your PATH. Par exemple, on my computer the path to git’s cmd folder is <code>C:\Program Files\Git\cmd</code></p>
<p>Assurez-vous your <code>id_rsa</code> file is in the folder <code>c:\users\yourusername.ssh</code></p>
<p>Restart your invite de commandes if you haven’t already, puis run <code>start-ssh-agent</code>. It will find your <code>id_rsa</code> and prompt you for the passphrase</p>
<p><strong>Update 2019 - A better solution if you’re using Windows 10:</strong> OpenSSH is available as part of Windows 10 which makes using SSH from cmd/powershell much easier in my opinion. It also doesn’t rely on having git installed, unlike my previous solution.</p>
<ul>
<li></li>
</ul>
<p>Open <code>Manage optional features</code> from the start menu and assurez-vous you have <code>Open SSH Client</code> in the list. If not, vous devriez be able to add it.</p>
<ul>
<li></li>
</ul>
<p>Open <code>Services</code> from the start Menu</p>
<ul>
<li></li>
</ul>
<p>Scroll down to <code>OpenSSH Authentication Agent</code> > right click > properties</p>
<ul>
<li></li>
</ul>
<p>Change the Startup type from Disabled to any of the other 3 options. I have mine set to <code>Automatic (Delayed Start)</code></p>
<ul>
<li></li>
</ul>
<p>Open cmd and type <code>where ssh</code> to confirm that the top listed path is in System32. Mine is installed at <code>C:\Windows\System32\OpenSSH\ssh.exe</code>. If it’s not in the list you may need to close and reopen cmd.</p>
<p>Once you’ve followed these steps, ssh-agent, ssh-add and all other ssh commands should now work from cmd. To start the agent vous pouvez simply type <code>ssh-agent</code>.</p>
<ul>
<li><strong>Optional step/troubleshooting</strong>: If you use git, vous devriez set the <code>GIT_SSH</code> variable d’environnement to the output of <code>where ssh</code> which you ran before (e.g <code>C:\Windows\System32\OpenSSH\ssh.exe</code>). This is to stop inconsistencies between the version of ssh you’re using (and your keys are added/generated with) and the version that git uses internally. <a href="https://stackoverflow.com/questions/2499331/git-with-ssh-on-windows/8713121#8713121">This should prevent issues that are similar to this</a></li>
</ul>
<p>Some nice things about this solution:</p>
<ul>
<li>You won’t need to start the</li>
</ul>
<p><em>(Réponse tronquée)</em></p>
