{"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\/sk\/blog\/administrirovanie\/podklyuchenie-k-windows-po-ssh-kak-v-linux","title":{"rendered":"Pripojenie k Windows cez SSH ako v Linuxe","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

V\u017edy ma tr\u00e1pi pripojenie k strojom s Windows. Nie, nie som odporcom ani z\u00e1stancom Microsoftu a ich produktov. Ka\u017ed\u00fd produkt existuje kv\u00f4li svojej funkcii, ale o tom to nie je.
\nPre m\u0148a bolo v\u017edy bolestiv\u00e9 pripoji\u0165 sa k serverom s Windows, preto\u017ee tieto pripojenia s\u00fa bu\u010f nastaven\u00e9 cez zlo\u017eitosti (ahoj WinRM s HTTPS), alebo nefunguj\u00fa ve\u013emi stabilne (zdrav\u00edm RDP k virtu\u00e1lkam za oce\u00e1nom).<\/p>\n

N\u00e1hodne som narazil na projekt Win32-OpenSSH<\/a><\/noindex>, a rozhodol som sa podeli\u0165 o sk\u00fasenosti s jeho nastaven\u00edm. Mo\u017eno niekomu t\u00e1to n\u00e1stroj u\u0161etr\u00ed ve\u013ea nervov.<\/p>\n

\"Pripojenie
\n<\/a><\/noindex>
\nMo\u017enosti in\u0161tal\u00e1cie:<\/p>\n

    \n
  1. Ru\u010dne<\/a><\/noindex><\/li>\n
  2. Cez bal\u00edk<\/a><\/noindex> Chocolatey<\/li>\n
  3. Cez Ansible, napr\u00edklad rola jborean93.win_openssh<\/a><\/noindex><\/li>\n<\/ol>\n

    \n\u010ealej budem hovori\u0165 o prvom bode, preto\u017ee ostatn\u00e9 s\u00fa celkom jasn\u00e9.<\/p>\n

    Chcem zd\u00f4razni\u0165, \u017ee tento projekt je zatia\u013e v beta f\u00e1ze, a preto sa neodpor\u00fa\u010da pou\u017e\u00edva\u0165 ho v produkcii.<\/p>\n

    Tak\u017ee, stiahneme si posledn\u00fa verziu, v s\u00fa\u010dasnosti je to 7.9.0.0p1-beta<\/a><\/noindex>. Existuj\u00fa verzie pre 32 aj 64-bitov\u00e9 syst\u00e9my.<\/p>\n

    Rozbal\u00edme do C:Program FilesOpenSSH<\/i>
    \nPovinn\u00fd bod pre spr\u00e1vnu funkciu: pr\u00e1va na z\u00e1pis v tejto prie\u010dinku musia ma\u0165 len SYSTEM<\/i> a administrat\u00edvna skupina.<\/p>\n

    Nain\u0161talujeme slu\u017eby skriptom install-sshd.ps1<\/i> nach\u00e1dzaj\u00facim sa v tejto prie\u010dinku<\/p>\n

    powershell.exe -ExecutionPolicy Bypass -File install-sshd.ps1<\/code><\/pre>\n
    \nPovol\u00edme prich\u00e1dzaj\u00face pripojenia na porte 22:<\/p>\n
    New-NetFirewallRule -Name sshd -DisplayName 'OpenSSH Server (sshd)' -Enabled True -Direction Inbound -Protocol TCP -Action Allow -LocalPort 22<\/code><\/pre>\n
    \nU\u017eito\u010dn\u00e1 pozn\u00e1mka: pr\u00edkaz New-NetFirewallRule<\/i> sa pou\u017e\u00edva na Windows Server 2012 a nov\u0161ie. V star\u0161\u00edch syst\u00e9moch (alebo desktopoch) m\u00f4\u017eete pou\u017ei\u0165 pr\u00edkaz:<\/p>\n
    netsh advfirewall firewall add rule name=sshd dir=in action=allow protocol=TCP localport=22\n<\/code><\/pre>\n
    \nSpust\u00edme slu\u017ebu:<\/p>\n
    net start sshd<\/code><\/pre>\n
    \nPri spusten\u00ed sa automaticky vygeneruj\u00fa hostite\u013esk\u00e9 k\u013e\u00fa\u010de (ak ch\u00fdbaj\u00fa) v %programdata%ssh<\/i><\/p>\n
    Automatick\u00e9 spustenie slu\u017eby pri spusten\u00ed syst\u00e9mu m\u00f4\u017eeme zapn\u00fa\u0165 pr\u00edkazom:<\/p>\n
    Set-Service sshd -StartupType Automatic<\/code><\/pre>\n
    \nTaktie\u017e m\u00f4\u017eeme zmeni\u0165 predvolen\u00fa pr\u00edkazov\u00fa shell (po in\u0161tal\u00e1cii, predvolene \u2014 cmd<\/i>):<\/p>\n
    New-ItemProperty -Path \"HKLM:SOFTWAREOpenSSH\" -Name DefaultShell -Value \"C:WindowsSystem32WindowsPowerShellv1.0powershell.exe\" -PropertyType String -Force<\/code><\/pre>\n
    \nU\u017eito\u010dn\u00e1 pozn\u00e1mka: Je potrebn\u00e9 uvies\u0165 absol\u00fatnu cestu.<\/p>\n
    \u010co \u010falej?<\/p>\n
    A \u010falej nastavujeme sshd_config<\/i>, ktor\u00fd sa nach\u00e1dza v C:ProgramDatassh<\/i>. Napr\u00edklad:<\/p>\n
    PasswordAuthentication no\nPubkeyAuthentication yes<\/code><\/pre>\n
    \nA vytvor\u00edme v pou\u017e\u00edvate\u013eskej prie\u010dinku adres\u00e1r .ssh<\/i>, a v \u0148om s\u00fabor authorized_keys<\/i>. Tam zap\u00ed\u0161eme verejn\u00e9 k\u013e\u00fa\u010de.<\/p>\n
    D\u00f4le\u017eit\u00e9 upozornenie: pr\u00e1va na z\u00e1pis do tohto s\u00faboru by mal ma\u0165 iba pou\u017e\u00edvate\u013e, ktor\u00e9ho adres\u00e1r s\u00fabor obsahuje.<\/p>\n
    Ale ak m\u00e1te s t\u00fdmto probl\u00e9my, v\u017edy je mo\u017en\u00e9 vypn\u00fa\u0165 overovanie pr\u00e1v v konfigur\u00e1cii:<\/p>\n
    StrictModes no<\/code><\/pre>\n
    \nMimochodom, v C:Program FilesOpenSSH<\/i> le\u017eia 2 skripty (FixHostFilePermissions.ps1<\/i>, FixUserFilePermissions.ps1<\/i>), ktor\u00e9 by mali, ale nemusia opravova\u0165 pr\u00e1va, vr\u00e1tane authorized_keys<\/i>, ale akosi to neopravuj\u00fa.<\/p>\n
    Nezab\u00fadajte re\u0161tartova\u0165 slu\u017ebu sshd<\/i> po zmene na aplikovanie zmien.<\/p>\n
    ru-mbp-666:infrastructure$ ssh Administrator@192.168.1.10 -i ~\/ .ssh\/id_rsa\nWindows PowerShell\nCopyright (C) 2016 Microsoft Corporation. V\u0161etky pr\u00e1va vyhraden\u00e9.\n\nPS C:UsersAdministrator> Get-Host\n\n\nN\u00e1zov             : ConsoleHost\nVerzia           : 5.1.14393.2791\nInstanceId       : 653210bd-6f58-445e-80a0-66f66666f6f6\nUI               : System.Management.Automation.Internal.Host.InternalHostUserInterface\nAktu\u00e1lna kult\u00fara : en-US\nAktu\u00e1lna UI kult\u00fara : en-US\nS\u00fakromn\u00e9 \u00fadaje   : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy\nDebuggerEnabled   : True\nIsRunspacePushed : False\nRunspace         : System.Management.Automation.Runspaces.LocalRunspace\n\nPS C:UsersAdministrator><\/code><\/pre>\n
    \nSubjekt\u00edvne v\u00fdhody\/nev\u00fdhody.<\/p>\n
    V\u00fdhody:<\/p>\n