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

Changed the flow to make it more clear what applies to key-based auth

Joey Aiello 2015-10-16 15:54:59 -07:00
parent 257aa81738
commit 2f7c521fb0
1 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
Deploy-Win32-OpenSSH.md

@ -8,17 +8,17 @@
* Open Firewall
* start PowerShell
* new-netfirewallrule -Protocol TCP -LocalPort 22 -Direction Inbound -Action Allow -DisplayName SSH
* Install key-auth package if you need key-based authentication
* run setup-ssh-lsa.cmd
* reboot
* Run SSH daemon as System (See below for alternative options)
* Download PSTools from [SysInternals](https://technet.microsoft.com/en-us/sysinternals/bb897553)
* psexec.exe -i -s cmd.exe
* Within cmd.exe - launch sshd.exe
* Running SSH daemon as Admin user
* Note - SSH daemon needs to run as System to support key-based authentication
* Give Admin user SE_ASSIGNPRIMARYTOKEN_NAME (steps below)
* secpol.msc -> Local Policies -> UserRightsAssessment
* Add the Admin user to "Replace a process level token"
* Log off and Log in.
* If you need key-based authentication:
* Install key-auth package
* run setup-ssh-lsa.cmd
* reboot
* Run SSH daemon as System (See below for alternative options)
* Download PSTools from [SysInternals](https://technet.microsoft.com/en-us/sysinternals/bb897553)
* psexec.exe -i -s cmd.exe
* Within cmd.exe - launch sshd.exe
* Running SSH daemon as Admin user (Note - SSH daemon needs to run as System to support key-based authentication)
* Give Admin user SE_ASSIGNPRIMARYTOKEN_NAME
* secpol.msc -> Local Policies -> UserRightsAssessment
* Add the Admin user to "Replace a process level token"
* Log off and Log in.
* In elevated cmd.exe, start sshd.exe