tyler.durden/Win32-OpenSSH
1
0
Fork 0
mirror of https://github.com/PowerShell/Win32-OpenSSH.git synced 2025-07-25 23:14:54 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated Install Win32 OpenSSH (markdown)

Manoj Ampalam 2018-01-19 19:35:28 -08:00
parent c284bc9a01
commit f915894784
1 changed files with 8 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Install-Win32-OpenSSH.md

@ -5,13 +5,7 @@
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. In an elevated Powershell console, run the following
* `powershell.exe -ExecutionPolicy Bypass -File uninstall-sshd.ps1`
1. Navigate to the OpenSSH directory
* `cd 'C:\Program Files\OpenSSH'`
1. Only when you migrate from releases before 1.0.0.0:
* 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.
* `powershell.exe -ExecutionPolicy Bypass -File uninstall-sshd.ps1`
1. Open the firewall for sshd.exe to allow inbound SSH connections
* `New-NetFirewallRule -Name sshd -DisplayName 'OpenSSH Server (sshd)' -Service sshd -Enabled True -Direction Inbound -Protocol TCP -Action Allow`
@ -20,11 +14,16 @@ To get links to latest downloads [this wiki page](https://github.com/PowerShell/
```
netsh advfirewall firewall add rule name=sshd dir=in action=allow protocol=TCP service=sshd
```
1. Start `sshd`
* `net start sshd`
1. Only when you migrate from releases before 1.0.0.0:
* 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.
1. Setup `sshd` and `ssh-agent` to auto-start (optional)
* `Set-Service sshd -StartupType Automatic`
* `Set-Service ssh-agent -StartupType Automatic`
1. Start `sshd`
* `net start sshd`
1. Configuring the default ssh shell (optional)
On the server side, configure the default ssh shell in the windows registry.