From dd7efaa652b984da49d9c9cebe22943020e9a98f Mon Sep 17 00:00:00 2001 From: Manoj Ampalam Date: Thu, 30 Mar 2017 09:55:21 -0700 Subject: [PATCH] Updated Install Win32 OpenSSH (markdown) --- Install-Win32-OpenSSH.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Install-Win32-OpenSSH.md b/Install-Win32-OpenSSH.md index c13903c..0174664 100644 --- a/Install-Win32-OpenSSH.md +++ b/Install-Win32-OpenSSH.md @@ -4,6 +4,9 @@ * Extract contents to `C:\Program Files\OpenSSH` * Start Powershell as Administrator * `cd 'C:\Program Files\OpenSSH'` +* On Windows 10, in developer mode, a different implementation of SSH exists in-box. Look for TCP port bindings on port 22 + * `netstat -anop TCP` + * If you do see 22 occupied, [#610](https://github.com/PowerShell/Win32-OpenSSH/issues/610) has workarounds to deal with port conflict. * Install sshd and ssh-agent services. * `powershell -executionpolicy bypass -file install-sshd.ps1` * Setup SSH host keys (this will generate all the 'host' keys that sshd expects when its starts)