{"id":80500,"date":"2020-05-06T13:42:29","date_gmt":"2020-05-06T11:42:29","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/protokoly-sftp-i-ftps"},"modified":"2020-05-06T13:42:29","modified_gmt":"2020-05-06T11:42:29","slug":"protokoly-sftp-i-ftps","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/protokoly-sftp-i-ftps","title":{"rendered":"Protokoly SFTP a FTPS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<h1>\u00davod<\/h1>\n<p><\/p>\n<p>Presne pred t\u00fd\u017ed\u0148om som p\u00edsal refer\u00e1t na t\u00e9mu uveden\u00fa v nadpise a zistil som, \u017ee informat\u00edvnych inform\u00e1ci\u00ed na internete nie je tak ve\u013ea. V\u00e4\u010d\u0161inou s\u00fa to len such\u00e9 fakty a n\u00e1vody na nastavenie. Preto som sa rozhodol text trochu upravi\u0165 a zverejni\u0165 ho ako \u010dl\u00e1nok.<\/p>\n<p>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h1>\u010co je to FTP<\/h1>\n<p><\/p>\n<p>FTP (File Transfer Protocol) \u2013 protokol na prenos s\u00faborov cez sie\u0165. Je jedn\u00fdm zo z\u00e1kladn\u00fdch protokolov Ethernetu. Objavil sa v roku 1971 a p\u00f4vodne fungoval v sie\u0165ach DARPA. V s\u00fa\u010dasnosti, rovnako ako HTTP, je prenos s\u00faborov zalo\u017een\u00fd na modeli pozost\u00e1vaj\u00facom z mno\u017einy protokolov TCP\/IP (Transmission Control Protocol\/Internet Protocol). Definovan\u00fd v RFC 959.<\/p>\n<p><\/p>\n<p>Protokol ur\u010duje nasleduj\u00face:<\/p>\n<\/p>\n<ul>\n<li>Ako sa bude vykon\u00e1va\u0165 kontrola ch\u00fdb<\/li>\n<li>Met\u00f3da balenia \u00fadajov (ak sa balenie pou\u017e\u00edva)<\/li>\n<li>Ak\u00fdm sp\u00f4sobom odosielaj\u00face zariadenie oznamuje, \u017ee dokon\u010dilo spr\u00e1vu<\/li>\n<li>Ak\u00fdm sp\u00f4sobom prij\u00edmaj\u00face zariadenie oznamuje, \u017ee prijalo spr\u00e1vu<\/li>\n<\/ul>\n<p><\/p>\n<h2>Interakcia medzi klientom a serverom<\/h2>\n<p><\/p>\n<p>Pozrime sa podrobnej\u0161ie na procesy prebiehaj\u00face pri pr\u00e1ci FTP. Spojenie inicializuje interpret protokolu pou\u017e\u00edvate\u013ea. Riadenie v\u00fdmeny sa uskuto\u010d\u0148uje prostredn\u00edctvom riadiaceho kan\u00e1la v \u0161tandarde TELNET. Pr\u00edkazy FTP generuje interpret protokolu pou\u017e\u00edvate\u013ea a odosiela ich na server. Odpovede servera s\u00fa pou\u017e\u00edvate\u013eovi zasielan\u00e9 taktie\u017e cez riadiaci kan\u00e1l. V z\u00e1sade m\u00e1 pou\u017e\u00edvate\u013e mo\u017enos\u0165 nadviaza\u0165 kontakt s interpretem protokolu servera a prostriedkami odli\u0161n\u00fdmi od interpreta pou\u017e\u00edvate\u013ea.<\/p>\n<p><\/p>\n<p>Hlavnou \u010drtou FTP je to, \u017ee pou\u017e\u00edva dvojit\u00e9 pripojenie. Jedno z nich sa pou\u017e\u00edva na prenos pr\u00edkazov serveru a prebieha predvolene cez TCP port 21, ktor\u00fd m\u00f4\u017ee by\u0165 zmenen\u00fd. Riadiace spojenie existuje po cel\u00fa dobu, po\u010das ktorej klient komunikuje so serverom. Riadiaci kan\u00e1l mus\u00ed by\u0165 otvoren\u00fd pri prenose \u00fadajov medzi strojmi. V pr\u00edpade jeho uzavretia sa prenos \u00fadajov zastav\u00ed. Druh\u00e9 sa pou\u017e\u00edva na priamy prenos \u00fadajov. Otv\u00e1ra sa zaka\u017ed\u00fdm, ke\u010f sa uskuto\u010d\u0148uje prenos s\u00faboru medzi klientom a serverom. V pr\u00edpade, \u017ee sa s\u00fa\u010dasne pren\u00e1\u0161a viacero s\u00faborov, pre ka\u017ed\u00fd z nich sa otv\u00e1ra svoj kan\u00e1l prenosu.<\/p>\n<p><\/p>\n<p>FTP m\u00f4\u017ee fungova\u0165 v akt\u00edvnom alebo pas\u00edvnom re\u017eime, pri\u010dom v\u00fdber re\u017eimu ovplyv\u0148uje sp\u00f4sob nadviazania pripojenia. V akt\u00edvnom re\u017eime klient vytvor\u00ed riadiace TCP pripojenie so serverom a odo\u0161le mu svoju IP adresu a n\u00e1hodn\u00e9 \u010d\u00edslo klientsk\u00e9ho portu, po \u010dom \u010dak\u00e1, k\u00fdm server spust\u00ed TCP pripojenie na t\u00fato adresu a \u010d\u00edslo portu. Ak je klient za firewallom a nem\u00f4\u017ee prija\u0165 prich\u00e1dzaj\u00face TCP pripojenie, m\u00f4\u017ee by\u0165 pou\u017eit\u00fd pas\u00edvny re\u017eim. V tomto re\u017eime klient vyu\u017e\u00edva riadiaci pr\u00fad, aby poslal serveru pr\u00edkaz PASV, a n\u00e1sledne dost\u00e1va od servera jeho IP adresu a \u010d\u00edslo portu, ktor\u00e9 klient pou\u017eije na otvorenie d\u00e1tov\u00e9ho pr\u00fadu zo svojho n\u00e1hodn\u00e9ho portu. <\/p>\n<p><\/p>\n<p>M\u00f4\u017ee nasta\u0165 situ\u00e1cia, ke\u010f sa d\u00e1ta m\u00f4\u017eu pren\u00e1\u0161a\u0165 na tret\u00ed stroj. V tomto pr\u00edpade pou\u017e\u00edvate\u013e organizuje riadiaci kan\u00e1l medzi dvoma servermi a zria\u010fuje priamy kan\u00e1l pre d\u00e1ta medzi nimi. Riadiace pr\u00edkazy id\u00fa cez pou\u017e\u00edvate\u013ea, zatia\u013e \u010do d\u00e1ta sa pren\u00e1\u0161aj\u00fa priamo medzi servermi.<\/p>\n<p><\/p>\n<p>Pri prenose d\u00e1t po sieti sa m\u00f4\u017eu pou\u017ei\u0165 \u0161tyri reprezent\u00e1cie d\u00e1t:<\/p>\n<p><\/p>\n<ul>\n<li>ASCII \u2013 pou\u017e\u00edva sa pre text. D\u00e1ta sa, ak je to potrebn\u00e9, pred prenosom konvertuj\u00fa zo znakovej reprezent\u00e1cie na odosielaj\u00facom hoste na 'osembitov\u00fd ASCII' a (op\u00e4\u0165, ak je to potrebn\u00e9) na znakov\u00fd form\u00e1t prij\u00edmaj\u00faceho hostite\u013ea. Najm\u00e4 sa menia znaky konca riadku. V d\u00f4sledku toho tento re\u017eim nie je vhodn\u00fd pre s\u00fabory, ktor\u00e9 obsahuj\u00fa nielen be\u017en\u00fd text.<\/li>\n<li>Bin\u00e1rny re\u017eim \u2013 odosielaj\u00face zariadenie posiela ka\u017ed\u00fd s\u00fabor po bajtoch a pr\u00edjemca uchov\u00e1va pr\u00fad bajtov pri prij\u00edman\u00ed. Podpora tohto re\u017eimu bola odpor\u00fa\u010dan\u00e1 pre v\u0161etky realiz\u00e1cie FTP.<\/li>\n<li>EBCDIC \u2013 pou\u017e\u00edva sa na prenos be\u017en\u00e9ho textu medzi hostite\u013emi v k\u00f3dovan\u00ed EBCDIC. Zvy\u0161ok je tento re\u017eim podobn\u00fd ASCII re\u017eimu.<\/li>\n<li>Lok\u00e1lny re\u017eim \u2013 umo\u017e\u0148uje dvom po\u010d\u00edta\u010dom s identick\u00fdmi nastaveniami posiela\u0165 d\u00e1ta vo vlastnom form\u00e1te bez konverzie na ASCII.<\/li>\n<\/ul>\n<p><\/p>\n<p>Prenos d\u00e1t m\u00f4\u017ee prebieha\u0165 v ktoromko\u013evek z troch re\u017eimov:<\/p>\n<p><\/p>\n<ul>\n<li>Pr\u00fadov\u00fd re\u017eim \u2013 d\u00e1ta sa posielaj\u00fa ako kontinu\u00e1lny pr\u00fad, \u010do uvo\u013e\u0148uje FTP od ak\u00e9hoko\u013evek spracovania. Namiesto toho sa cel\u00e9 spracovanie vykon\u00e1va v TCP. Indik\u00e1tor konca s\u00faboru nie je potrebn\u00fd, okrem oddelenia d\u00e1t na z\u00e1znamy.<\/li>\n<li>Blokov\u00fd re\u017eim \u2013 FTP rozde\u013euje d\u00e1ta na nieko\u013eko blokov (blok hlavi\u010dky, po\u010det bajtov, pole d\u00e1t) a n\u00e1sledne ich odosiela cez TCP.<\/li>\n<li>Re\u017eim kompresie \u2013 d\u00e1ta sa komprimuj\u00fa jednotn\u00fdm algoritmom (zvy\u010dajne k\u00f3dovan\u00edm dlh\u00fdch s\u00e9ri\u00ed).<\/li>\n<\/ul>\n<p><\/p>\n<p>FTP server \u2013 je server, ktor\u00fd umo\u017e\u0148uje pou\u017e\u00edvanie protokolu prenosu s\u00faborov. M\u00e1 ur\u010dit\u00e9 vlastnosti, ktor\u00e9 ho odli\u0161uj\u00fa od be\u017en\u00fdch webov\u00fdch serverov:<\/p>\n<p><\/p>\n<ul>\n<li>Vy\u017eaduje sa autentifik\u00e1cia pou\u017e\u00edvate\u013eov<\/li>\n<li>V\u0161etky oper\u00e1cie sa vykon\u00e1vaj\u00fa v r\u00e1mci aktu\u00e1lnej rel\u00e1cie<\/li>\n<li>Mo\u017enos\u0165 vykon\u00e1vania r\u00f4znych akci\u00ed so s\u00faborov\u00fdm syst\u00e9mom<\/li>\n<li>Pre ka\u017ed\u00e9 spojenie sa pou\u017e\u00edva samostatn\u00fd kan\u00e1l<\/li>\n<\/ul>\n<p><\/p>\n<p>FTP klient \u2013 je program, ktor\u00fd umo\u017e\u0148uje pripoji\u0165 sa k vzdialen\u00e9mu serveru cez FTP a tie\u017e vykon\u00e1va\u0165 na \u0148om potrebn\u00e9 oper\u00e1cie so s\u00fa\u010das\u0165ami s\u00faborov\u00e9ho syst\u00e9mu. Klientom m\u00f4\u017ee by\u0165 celkom dobre aj prehliada\u010d, do adresn\u00e9ho riadku ktor\u00e9ho je potrebn\u00e9 zada\u0165 adresu, ktor\u00e1 predstavuje cestu k ur\u010dit\u00e9mu adres\u00e1ru alebo s\u00faboru na vzdialenom serveri, v s\u00falade so z\u00e1kladn\u00fdm blokov\u00fdm sch\u00e9mom URL:<\/p>\n<p><\/p>\n<p><code>ftp:\/\/user:pass@address:port\/directory\/file<\/code><\/p>\n<p><\/p>\n<p>Av\u0161ak, pou\u017eitie webov\u00e9ho prehliada\u010da na tento \u00fa\u010del umo\u017en\u00ed len prezera\u0165 alebo s\u0165ahova\u0165 po\u017eadovan\u00e9 s\u00fabory. Aby sa naplno vyu\u017eili v\u0161etky v\u00fdhody FTP, ako klient by sa malo pou\u017e\u00edva\u0165 \u0161pecializovan\u00e9 softv\u00e9rov\u00e9 vybavenie. <\/p>\n<p><\/p>\n<p>FTP autentifik\u00e1cia pou\u017e\u00edva sch\u00e9mu pou\u017e\u00edvate\u013esk\u00e9 meno\/heslo na poskytnutie pr\u00edstupu. Pou\u017e\u00edvate\u013esk\u00e9 meno sa posiela serveru pr\u00edkazom USER, a heslo pr\u00edkazom PASS. Ak server prijme inform\u00e1cie poskytnut\u00e9 klientom, po\u0161le klientovi pozvanie a za\u010d\u00edna rel\u00e1ciu. Pou\u017e\u00edvatelia m\u00f4\u017eu, ak server podporuje t\u00fato funkciu, vst\u00fapi\u0165 do syst\u00e9mu bez poskytnutia prihlasovac\u00edch \u00fadajov, ale server m\u00f4\u017ee poskytn\u00fa\u0165 len obmedzen\u00fd pr\u00edstup pre tak\u00e9 rel\u00e1cie.<\/p>\n<p><\/p>\n<p>Hostite\u013e, ktor\u00fd poskytuje FTP slu\u017ebu, m\u00f4\u017ee zabezpe\u010di\u0165 anonymn\u00fd pr\u00edstup k FTP. Pou\u017e\u00edvatelia sa zvy\u010dajne prihlasuj\u00fa ako \u201eanonymous\u201c (m\u00f4\u017ee by\u0165 rozli\u0161ovan\u00e9 na niektor\u00fdch FTP serveroch) ako meno pou\u017e\u00edvate\u013ea. Hoci sa zvy\u010dajne \u017eiada pou\u017e\u00edvate\u013eov, aby poslali adresu ich elektronickej po\u0161ty namiesto hesla, \u017eiadna overenie sa v skuto\u010dnosti nevykon\u00e1va. Mnoh\u00e9 FTP hostuj\u00face slu\u017eby, ktor\u00e9 poskytuj\u00fa aktualiz\u00e1cie softv\u00e9ru, podporuj\u00fa anonymn\u00fd pr\u00edstup.<\/p>\n<p><\/p>\n<h2>Sch\u00e9ma protokolu<\/h2>\n<p><\/p>\n<p>Interakcia \u201eklient-server\u201c pri FTP pripojen\u00ed m\u00f4\u017ee by\u0165 vidite\u013ene zn\u00e1zornen\u00e1 takto:<\/p>\n<p>\n<img decoding=\"async\" alt=\"Protokoly SFTP a FTPS\" src=\"\/wp-content\/uploads\/2020\/05\/9513d1898a0938a30b0f87d7956bc98f.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h1>Zabezpe\u010den\u00fd FTP<\/h1>\n<p><\/p>\n<p>FTP nebol p\u00f4vodne navrhnut\u00fd ako zabezpe\u010den\u00fd, preto\u017ee bol ur\u010den\u00fd na komunik\u00e1ciu medzi r\u00f4znymi vojensk\u00fdmi objektmi a zariadeniami. Av\u0161ak, s rozvojom a roz\u0161\u00edren\u00edm internetu sa riziko neopr\u00e1vnen\u00e9ho pr\u00edstupu zv\u00fd\u0161ilo mnohon\u00e1sobne. Vznikla potreba chr\u00e1ni\u0165 servery pred r\u00f4znymi typmi \u00fatokov. V m\u00e1ji 1999 autori RFC 2577 zhroma\u017edili zranite\u013enosti do nasledovn\u00e9ho zoznamu probl\u00e9mov:<\/p>\n<p><\/p>\n<ul>\n<li>Skryt\u00e9 \u00fatoky (bounce attacks)<\/li>\n<li>Spoof-\u00fatoky (spoof attacks)<\/li>\n<li>\u00datoky hrubou silou (brute force attacks)<\/li>\n<li>Zachyt\u00e1vanie paketov, sniffing (packet capture, sniffing)<\/li>\n<li>Zachyt\u00e1vanie portov (port stealing)<\/li>\n<\/ul>\n<p><\/p>\n<p>Be\u017en\u00fd FTP nem\u00e1 mo\u017enos\u0165 pren\u00e1\u0161a\u0165 \u00fadaje za\u0161ifrovane, a preto m\u00f4\u017eu by\u0165 men\u00e1 pou\u017e\u00edvate\u013eov, hesl\u00e1, pr\u00edkazy a in\u00e9 inform\u00e1cie jednoducho zachyten\u00e9 zlo\u010dincami. Be\u017en\u00fdm rie\u0161en\u00edm tohto probl\u00e9mu je pou\u017e\u00edvanie \"zabezpe\u010den\u00fdch\", TLS-ochr\u00e1nen\u00fdch verzi\u00ed zranite\u013en\u00e9ho protokolu (FTPS) alebo in\u00e9ho, viac zabezpe\u010den\u00e9ho protokolu, ako je SFTP\/SCP poskytovan\u00e9 v\u00e4\u010d\u0161inou implement\u00e1ci\u00ed protokolu Secure Shell.<\/p>\n<p><\/p>\n<h2>FTPS<\/h2>\n<p><\/p>\n<p>FTPS (FTP + SSL) je roz\u0161\u00edrenie \u0161tandardn\u00e9ho protokolu prenosu s\u00faborov, ktor\u00e9 prid\u00e1va do jeho z\u00e1kladnej funkcionality vytv\u00e1ranie \u0161ifrovan\u00fdch rel\u00e1ci\u00ed pomocou protokolu SSL (Secure Sockets Layer \u2014 \u00farove\u0148 zabezpe\u010den\u00fdch socketov). V s\u00fa\u010dasnosti je ochrana zabezpe\u010den\u00e1 jeho pokro\u010dilej\u0161\u00edm n\u00e1protivkom TLS (Transport Layer Security \u2014 zabezpe\u010denie na transportnej \u00farovni).<\/p>\n<p><\/p>\n<h3>SSL<\/h3>\n<p><\/p>\n<p>Protokol SSL bol navrhnut\u00fd spolo\u010dnos\u0165ou Netscape Communications v roku 1996 s cie\u013eom zabezpe\u010di\u0165 bezpe\u010dnos\u0165 a d\u00f4vernos\u0165 internetov\u00fdch spojen\u00ed. Protokol podporuje autentifik\u00e1ciu (potvrdenie identity) klienta a servera, nez\u00e1vis\u00ed od aplik\u00e1ci\u00ed a je transparentn\u00fd pre protokoly HTTP, FTP a Telnet.<\/p>\n<p><\/p>\n<p>Protokol SSL Handshake pozost\u00e1va z dvoch f\u00e1z: overenie identity servera a volite\u013en\u00e9 overenie identity klienta. V prvej f\u00e1ze server na \u017eiados\u0165 klienta posiela svoj certifik\u00e1t a parametre \u0161ifrovania. Potom klient vygeneruje hlavn\u00fd k\u013e\u00fa\u010d, za\u0161ifruje ho verejn\u00fdm k\u013e\u00fa\u010dom servera a odosiela serveru. Server de\u0161ifruje hlavn\u00fd k\u013e\u00fa\u010d svoj\u00edm s\u00fakromn\u00fdm k\u013e\u00fa\u010dom a potvrdzuje svoju identitu klientovi, odoslan\u00edm spr\u00e1vy podp\u00edsanej hlavn\u00fdm k\u013e\u00fa\u010dom klienta.<\/p>\n<p><\/p>\n<p>Nasleduj\u00face \u00fadaje s\u00fa \u0161ifrovan\u00e9 a overen\u00e9 k\u013e\u00fa\u010dmi, ktor\u00e9 s\u00fa z\u00edskan\u00e9 na z\u00e1klade tohto master k\u013e\u00fa\u010da. V druhom kroku, ktor\u00fd nie je povinn\u00fd, server posiela po\u017eiadavku klientovi a klient potvrdzuje serveru svoju autentickos\u0165 vr\u00e1ten\u00edm po\u017eiadavky s vlastn\u00fdm digit\u00e1lnym podpisom a certifik\u00e1tom verejn\u00e9ho k\u013e\u00fa\u010da.<\/p>\n<p><\/p>\n<p>SSL podporuje r\u00f4zne kryptografick\u00e9 algoritmy. Pri nadv\u00e4zovan\u00ed spojenia sa pou\u017e\u00edva kryptosyst\u00e9m verejn\u00e9ho k\u013e\u00fa\u010da RSA. Po v\u00fdmene k\u013e\u00fa\u010dov sa pou\u017e\u00edvaj\u00fa r\u00f4zne \u0161ifrovacie met\u00f3dy: RC2, RC4, IDEA, DES a TripleDES. Taktie\u017e sa pou\u017e\u00edva MD5 \u2014 algoritmus na tvorbu digestov spr\u00e1v. Syntax certifik\u00e1tov verejn\u00e9ho k\u013e\u00fa\u010da je pop\u00edsan\u00e1 v X.509.<\/p>\n<p><\/p>\n<p>Jednou z v\u00fdznamn\u00fdch v\u00fdhod SSL je jeho \u00fapln\u00e1 softv\u00e9rov\u00e1 a platformov\u00e1 nez\u00e1vislos\u0165. Protokol bol navrhnut\u00fd na princ\u00edpoch prenosnosti a ideol\u00f3gia jeho kon\u0161trukcie nez\u00e1vis\u00ed od aplik\u00e1ci\u00ed, v r\u00e1mci ktor\u00fdch je pou\u017e\u00edvan\u00fd. Okrem toho je d\u00f4le\u017eit\u00e9, \u017ee nad protokolom SSL m\u00f4\u017eu by\u0165 transparentne aplikovan\u00e9 aj in\u00e9 protokoly; bu\u010f pre \u010fal\u0161ie zv\u00fd\u0161enie \u00farovne ochrany cie\u013eov\u00fdch informa\u010dn\u00fdch tokov, alebo na prisp\u00f4sobenie kryptografick\u00fdch schopnost\u00ed SSL pre nejak\u00fa konkr\u00e9tnu \u00falohu.<\/p>\n<p><\/p>\n<h3>SSL pripojenie<\/h3>\n<p>\n<img decoding=\"async\" alt=\"Protokoly SFTP a FTPS\" src=\"\/wp-content\/uploads\/2020\/05\/5c002ffba19382c1d3b330d7c948692b.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p>Poskytovan\u00fd bezpe\u010dn\u00fd kan\u00e1l SSL m\u00e1 tri hlavn\u00e9 vlastnosti: <\/p>\n<p><\/p>\n<ul>\n<li>Kan\u00e1l je s\u00fakromn\u00fd. \u0160ifrovanie sa pou\u017e\u00edva pre v\u0161etky spr\u00e1vy po jednoduchom dial\u00f3gu, ktor\u00fd sl\u00fa\u017ei na ur\u010denie tajn\u00e9ho k\u013e\u00fa\u010da.<\/li>\n<li>Kan\u00e1l je autentifikovan\u00fd. Serverov\u00e1 strana dial\u00f3gu je v\u017edy autentifikovan\u00e1, zatia\u013e \u010do klientsk\u00e1 \u2014 autentifikovan\u00e1 volite\u013ene.<\/li>\n<li>Kan\u00e1l je spo\u013eahliv\u00fd. Transport spr\u00e1v zah\u0155\u0148a kontrolu integrity (s vyu\u017eit\u00edm MAC).<\/li>\n<\/ul>\n<p><\/p>\n<h3>Vlastnosti FTPS<\/h3>\n<p><\/p>\n<p>Existuj\u00fa dve implement\u00e1cie FTPS, ktor\u00e9 pou\u017e\u00edvaj\u00fa r\u00f4zne met\u00f3dy zabezpe\u010denia: <\/p>\n<p><\/p>\n<ul>\n<li>Nejasn\u00e1 met\u00f3da predpoklad\u00e1 pou\u017eitie \u0161tandardn\u00e9ho protokolu SSL s nastaven\u00edm rel\u00e1cie pred odoslan\u00edm \u00fadajov, \u010do naru\u0161uje kompatibilitu s be\u017en\u00fdmi FTP klientami a servermi. Pre sp\u00e4tn\u00fa kompatibilitu s klientmi, ktor\u00ed nepodporuj\u00fa FTPS, sa pre kontroln\u00e9 spojenie pou\u017e\u00edva TCP port 990 a pre prenos \u00fadajov \u2014 989. To umo\u017e\u0148uje zachova\u0165 \u0161tandardn\u00fd port 21 pre protokol FTP. T\u00e1to met\u00f3da bola ozna\u010den\u00e1 za zastaran\u00fa.<\/li>\n<li>Explicit \u2013 je omnoho pohodlnej\u0161\u00ed, preto\u017ee pou\u017e\u00edva pr\u00edkazy \u0161tandardn\u00e9ho FTP, ale pri odpovedi \u0161ifruje d\u00e1ta, \u010do umo\u017e\u0148uje vyu\u017e\u00edva\u0165 jedno a to ist\u00e9 riadiace spojenie pre FTP aj FTPS. Klient mus\u00ed v\u00fdslovne po\u017eiada\u0165 server o zabezpe\u010den\u00fd prenos \u00fadajov a n\u00e1sledne potvrdi\u0165 sp\u00f4sob \u0161ifrovania. Ak klient nepo\u017eaduje zabezpe\u010den\u00fd prenos, FTPS server m\u00e1 pr\u00e1vo bu\u010f zachova\u0165, alebo uzavrie\u0165 nezabezpe\u010den\u00e9 spojenie. Mechanizmus dohodovania identifik\u00e1cie a ochrany \u00fadajov bol pridan\u00fd pod RFC 2228, ktor\u00fd zah\u0155\u0148a nov\u00fd FTP pr\u00edkaz AUTH. Hoci tento \u0161tandard jasne neur\u010duje mechanizmy ochrany, ur\u010duje, \u017ee zabezpe\u010den\u00e9 spojenie mus\u00ed iniciova\u0165 klient pomocou vy\u0161\u0161ie op\u00edsan\u00e9ho algoritmu. Ak server nepodporuje zabezpe\u010den\u00e9 spojenia, mus\u00ed by\u0165 vr\u00e1ten\u00fd k\u00f3d chyby 504. FTPS klienti m\u00f4\u017eu z\u00edska\u0165 inform\u00e1cie o podporovan\u00fdch protokoloch ochrany serverom pomocou pr\u00edkazu FEAT, av\u0161ak server nie je povinn\u00fd zverejni\u0165, ak\u00e9 \u00farovne zabezpe\u010denia podporuje. Najobvyklej\u0161ie FTPS pr\u00edkazy s\u00fa AUTH TLS a AUTH SSL, ktor\u00e9 zabezpe\u010duj\u00fa TLS a SSL.<\/li>\n<\/ul>\n<p><\/p>\n<h2>SFTP<\/h2>\n<p><\/p>\n<p>SFTP (Secure File Transfer Protocol) \u2013 protokol aplika\u010dnej \u00farovne na prenos s\u00faborov, funguj\u00faci nad zabezpe\u010den\u00fdm kan\u00e1lom. Nemali by ste ho zamie\u0148a\u0165 s (Simple File Transfer Protocol), ktor\u00fd m\u00e1 rovnak\u00fa skratku. Ak je FTPS jednoducho roz\u0161\u00edren\u00edm FTP, SFTP je samostatn\u00fd a nijako nes\u00favisiaci protokol, ktor\u00fd ako z\u00e1klad pou\u017e\u00edva SSH (Secure Shell \u2013 bezpe\u010dn\u00e1 schr\u00e1nka).<\/p>\n<p><\/p>\n<h3>Secure Shell<\/h3>\n<p><\/p>\n<p>V\u00fdvoj protokolu zabezpe\u010dovala jedna z skup\u00edn IETF s n\u00e1zvom Secsh. Pracovn\u00e1 dokument\u00e1cia k nov\u00e9mu protokolu SFTP sa nestala ofici\u00e1lnym \u0161tandardom, av\u0161ak za\u010dala sa akt\u00edvne pou\u017e\u00edva\u0165 na v\u00fdvoj aplik\u00e1ci\u00ed. N\u00e1sledne bolo vydan\u00fdch \u0161es\u0165 verzi\u00ed protokolu. Av\u0161ak, postupn\u00e9 zvy\u0161ovanie funkcionality v \u0148om viedlo k tomu, \u017ee 14. augusta 2006 bolo prijat\u00e9 rozhodnutie o zastaven\u00ed pr\u00e1ce na rozvoji protokolu vzh\u013eadom na splnenie hlavnej \u00falohy projektu (v\u00fdvoj SSH) a nedostatok dostato\u010dnej expertn\u00e9ho \u00farovne na prechod k v\u00fdvoju plnohodnotn\u00e9ho protokolu vzdialen\u00e9ho s\u00faborov\u00e9ho syst\u00e9mu.<\/p>\n<p><\/p>\n<p>SSH je sie\u0165ov\u00fd protokol, ktor\u00fd umo\u017e\u0148uje dia\u013ekov\u00e9 ovl\u00e1danie opera\u010dn\u00e9ho syst\u00e9mu a tunelovanie TCP spojen\u00ed (napr\u00edklad na prenos s\u00faborov). Je funk\u010dne podobn\u00fd protokolom Telnet a rlogin, ale na rozdiel od nich \u0161ifruje cel\u00fd prenos, vr\u00e1tane pren\u00e1\u0161an\u00fdch hesiel. SSH umo\u017e\u0148uje v\u00fdber r\u00f4znych \u0161ifrovac\u00edch algoritmov. SSH klienti a SSH servery s\u00fa dostupn\u00e9 pre v\u00e4\u010d\u0161inu sie\u0165ov\u00fdch opera\u010dn\u00fdch syst\u00e9mov.<\/p>\n<p><\/p>\n<p>SSH umo\u017e\u0148uje bezpe\u010dne pren\u00e1\u0161a\u0165 takmer ktor\u00fdko\u013evek in\u00fd sie\u0165ov\u00fd protokol v nechr\u00e1nenej sieti. T\u00fdmto sp\u00f4sobom je mo\u017en\u00e9 nielen dia\u013ekovo pracova\u0165 na po\u010d\u00edta\u010di cez pr\u00edkazov\u00fd riadok, ale aj pren\u00e1\u0161a\u0165 \u0161ifrovan\u00fd zvukov\u00fd alebo video prenos (napr\u00edklad z webovej kamery). SSH m\u00f4\u017ee tie\u017e pou\u017e\u00edva\u0165 kompresiu pren\u00e1\u0161an\u00fdch \u00fadajov na ich n\u00e1sledn\u00e9 \u0161ifrovanie, \u010do je praktick\u00e9 napr\u00edklad pre dia\u013ekov\u00e9 sp\u00fa\u0161\u0165anie klientov X Window System.<\/p>\n<p><\/p>\n<p>Prv\u00e1 verzia protokolu, SSH-1, bola vyvinut\u00e1 v roku 1995 v\u00fdskumn\u00edkom Tatu Ulj\u00f6nenom z Technickej univerzity v Helsink\u00e1ch (F\u00ednsko). SSH-1 bol nap\u00edsan\u00fd na zabezpe\u010denie v\u00e4\u010d\u0161ej d\u00f4vernosti ako protokoly rlogin, telnet a rsh. V roku 1996 bola vyvinut\u00e1 bezpe\u010dnej\u0161ia verzia protokolu, SSH-2, ktor\u00e1 nie je sp\u00e4tne kompatibiln\u00e1 so SSH-1. Protokol nadobudol e\u0161te v\u00e4\u010d\u0161iu popularitu a do roku 2000 mal pribli\u017ene dva mili\u00f3ny pou\u017e\u00edvate\u013eov. V s\u00fa\u010dasnosti sa pod pojmom \"SSH\" zvy\u010dajne rozumie pr\u00e1ve SSH-2, preto\u017ee prv\u00e1 verzia protokolu sa kv\u00f4li v\u00fdznamn\u00fdm nedostatkom v s\u00fa\u010dasnosti takmer nepou\u017e\u00edva. V roku 2006 bol protokol schv\u00e1len\u00fd pracovnou skupinou IETF ako internetov\u00fd \u0161tandard.<\/p>\n<p><\/p>\n<p>Existuj\u00fa dve roz\u0161\u00edrenia SSH: s\u00fakromn\u00e1 komer\u010dn\u00e1 a bezplatn\u00e1 open source. Bezplatn\u00e1 verzia sa naz\u00fdva OpenSSH. K roku 2006 pou\u017e\u00edvalo 80 % po\u010d\u00edta\u010dov na internete pr\u00e1ve OpenSSH. S\u00fakromn\u00fa verziu vyv\u00edja organiz\u00e1cia SSH Communications Security, ktor\u00e1 je stopercentnou dc\u00e9rskou spolo\u010dnos\u0165ou korpor\u00e1cie Tectia a je bezplatn\u00e1 na nekomer\u010dn\u00e9 pou\u017eitie. Tieto implement\u00e1cie obsahuj\u00fa prakticky rovnak\u00fd s\u00fabor pr\u00edkazov.<\/p>\n<p><\/p>\n<p>Protokol SSH-2, na rozdiel od protokolu telnet, je odoln\u00fd vo\u010di \u00fatokom odpo\u010d\u00favania prenosu (\u201esniffing\u201c), ale nie je odoln\u00fd vo\u010di \u00fatokom \u201e\u010dlovek v strede\u201c. Protokol SSH-2 je tie\u017e odoln\u00fd vo\u010di \u00fatokom cez prevzatie rel\u00e1cie (angl. session hijacking), preto\u017ee nie je mo\u017en\u00e9 pripoji\u0165 sa k u\u017e nadstavenej rel\u00e1cii alebo ju zachyti\u0165.<\/p>\n<p><\/p>\n<p>Na zabr\u00e1nenie \u00fatokom \u201e\u010dlovek v strede\u201c pri pripojen\u00ed k hostite\u013eovi, ktor\u00e9ho k\u013e\u00fa\u010d je pre klienta zatia\u013e nezn\u00e1my, klientsk\u00fd softv\u00e9r pou\u017e\u00edvate\u013eovi zobrazuje \u201eodtla\u010dok k\u013e\u00fa\u010da\u201c (angl. key fingerprint). Odpor\u00fa\u010da sa starostlivo skontrolova\u0165 zobrazen\u00fd odtla\u010dok k\u013e\u00fa\u010da klientsk\u00fdm softv\u00e9rom s odtla\u010dkom k\u013e\u00fa\u010da servera, ide\u00e1lne z\u00edskan\u00fdm prostredn\u00edctvom d\u00f4veryhodn\u00fdch komunika\u010dn\u00fdch kan\u00e1lov alebo osobne.<\/p>\n<p><\/p>\n<p>Podpora SSH je realizovan\u00e1 vo v\u0161etk\u00fdch UNIX-like syst\u00e9moch a na v\u00e4\u010d\u0161ine z nich s\u00fa medzi \u0161tandardn\u00fdmi utilitami pr\u00edtomn\u00e9 klienti a servery ssh. Existuje mnoho realiz\u00e1ci\u00ed SSH klientov aj pre ne-UNIX opera\u010dn\u00e9 syst\u00e9my. Protokol si z\u00edskal ve\u013ek\u00fa popularitu po \u0161irokom rozvoji analyz\u00e1torov prenosu a sp\u00f4sobov naru\u0161enia fungovania lok\u00e1lnych siet\u00ed ako alternat\u00edvne nebezpe\u010dn\u00e9ho protokolu Telnet na spravovanie d\u00f4le\u017eit\u00fdch uzlov.<\/p>\n<p><\/p>\n<h3>Spojenie pomocou SSH<\/h3>\n<p><\/p>\n<p>Na pr\u00e1cu cez SSH je potrebn\u00fd SSH server a SSH klient. Server po\u010d\u00fava pripojenia od klientsk\u00fdch strojov a po nadviazan\u00ed spojenia vykon\u00e1 autentifik\u00e1ciu, po ktorej za\u010dne obsluhova\u0165 klienta. Klient sa vyu\u017e\u00edva na prihl\u00e1senie na vzdialen\u00fd stroj a vykon\u00e1vanie pr\u00edkazov.<\/p>\n<p>\n<img decoding=\"async\" alt=\"Protokoly SFTP a FTPS\" src=\"\/wp-content\/uploads\/2020\/05\/2370127e0483cf579c3ae461819ada7c.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h3>Porovnanie s FTPS<\/h3>\n<p><\/p>\n<p>Hlavn\u00e9, \u010do odde\u013euje SFTP od \u0161tandardn\u00e9ho FTP a FTPS, je to, \u017ee SFTP \u0161ifruje \u00faplne v\u0161etky pr\u00edkazy, men\u00e1 pou\u017e\u00edvate\u013eov, hesl\u00e1 a \u010fal\u0161ie d\u00f4vern\u00e9 inform\u00e1cie.<\/p>\n<p><\/p>\n<p>Oba protokoly FTPS a SFTP pou\u017e\u00edvaj\u00fa kombin\u00e1ciu asymetrick\u00fdch algoritmov (RSA, DSA), symetrick\u00fdch algoritmov (DES\/3DES, AES, Twhofish at\u010f.), ako aj algoritmus v\u00fdmeny k\u013e\u00fa\u010dov. Na autentifik\u00e1ciu FTPS (alebo, ak budeme presnej\u0161\u00ed, SSL\/TLS pod\u013ea protokolu FTP) pou\u017e\u00edva certifik\u00e1ty X.509, zatia\u013e \u010do SFTP (SSH protokol) pou\u017e\u00edva SSH k\u013e\u00fa\u010de.<\/p>\n<p><\/p>\n<p>Certifik\u00e1ty X.509 zah\u0155\u0148aj\u00fa verejn\u00fd k\u013e\u00fa\u010d a ur\u010dit\u00fa inform\u00e1ciu o certifik\u00e1te vlastn\u00edka. Tieto inform\u00e1cie umo\u017e\u0148uj\u00fa na druhej strane overi\u0165 integritu samotn\u00e9ho certifik\u00e1tu, pravos\u0165 a vlastn\u00edka osved\u010denia. Certifik\u00e1ty X.509 maj\u00fa zodpovedaj\u00faci s\u00fakromn\u00fd k\u013e\u00fa\u010d, ktor\u00fd sa zvy\u010dajne uchov\u00e1va oddelene od certifik\u00e1tu z d\u00f4vodov bezpe\u010dnosti.<\/p>\n<p><\/p>\n<p>SSH k\u013e\u00fa\u010d obsahuje iba verejn\u00fd k\u013e\u00fa\u010d (zodpovedaj\u00faci s\u00fakromn\u00fd k\u013e\u00fa\u010d sa uchov\u00e1va osobitne). Neobsahuje \u017eiadne inform\u00e1cie o vlastn\u00edkoch k\u013e\u00fa\u010da. Niektor\u00e9 implement\u00e1cie SSH pou\u017e\u00edvaj\u00fa certifik\u00e1ty X.509 na autentifik\u00e1ciu, ale v skuto\u010dnosti nekontroluj\u00fa cel\u00fa re\u0165azec certifik\u00e1tov \u2014 pou\u017e\u00edva sa iba verejn\u00fd k\u013e\u00fa\u010d (\u010do rob\u00ed tak\u00fato autentifik\u00e1ciu ne\u00faplnou).<\/p>\n<p><\/p>\n<h1>Z\u00e1ver<\/h1>\n<p><\/p>\n<p>Protokol FTP bezpochyby st\u00e1le hr\u00e1 d\u00f4le\u017eit\u00fa \u00falohu v oblasti uchov\u00e1vania a \u0161\u00edrenia inform\u00e1ci\u00ed v sieti, napriek svojmu pokro\u010dil\u00e9mu veku. Je to pohodln\u00fd, multifunk\u010dn\u00fd a \u0161tandardizovan\u00fd protokol. Na jeho z\u00e1klade bolo postaven\u00fdch mno\u017estvo s\u00faborov\u00fdch arch\u00edvov, bez ktor\u00fdch by technick\u00e1 pr\u00e1ca nebola tak efekt\u00edvna. Okrem toho sa \u013eahko nastavuje a existuj\u00fa serverov\u00e9 a klientsk\u00e9 programy prakticky pre v\u0161etky aktu\u00e1lne i menej popul\u00e1rne platformy.<\/p>\n<p><\/p>\n<p>Na druhej strane jeho chr\u00e1nen\u00e9 verzie rie\u0161ia probl\u00e9m ochrany s\u00fakromia uchov\u00e1van\u00fdch a pren\u00e1\u0161an\u00fdch d\u00e1t v modernom svete. Oba nov\u00e9 protokoly maj\u00fa svoje v\u00fdhody a nev\u00fdhody a plnia trochu odli\u0161n\u00e9 \u00falohy. V oblastiach, kde je preferovan\u00fd s\u00faborov\u00fd arch\u00edv, je vhodnej\u0161ie pou\u017ei\u0165 FTPS, najm\u00e4 ak sa tam predt\u00fdm pou\u017e\u00edval klasick\u00fd FTP. SFTP je menej roz\u0161\u00edren\u00fd kv\u00f4li svojej nekompatibilite so star\u00fdm protokolom, ale je bezpe\u010dnej\u0161\u00ed a m\u00e1 v\u00e4\u010d\u0161iu funkcionalitu, preto\u017ee je s\u00fa\u010das\u0165ou syst\u00e9mu vzdialenej spr\u00e1vy.<\/p>\n<p><\/p>\n<h1>Zoznam zdrojov<\/h1>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/topref.ru\/referat\/52883.html\">Refer\u00e1t \u201eFTP protokol. V\u0161eobecn\u00e9 inform\u00e1cie a vlastnosti\u201c<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/studentlib.com\/referat-191865-protokoly_ssh_cmip_telnet.html\">Refer\u00e1t \u201eProtokoly SSH, CMIP, Telnet\u201c<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/works.doklad.ru\/view\/l4Ukh5_LHzk.html\">Prezent\u00e1cia \u201eSSL\/TLS\u201c<\/a><\/noindex><\/li>\n<\/ul>\n<p>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/500438\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u0435\u0434\u0438\u0441\u043b\u043e\u0432\u0438\u0435 \u0411\u0443\u043a\u0432\u0430\u043b\u044c\u043d\u043e \u043d\u0435\u0434\u0435\u043b\u044e \u043d\u0430\u0437\u0430\u0434 \u044f \u043f\u0438\u0441\u0430\u043b \u0440\u0435\u0444\u0435\u0440\u0430\u0442 \u043f\u043e \u043e\u0431\u043e\u0437\u043d\u0430\u0447\u0435\u043d\u043d\u043e\u0439 \u0432 \u0437\u0430\u0433\u043e\u043b\u043e\u0432\u043a\u0435 \u0442\u0435\u043c\u0435 \u0438 \u0441\u0442\u043e\u043b\u043a\u043d\u0443\u043b\u0441\u044f \u0441 \u0442\u0435\u043c, \u0447\u0442\u043e, \u0441\u043a\u0430\u0436\u0435\u043c \u0442\u0430\u043a, \u043f\u043e\u0437\u043d\u0430\u0432\u0430\u0442\u0435\u043b\u044c\u043d\u043e\u0439 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438 \u0432 \u0441\u0435\u0442\u0438 \u043d\u0435 \u0442\u0430\u043a \u0443\u0436 \u043c\u043d\u043e\u0433\u043e. \u0412 \u043e\u0441\u043d\u043e\u0432\u043d\u043e\u043c \u0441\u0443\u0445\u0438\u0435 \u0444\u0430\u043a\u0442\u044b \u0438 \u0438\u043d\u0441\u0442\u0440\u0443\u043a\u0446\u0438\u0438 \u043f\u043e \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0435. \u041f\u043e\u044d\u0442\u043e\u043c\u0443 \u044f \u0440\u0435\u0448\u0438\u043b \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043f\u043e\u0434\u043a\u043e\u0440\u0440\u0435\u043a\u0442\u0438\u0440\u043e\u0432\u0430\u0442\u044c \u0442\u0435\u043a\u0441\u0442 \u0438 \u0432\u044b\u043b\u043e\u0436\u0438\u0442\u044c \u0435\u0433\u043e \u0432 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u0441\u0442\u0430\u0442\u044c\u0438. \u0427\u0442\u043e \u0442\u0430\u043a\u043e\u0435 FTP FTP (File Transfer Protocol) \u2013 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":80501,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-80500","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0440\u0435\u0434\u0438\u0441\u043b\u043e\u0432\u0438\u0435 \u0411\u0443\u043a\u0432\u0430\u043b\u044c\u043d\u043e \u043d\u0435\u0434\u0435\u043b\u044e \u043d\u0430\u0437\u0430\u0434 \u044f \u043f\u0438\u0441\u0430\u043b \u0440\u0435\u0444\u0435\u0440\u0430\u0442 \u043f\u043e \u043e\u0431\u043e\u0437\u043d\u0430\u0447\u0435\u043d\u043d\u043e\u0439 \u0432 \u0437\u0430\u0433\u043e\u043b\u043e\u0432\u043a\u0435 \u0442\u0435\u043c\u0435 \u0438 \u0441\u0442\u043e\u043b\u043a\u043d\u0443\u043b\u0441\u044f \u0441 \u0442\u0435\u043c, \u0447\u0442\u043e, \u0441\u043a\u0430\u0436\u0435\u043c \u0442\u0430\u043a, \u043f\u043e\u0437\u043d\u0430\u0432\u0430\u0442\u0435\u043b\u044c\u043d\u043e\u0439 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438 \u0432 \u0441\u0435\u0442\u0438 \u043d\u0435 \u0442\u0430\u043a \u0443\u0436 \u043c\u043d\u043e\u0433\u043e.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/protokoly-sftp-i-ftps\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u044b SFTP \u0438 FTPS | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u0435\u0434\u0438\u0441\u043b\u043e\u0432\u0438\u0435 \u0411\u0443\u043a\u0432\u0430\u043b\u044c\u043d\u043e \u043d\u0435\u0434\u0435\u043b\u044e \u043d\u0430\u0437\u0430\u0434 \u044f \u043f\u0438\u0441\u0430\u043b \u0440\u0435\u0444\u0435\u0440\u0430\u0442 \u043f\u043e \u043e\u0431\u043e\u0437\u043d\u0430\u0447\u0435\u043d\u043d\u043e\u0439 \u0432 \u0437\u0430\u0433\u043e\u043b\u043e\u0432\u043a\u0435 \u0442\u0435\u043c\u0435 \u0438 \u0441\u0442\u043e\u043b\u043a\u043d\u0443\u043b\u0441\u044f \u0441 \u0442\u0435\u043c, \u0447\u0442\u043e, \u0441\u043a\u0430\u0436\u0435\u043c \u0442\u0430\u043a, \u043f\u043e\u0437\u043d\u0430\u0432\u0430\u0442\u0435\u043b\u044c\u043d\u043e\u0439 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438 \u0432 \u0441\u0435\u0442\u0438 \u043d\u0435 \u0442\u0430\u043a \u0443\u0436 \u043c\u043d\u043e\u0433\u043e.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/protokoly-sftp-i-ftps\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-05-06T11:42:29+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-05-06T11:42:29+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Protokoly SFTP a FTPS | ProHoster","description":"Predslov Pred t\u00fd\u017ed\u0148om som p\u00edsal refer\u00e1t na t\u00e9mu uveden\u00fa v nadpise a narazil som na to, \u017ee, povedzme, pou\u010dnej inform\u00e1cie na internete nie je a\u017e tak ve\u013ea.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/protokoly-sftp-i-ftps","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u044b SFTP \u0438 FTPS | ProHoster","og:description":"\u041f\u0440\u0435\u0434\u0438\u0441\u043b\u043e\u0432\u0438\u0435 \u0411\u0443\u043a\u0432\u0430\u043b\u044c\u043d\u043e \u043d\u0435\u0434\u0435\u043b\u044e \u043d\u0430\u0437\u0430\u0434 \u044f \u043f\u0438\u0441\u0430\u043b \u0440\u0435\u0444\u0435\u0440\u0430\u0442 \u043f\u043e \u043e\u0431\u043e\u0437\u043d\u0430\u0447\u0435\u043d\u043d\u043e\u0439 \u0432 \u0437\u0430\u0433\u043e\u043b\u043e\u0432\u043a\u0435 \u0442\u0435\u043c\u0435 \u0438 \u0441\u0442\u043e\u043b\u043a\u043d\u0443\u043b\u0441\u044f \u0441 \u0442\u0435\u043c, \u0447\u0442\u043e, \u0441\u043a\u0430\u0436\u0435\u043c \u0442\u0430\u043a, \u043f\u043e\u0437\u043d\u0430\u0432\u0430\u0442\u0435\u043b\u044c\u043d\u043e\u0439 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438 \u0432 \u0441\u0435\u0442\u0438 \u043d\u0435 \u0442\u0430\u043a \u0443\u0436 \u043c\u043d\u043e\u0433\u043e.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/protokoly-sftp-i-ftps","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-05-06T11:42:29+00:00","article:modified_time":"2020-05-06T11:42:29+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"80500","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 16:16:28","updated":"2022-10-01 20:55:08","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/80500","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=80500"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/80500\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/80501"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=80500"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=80500"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=80500"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}