Difference between revisions of "Windows Domain SSH"
From Stadm
Jump to navigationJump to search| Line 1: | Line 1: | ||
[[Category:Windows]] | [[Category:Windows]] | ||
| − | + | *Install Cygwin, for openssh you only need the openssh package but a few other tools will probably help(vim,wget,shutdown,rsync) | |
*Create a service domain account that we will used to be able to login through ssh from a domain joined computer | *Create a service domain account that we will used to be able to login through ssh from a domain joined computer | ||
| − | |||
*on the local computer | *on the local computer | ||
| Line 14: | Line 13: | ||
Log on as a service | Log on as a service | ||
Replace a process level token | Replace a process level token | ||
| + | |||
| + | *Setup sshd | ||
| + | ssh-host-config | ||
| + | *We are going to answer yes to most of the default configuration, below shows a summary of what we ill be saying yes and no too as long as with output from a setup | ||
| + | Should privilege separation be used(yes/no)? Yes | ||
Revision as of 14:58, 9 June 2015
- Install Cygwin, for openssh you only need the openssh package but a few other tools will probably help(vim,wget,shutdown,rsync)
- Create a service domain account that we will used to be able to login through ssh from a domain joined computer
- on the local computer
- regedit
Local Security Policy => Security Settings => Local Policies => User Rights Assignment
- add domain user to these groups
Act as part of the operating system Create a token object Deny log on through remote desktop services Log on as a service Replace a process level token
- Setup sshd
ssh-host-config
- We are going to answer yes to most of the default configuration, below shows a summary of what we ill be saying yes and no too as long as with output from a setup
Should privilege separation be used(yes/no)? Yes
