From 6c6dfb3fbf8a5aa9913a2d4cd9f5b9d4392117c8 Mon Sep 17 00:00:00 2001 From: Yanbing Date: Thu, 18 Jan 2018 12:18:27 -0800 Subject: [PATCH] Updated Install Win32 OpenSSH (markdown) --- Install-Win32-OpenSSH.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Install-Win32-OpenSSH.md b/Install-Win32-OpenSSH.md index 960a28a..9cbe0cd 100644 --- a/Install-Win32-OpenSSH.md +++ b/Install-Win32-OpenSSH.md @@ -13,9 +13,9 @@ To figure out if this is the case, look for TCP port bindings on port 22 and the * If you do see 22 occupied, [#610](https://github.com/PowerShell/Win32-OpenSSH/issues/610) has workarounds to deal with port conflict. 1. Install `sshd` and `ssh-agent` services. * `powershell -ExecutionPolicy Bypass -File install-sshd.ps1` -1. Generate SSH host keys (in powershell window) - * `.\ssh-keygen.exe -A` - * `Powershell.exe -ExecutionPolicy Bypass -Command '. .\FixHostFilePermissions.ps1 -Confirm:$false'` (Note the first "." is a call operator.) +1. Generate SSH host keys (Optional after build 1.0.0.0 in powershell window) + * `.\ssh-keygen.exe -A` + * Fix ACLs if the keys/config files are generated/deployed on build before 1.0.0.0: `Powershell.exe -ExecutionPolicy Bypass -Command '. .\FixHostFilePermissions.ps1 -Confirm:$false'` (Note the first "." is a call operator.) 1. Secure SSH host keys (optional) * `Start-Service ssh-agent` * Download psexec from [here](https://technet.microsoft.com/en-us/sysinternals/pstools)