{"id":34663,"date":"2019-10-31T21:59:41","date_gmt":"2019-10-31T18:59:41","guid":{"rendered":"https:\/\/prohoster.info\/blog\/podklyuchenie-k-windows-po-ssh-kak-v-linux\/"},"modified":"2019-10-31T21:59:41","modified_gmt":"2019-10-31T18:59:41","slug":"podklyuchenie-k-windows-po-ssh-kak-v-linux","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/podklyuchenie-k-windows-po-ssh-kak-v-linux","title":{"rendered":"Connecting to Windows via SSH like in Linux","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

I've always found it frustrating to connect to Windows machines. No, I'm not against Microsoft or their products. Every product exists for its purpose, but that's not the issue here.
\nI have always dreadfully struggled to connect to Windows servers because these connections are either configured in the most convoluted way (hello WinRM with HTTPS) or are not very stable (hello RDP to virtual machines across the ocean).<\/p>\n

Therefore, having accidentally stumbled upon the project Win32-OpenSSH<\/a><\/noindex>, I decided to share my setup experience. This tool may save someone a lot of nerves.<\/p>\n

\"Connecting
\n<\/a><\/noindex>
\nInstallation options:<\/p>\n

    \n
  1. Manually<\/a><\/noindex><\/li>\n
  2. Through the package<\/a><\/noindex> Chocolatey<\/li>\n
  3. Via Ansible, for example, the role jborean93.win_openssh<\/a><\/noindex><\/li>\n<\/ol>\n

    \nNext, I will discuss the first point, as the others are relatively straightforward.<\/p>\n

    Note that this project is still in beta, so it is not recommended for production use.<\/p>\n

    So, let\u2019s download the latest release, which is currently 7.9.0.0p1-beta<\/a><\/noindex>. There are versions for both 32-bit and 64-bit systems.<\/p>\n

    Unpack it to C:Program FilesOpenSSH<\/i>
    \nA crucial moment for proper operation: write permissions in this directory must only be for SYSTEM<\/i> and the admin group.<\/p>\n

    Install the services using the script install-sshd.ps1<\/i> located in this directory<\/p>\n

    powershell.exe -ExecutionPolicy Bypass -File install-sshd.ps1<\/code><\/pre>\n
    \nAllow incoming connections on port 22:<\/p>\n
    New-NetFirewallRule -Name sshd -DisplayName 'OpenSSH Server (sshd)' -Enabled True -Direction Inbound -Protocol TCP -Action Allow -LocalPort 22<\/code><\/pre>\n
    \nClarification: the applet New-NetFirewallRule<\/i> is used on Windows Server 2012 and newer. In older systems (or desktop versions), you can use the command:<\/p>\n
    netsh advfirewall firewall add rule name=sshd dir=in action=allow protocol=TCP localport=22\n<\/code><\/pre>\n
    \nStarting the service:<\/p>\n
    net start sshd<\/code><\/pre>\n
    \nUpon startup, host keys will be automatically generated (if they are missing) in %programdata%ssh<\/i><\/p>\n
    To enable service auto-start with system startup, we can use the command:<\/p>\n
    Set-Service sshd -StartupType Automatic<\/code><\/pre>\n
    \nAdditionally, you can change the default shell (after installation, by default it's cmd<\/i>):<\/p>\n
    New-ItemProperty -Path \"HKLM:SOFTWAREOpenSSH\" -Name DefaultShell -Value \"C:WindowsSystem32WindowsPowerShellv1.0powershell.exe\" -PropertyType String -Force<\/code><\/pre>\n
    \nClarification: You must specify the absolute path.<\/p>\n
    What's next?<\/p>\n
    Then we adjust sshd_config<\/i>, located in C:ProgramDatassh<\/i>. For example:<\/p>\n
    PasswordAuthentication no\nPubkeyAuthentication yes<\/code><\/pre>\n
    \nAnd create the directory .ssh<\/i>, and within it, the file authorized_keys<\/i>. Here, we will write the public keys.<\/p>\n
    An important clarification: write permissions to this file must be granted only to the user whose directory contains the file.<\/p>\n
    However, if you have issues with this, you can always disable rights checking in the config:<\/p>\n
    StrictModes no<\/code><\/pre>\n
    \nBy the way, in C:Program FilesOpenSSH<\/i> there are 2 scripts (FixHostFilePermissions.ps1<\/i>, FixUserFilePermissions.ps1<\/i>), which are supposed to but not necessarily fix permissions, including those with authorized_keys<\/i>, but for some reason, they do not fix.<\/p>\n
    Don't forget to restart the service sshd.<\/i> after applying the changes.<\/p>\n
    ru-mbp-666:infrastructure$ ssh Administrator@192.168.1.10 -i ~\/.ssh\/id_rsa\nWindows PowerShell\nCopyright (C) 2016 Microsoft Corporation. All rights reserved.\n\nPS C:UsersAdministrator> Get-Host\n\n\nName             : ConsoleHost\nVersion          : 5.1.14393.2791\nInstanceId       : 653210bd-6f58-445e-80a0-66f66666f6f6\nUI               : System.Management.Automation.Internal.Host.InternalHostUserInterface\nCurrentCulture   : en-US\nCurrentUICulture : en-US\nPrivateData      : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy\nDebuggerEnabled  : True\nIsRunspacePushed : False\nRunspace         : System.Management.Automation.Runspaces.LocalRunspace\n\nPS C:UsersAdministrator><\/code><\/pre>\n
    \nSubjective pros\/cons.<\/p>\n
    Pros:<\/p>\n