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

Updated Install Win32 OpenSSH (markdown)

Yanbing 2018-01-03 10:55:59 -08:00
parent 28f7fa7622
commit d4d2e1f7e2
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Install-Win32-OpenSSH.md

@ -28,10 +28,10 @@ To figure out if this is the case, look for TCP port bindings on port 22 and the
* `ssh-add ssh_host_ed25519_key` * `ssh-add ssh_host_ed25519_key`
* Host private keys are now securely stored by ssh-agent, private key files can be deleted at this point. * Host private keys are now securely stored by ssh-agent, private key files can be deleted at this point.
[`sdelete`](https://docs.microsoft.com/en-us/sysinternals/downloads/sdelete) may be used to securely erase them. [`sdelete`](https://docs.microsoft.com/en-us/sysinternals/downloads/sdelete) may be used to securely erase them.
1. Open the firewall on TCP port 22 to allow inbound SSH connections 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` * `New-NetFirewallRule -Name sshd -DisplayName 'OpenSSH Server (sshd)' -Service sshd -Enabled True -Direction Inbound -Protocol TCP -Action Allow`
Note: `New-NetFirewallRule` is for servers only. If you're on a client desktop machine (like Windows 10) try: Note: `New-NetFirewallRule` is for Windows 2012 and above servers only. If you're on a client desktop machine (like Windows 10) or Windows 2008 R2 and below, try:
``` ```
netsh advfirewall firewall add rule name=sshd dir=in action=allow protocol=TCP service=sshd netsh advfirewall firewall add rule name=sshd dir=in action=allow protocol=TCP service=sshd