From b95f38e95d95ce65eaa78ad9e54a5f4ee03277c0 Mon Sep 17 00:00:00 2001 From: Yanbing Date: Sat, 20 Jan 2018 20:11:22 -0800 Subject: [PATCH] Updated Install Win32 OpenSSH (markdown) --- Install-Win32-OpenSSH.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Install-Win32-OpenSSH.md b/Install-Win32-OpenSSH.md index dda433f..189278b 100644 --- a/Install-Win32-OpenSSH.md +++ b/Install-Win32-OpenSSH.md @@ -3,7 +3,7 @@ 1. Note [these considerations](https://github.com/PowerShell/Win32-OpenSSH/wiki/Various-Considerations) and [project scope](https://github.com/PowerShell/Win32-OpenSSH/wiki/Project-Scope) first. 1. Download the [latest](https://github.com/PowerShell/Win32-OpenSSH/releases/latest/) build of OpenSSH. To get links to latest downloads [this wiki page](https://github.com/PowerShell/Win32-OpenSSH/wiki/How-to-retrieve-links-to-latest-packages). -1. Extract contents of the latest build to `C:\Program Files\OpenSSH` +1. Extract contents of the latest build to `C:\Program Files\OpenSSH` (Make sure binary location has the write permissions to just SYSTEM, Administrator groups.) 1. In an elevated Powershell console, run the following * `powershell.exe -ExecutionPolicy Bypass -File install-sshd.ps1` 1. Open the firewall for sshd.exe to allow inbound SSH connections @@ -19,7 +19,7 @@ To get links to latest downloads [this wiki page](https://github.com/PowerShell/ 1. Migrate sshd configuration from 0.0.X.X versions (optional): * To use existing customized sshd_config, you need to copy it from binary location to %programdata%\ssh\sshd_config (Note that %programdata% is a hidden directory). * To use existing host keys, you need to copy them from binary location to %programdata%\ssh\ - * Prior versions required SSHD resources (sshd_config, host keys and authorized_keys) to have READ access to "NT Service\SSHD". This is no longer a requirement and the corresponding ACL entry should be removed. You may run Powershell.exe -ExecutionPolicy Bypass -Command '. .\FixHostFilePermissions.ps1 -Confirm:$false' (Note the first "." is a call operator.) to fix up these permissions. + * Prior versions required SSHD resources (sshd_config, host keys and authorized_keys) to have READ access to "NT Service\SSHD". This is no longer a requirement and the corresponding ACL entry should be removed. You may run `Powershell.exe -ExecutionPolicy Bypass -Command '. .\FixHostFilePermissions.ps1 -Confirm:$false'` (Note the first "." is a call operator.) to fix up these permissions. 1. Setup `sshd` and `ssh-agent` to auto-start (optional) * `Set-Service sshd -StartupType Automatic` * `Set-Service ssh-agent -StartupType Automatic`