{"id":32603,"date":"2019-10-31T21:47:55","date_gmt":"2019-10-31T18:47:55","guid":{"rendered":"https:\/\/prohoster.info\/blog\/potentsialnye-ataki-na-https-i-kak-ot-nih-zashhititsya\/"},"modified":"2019-10-31T21:47:55","modified_gmt":"2019-10-31T18:47:55","slug":"potentsialnye-ataki-na-https-i-kak-ot-nih-zashhititsya","status":"publish","type":"post","link":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/potentsialnye-ataki-na-https-i-kak-ot-nih-zashhititsya","title":{"rendered":"Potencijalni napadi na HTTPS i kako se za\u0161tititi od njih","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Polovina web stranica <noindex><a rel=\"nofollow\" href=\"https:\/\/1cloud.ru\/services\/ssl\/dv?utm_source=habrahabr&amp;utm_medium=cpm&amp;utm_campaign=https&amp;utm_content=site\">koristi HTTPS<\/a><\/noindex>, a njihov broj se konstantno pove\u0107ava. Protokol smanjuje rizik od presretanja saobra\u0107aja, ali ne isklju\u010duje poku\u0161aje napada. O nekima od njih \u2014 POODLE, BEAST, DROWN i drugi \u2014 i na\u010dinima za\u0161tite, govori\u0107emo u na\u0161em materijalu.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/1cloud\/blog\/449866\/\"><img decoding=\"async\" alt=\"Potencijalni napadi na HTTPS i kako se za\u0161tititi od njih\" src=\"\/wp-content\/uploads\/2019\/04\/305d426243ec7e580b5dd14de36eaed0.jpeg\" style=\"display:block;margin: 0 auto;\" \/> <\/a><\/noindex><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\n<i>\/ Flickr \/ <noindex><a rel=\"nofollow\" href=\"https:\/\/www.flickr.com\/photos\/2011101\/23434336563\/\">Sven Graeme<\/a><\/noindex> \/ CC BY-SA<\/i><\/p>\n<h2>POODLE<\/h2>\n<p>\nPrvi put o napadu <noindex><a rel=\"nofollow\" href=\"https:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2014-3566\">POODLE<\/a><\/noindex> se saznalo 2014. godine. Ranjivost u protokolu SSL 3.0 otkrio je stru\u010dnjak za bezbednost Bodo M\u00f6ller sa kolegama iz Google-a.<\/p>\n<p>Njena su\u0161tina je u slede\u0107em: haker prisiljava klijenta da uspostavi vezu putem SSL 3.0, emuliraju\u0107i prekide veze. Zatim tra\u017ei u enkriptovanom <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%A0%D0%B5%D0%B6%D0%B8%D0%BC_%D1%81%D1%86%D0%B5%D0%BF%D0%BB%D0%B5%D0%BD%D0%B8%D1%8F_%D0%B1%D0%BB%D0%BE%D0%BA%D0%BE%D0%B2_%D1%88%D0%B8%D1%84%D1%80%D0%BE%D1%82%D0%B5%D0%BA%D1%81%D1%82%D0%B0\">CBC<\/a><\/noindex>-na\u010dinu saobra\u0107aja posebne poruke-oznake. Pomo\u0107u serije la\u017enih zahteva, napada\u010d dobija mogu\u0107nost rekonstrukcije sadr\u017eaja podataka od interesa, na primer, kola\u010di\u0107a.<\/p>\n<p>SSL 3.0 je zastareli protokol. Ali pitanje njegove sigurnosti je jo\u0161 uvek aktuelno. Klijenti ga koriste da bi izbegli probleme kompatibilnosti sa serverima. Prema nekim podacima, skoro 7% od 100.000 najpopularnijih web stranica <noindex><a rel=\"nofollow\" href=\"https:\/\/www.thesslstore.com\/blog\/nearly-21-of-the-worlds-top-100000-websites-still-arent-using-https\/\">i dalje podr\u017eava SSL 3.0<\/a><\/noindex>. Tako\u0111e <noindex><a rel=\"nofollow\" href=\"https:\/\/www.globalsign.com\/en\/blog\/poodle-vulnerability-expands-beyond-sslv3-to-tls\/\">postoje<\/a><\/noindex> modifikacije POODLE, koje su cilj vi\u0161e moderne TLS 1.0 i TLS 1.1. Ove godine <noindex><a rel=\"nofollow\" href=\"https:\/\/www.tripwire.com\/state-of-security\/vulnerability-management\/zombie-poodle-goldendoodle\/\">pojavila su se<\/a><\/noindex> nove napade Zombie POODLE i GOLDENDOODLE, koji zaobilaze za\u0161titu TLS 1.2 (oni su i dalje povezani sa CBC-kriptovanjem).<\/p>\n<p><b>Kako se za\u0161tititi.<\/b> U slu\u010daju originalnog POODLE-a, potrebno je isklju\u010diti podr\u0161ku za SSL 3.0. Me\u0111utim, u ovom slu\u010daju postoji rizik od problema sa kompatibilno\u0161\u0107u. Alternativno re\u0161enje mo\u017ee biti mehanizam TLS_FALLBACK_SCSV \u2014 on garantuje da \u0107e razmena podataka putem SSL 3.0 biti obavljena samo sa starim sistemima. Napada\u010di vi\u0161e ne mogu inicirati sni\u017eavanje verzije protokola. Na\u010din za\u0161tite od Zombie POODLE-a i GOLDENDOODLE-a je isklju\u010divanje podr\u0161ke za CBC u aplikacijama zasnovanim na TLS 1.2. Radikalno re\u0161enje bi bilo prelazak na TLS 1.3 \u2014 u novoj verziji protokola ne koristi se CBC-kriptovanje. Umesto toga, koriste se otporniji AES i ChaCha20.<\/p>\n<h2>BEAST<\/h2>\n<p>\nJedan od najranijih napada na SSL i TLS 1.0, otkriven 2011. godine. Kao i POODLE, BEAST <noindex><a rel=\"nofollow\" href=\"https:\/\/www.acunetix.com\/blog\/articles\/tls-vulnerabilities-attacks-final-part\/\">koristi<\/a><\/noindex> \u043e\u0441\u043e\u0431itnosti CBC-\u0161ifriranja. Napada\u010di instaliraju JavaScript-agent ili Java-applett na klijentov ure\u0111aj, koji zamjenjuje poruke prilikom prijenosa podataka preko TLS ili SSL. Budu\u0107i da napada\u010di znaju sadr\u017eaj \"la\u017enih\" paketa, mogu ih iskoristiti da de\u0161ifriraju vektor inicijalizacije i pro\u010ditaju ostale poruke poslane serveru, kao \u0161to su cookie-datoteke za autentifikaciju.<\/p>\n<p>Do danas, ranjivosti BEAST i dalje su <noindex><a rel=\"nofollow\" href=\"https:\/\/www.zdnet.com\/article\/its-2018-and-network-middleware-still-cant-handle-tls-without-breaking-encryption\/\">podlo\u017ene brojnim mre\u017enim alatima<\/a><\/noindex>: proxy-serveri i aplikacije za za\u0161titu lokalnih internet-gatewaya.<\/p>\n<p><b>Kako se za\u0161tititi.<\/b> Napada\u010du je potrebno redovito slati zahtjeve kako bi de\u0161ifrirao podatke. U VMware <noindex><a rel=\"nofollow\" href=\"https:\/\/kb.vmware.com\/s\/article\/2008784\">preporu\u010duju<\/a><\/noindex> smanjiti trajanje SSLSessionCacheTimeout \u2014 sa pet minuta (preporu\u010dena postavka prema defaultu) na 30 sekundi. Ovaj pristup ote\u017eat \u0107e realizaciju planova napada\u010dima, iako \u0107e imati neki negativan u\u010dinak na performanse. Osim toga, treba razumjeti da \u0107e ranjivost BEAST uskoro sama po sebi postati stvar pro\u0161losti \u2014 od 2020. godine najve\u0107i web preglednici <noindex><a rel=\"nofollow\" href=\"https:\/\/www.bleepingcomputer.com\/news\/security\/tls-10-and-tls-11-being-retired-in-2020-by-all-major-browsers\/\">prekidaju<\/a><\/noindex> podr\u0161ku za TLS 1.0 i 1.1. U svakom slu\u010daju, s ovim protokolima radi manje od 1,5% svih korisnika preglednika.<\/p>\n<h2>DROWN<\/h2>\n<p>\nOvo je napad preko protokola, koji koristi gre\u0161ke u implementaciji SSLv2 sa 40-bitnim RSA klju\u010devima. Napada\u010d prislu\u0161kuje stotine TLS-veza cilja i \u0161alje posebne pakete serveru sa SSLv2, koji koristi isti privatni klju\u010d. Koriste\u0107i <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/Adaptive_chosen-ciphertext_attack\">Bleichenbacherov napad<\/a><\/noindex>, haker mo\u017ee de\u0161ifrirati jednu od pribli\u017eno hiljadu TLS sesija klijenta.<\/p>\n<p>O DROWN-u se prvi put saznalo 2016. godine \u2014 tada je njome bila <noindex><a rel=\"nofollow\" href=\"https:\/\/www.acunetix.com\/blog\/articles\/tls-vulnerabilities-attacks-final-part\/\">podlo\u017ena tre\u0107ina servera<\/a><\/noindex> u svijetu. Danas nije izgubila na relevantnosti. Od 150 hiljada najpopularnijih sajtova, 2% i dalje <noindex><a rel=\"nofollow\" href=\"https:\/\/www.ssllabs.com\/ssl-pulse\/\">podr\u017eavaju<\/a><\/noindex> koristi SSLv2 i ranjive mehanizme \u0161ifriranja.<\/p>\n<p><b>Kako se za\u0161tititi.<\/b> Potreban je instalirati zakrpe koje su predlo\u017eili developeri kriptografskih biblioteka, koje isklju\u010duju podr\u0161ku za SSLv2. Na primjer, dvije takve zakrpe su predstavljene za OpenSSL (2016. godine <noindex><a rel=\"nofollow\" href=\"https:\/\/drownattack.com\/#mitigation\">to su bila a\u017euriranja<\/a><\/noindex> 1.0.1s i 1.0.2g). Tako\u0111e su objavljena a\u017euriranja i upute za isklju\u010divanje ranjivog protokola u <noindex><a rel=\"nofollow\" href=\"https:\/\/access.redhat.com\/security\/vulnerabilities\/drown\">Red Hat<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/httpd.apache.org\/docs\/2.2\/mod\/mod_ssl.html#sslprotocol\">Apache<\/a><\/noindex>, <noindex><a rel=\"nofollow\" href=\"https:\/\/security-tracker.debian.org\/tracker\/CVE-2016-0800\">Debian<\/a><\/noindex>.<\/p>\n<blockquote><p><i>\"Resurs mo\u017ee biti ranjiv za DROWN, ako njegove klju\u010deve koristi strani server sa SSLv2, kao \u0161to je po\u0161tanski server,\" isti\u010de \u0161ef odjela za razvoj <noindex><a rel=\"nofollow\" href=\"https:\/\/1cloud.ru\/?utm_source=habrahabr&amp;utm_medium=cpm&amp;utm_campaign=https&amp;utm_content=site\">IaaS-provajdera 1cloud.ru<\/a><\/noindex> Sergej Belkin. \u2014 Ova situacija nastaje kada nekoliko servera koristi zajedni\u010dki SSL certifikat. U tom slu\u010daju, podr\u0161ka za SSLv2 treba biti onemogu\u0107ena na svim ure\u0111ajima.<\/i><\/p><\/blockquote>\n<p>\nMo\u017eete provjeriti je li potrebno a\u017eurirati svoj sustav pomo\u0107u posebnog <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/nimia\/public_drown_scanner\">alata<\/a><\/noindex> \u2014 razvili su ga stru\u010dnjaci za informati\u010dku sigurnost koji su otkrili DROWN. Vi\u0161e preporuka vezanih uz za\u0161titu od ovog tipa napada mo\u017eete pro\u010ditati u <noindex><a rel=\"nofollow\" href=\"https:\/\/www.openssl.org\/blog\/blog\/2016\/03\/01\/an-openssl-users-guide-to-drown\/\">postu na web stranici OpenSSL<\/a><\/noindex>.<\/p>\n<h2>Heartbleed<\/h2>\n<p>\nJedna od najve\u0107ih ranjivosti u softveru \u2014 <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/Heartbleed\">Heartbleed<\/a><\/noindex>. Otkrivena je 2014. godine u OpenSSL biblioteci. U trenutku objave gre\u0161ke, broj ranjivih web stranica <noindex><a rel=\"nofollow\" href=\"https:\/\/news.netcraft.com\/archives\/2014\/04\/08\/half-a-million-widely-trusted-websites-vulnerable-to-heartbleed-bug.html\">procjenjivao se na pola milijuna<\/a><\/noindex> \u2014 to je otprilike 17% za\u0161ti\u0107enih resursa na mre\u017ei.<\/p>\n<p>Napad se realizira putem malog modula Heartbeat ekstenzije TLS. TLS protokol zahtijeva da se podaci prenose neprekidno. U slu\u010daju dugotrajne neaktivnosti dolazi do prekida i ponovno se mora uspostaviti veza. Kako bi se nosili s ovim problemom, serveri i klijenti umjetno \"\u0161ume\" kanal (<noindex><a rel=\"nofollow\" href=\"https:\/\/tools.ietf.org\/html\/rfc6520\">RFC 6520, str.5<\/a><\/noindex>), \u0161alju\u0107i paket nasumi\u010dne du\u017eine. Ako je bio ve\u0107i od maksimalnog paketa, ranjive verzije OpenSSL-a \u010ditale su memoriju izvan dodijeljenog bafera. U ovom podru\u010dju mogli su se nalaziti bilo kakvi podaci, uklju\u010duju\u0107i tajne klju\u010deve \u0161ifriranja i informacije o drugim vezama.<\/p>\n<p>Ranjivost je bila prisutna u svim verzijama biblioteke izme\u0111u 1.0.1 i 1.0.1f uklju\u010divo, kao i u nekoliko operativnih sustava \u2014 Ubuntu do 12.04.4, CentOS stariji od 6.5, OpenBSD 5.3 i drugih. Potpuni popis dostupan je <noindex><a rel=\"nofollow\" href=\"http:\/\/heartbleed.com\/\">na stranici posve\u0107enoj Heartbleed<\/a><\/noindex>. Iako su zakrpe protiv ove ranjivosti objavljene gotovo odmah nakon njenog otkri\u0107a, problem ostaje aktualan i danas. \u010cak i 2017. godine <noindex><a rel=\"nofollow\" href=\"https:\/\/thehackernews.com\/2017\/01\/heartbleed-openssl-vulnerability.html\">radilo je gotovo 200 tisu\u0107a web stranica<\/a><\/noindex>, podlo\u017enih Heartbleed-u.<\/p>\n<p><b>Kako se za\u0161tititi.<\/b> Potrebno je <noindex><a rel=\"nofollow\" href=\"https:\/\/www.openssl.org\/source\/\">a\u017eurirati OpenSSL<\/a><\/noindex> na verziju 1.0.1g ili noviju. Tako\u0111er, mo\u017eete ru\u010dno onemogu\u0107iti Heartbeat zahtjeve pomo\u0107u opcije DOPENSSL_NO_HEARTBEATS. Nakon a\u017euriranja stru\u010dnjaci za informati\u010dku sigurnost <noindex><a rel=\"nofollow\" href=\"https:\/\/thehackernews.com\/2017\/01\/heartbleed-openssl-vulnerability.html\">preporu\u010duju<\/a><\/noindex> ponovno izdaju SSL certifikate. Zamjena je potrebna u slu\u010daju da su podaci o klju\u010devima \u0161ifriranja ipak dospjeli do hakera.<\/p>\n<h2>Zamjena certifikata<\/h2>\n<p>\nIzme\u0111u korisnika i servera uspostavlja se kontrolirana to\u010dka s legitimnim SSL certifikatom koja aktivno presre\u0107e promet. Ova to\u010dka se pretvara da je legitimni server, prikazuju\u0107i valjani certifikat, i pru\u017ea mogu\u0107nost provo\u0111enja MITM napada.<\/p>\n<p>Prema <noindex><a rel=\"nofollow\" href=\"https:\/\/jhalderm.com\/pub\/papers\/interception-ndss17.pdf\">istra\u017eivanju<\/a><\/noindex> Prema istra\u017eivanju kompanija Mozilla, Google i nekoliko univerziteta, otprilike 11% za\u0161ti\u0107enih veza na mre\u017ei je \"prislu\u0161kivano\". Ovo je rezultat instalacije sumnjivih korenskih sertifikata na ra\u010dunarima korisnika.<\/p>\n<p><b>Kako se za\u0161tititi.<\/b> Kori\u0161\u0107enje usluga pouzdanih <noindex><a rel=\"nofollow\" href=\"https:\/\/1cloud.ru\/services\/ssl?utm_source=habrahabr&amp;utm_medium=cpm&amp;utm_campaign=https&amp;utm_content=site\">SSL provajdera<\/a><\/noindex>. \"Kvalitet\" sertifikata mo\u017ee se proveriti pomo\u0107u servisa <noindex><a rel=\"nofollow\" href=\"https:\/\/www.certificate-transparency.org\/\">Certificate Transparency<\/a><\/noindex> (CT). U otkrivanju \"prislu\u0161kivanja\" mogu pomo\u0107i i cloud provajderi \u2014 ve\u0107 danas neka velika preduze\u0107a nude specijalizovane alate za monitoring TLS konekcija.<\/p>\n<p>Drugi na\u010din za\u0161tite bi\u0107e novi <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/1cloud\/blog\/444986\/\">standard.<\/a><\/noindex> ACME, koji automatizuje dobijanje SSL sertifikata. Pri tom \u0107e dodati dodatne mehanizme za provere vlasnika sajta. Vi\u0161e o njemu <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/1cloud\/blog\/444986\/\">pisali smo u jednom od na\u0161ih prethodnih materijala<\/a><\/noindex>.<\/p>\n<p><img decoding=\"async\" alt=\"Potencijalni napadi na HTTPS i kako se za\u0161tititi od njih\" src=\"\/wp-content\/uploads\/2019\/04\/0ce792d1ebce9077460ebd02518e01ac.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>\/ Flickr \/ <noindex><a rel=\"nofollow\" href=\"https:\/\/www.flickr.com\/photos\/yusamoilov\/13334048894\/\">Yuri Samoilov<\/a><\/noindex> \/ CC BY<\/i><\/p>\n<h2>Perspektive HTTPS<\/h2>\n<p>\nUprkos brojnim ranjivostima, IT giganti i stru\u010dnjaci za bezbednost veruju u budu\u0107nost ovog protokola. Za aktivnu implementaciju HTTPS <noindex><a rel=\"nofollow\" href=\"https:\/\/www.w3.org\/DesignIssues\/Security-NotTheS.html\">zala\u017ee se<\/a><\/noindex> kreator WWW Tim Berners-Lee. Prema njegovim re\u010dima, vremenom \u0107e TLS postajati sve sigurniji, \u0161to \u0107e zna\u010dajno pove\u0107ati bezbednost konekcija. Berners-Lee je \u010dak pretpostavio da \u0107e u <noindex><a rel=\"nofollow\" href=\"https:\/\/www.w3.org\/DesignIssues\/Security-ClientCerts.html\">budu\u0107nosti postojati<\/a><\/noindex> klijentski sertifikati za autentifikaciju identiteta. Oni \u0107e pomo\u0107i u pobolj\u0161anju za\u0161tite servera od napada\u010da.<\/p>\n<p>Razvijanje tehnologije SSL\/TLS tako\u0111e se planira putem ma\u0161inskog u\u010denja \u2014 pametni algoritmi \u0107e odgovarati za filtriranje zlonamernog saobra\u0107aja. U HTTPS konekcijama administratori nemaju mogu\u0107nost da saznaju sadr\u017eaj \u0161ifrovanih poruka \u2014 uklju\u010duju\u0107i otkrivanje zahteva od zlonamernog softvera. Ve\u0107 danas neuronske mre\u017ee mogu da filtriraju potencijalno opasne pakete sa precizno\u0161\u0107u od 90%. (<noindex><a rel=\"nofollow\" href=\"https:\/\/2018.bsidesbud.com\/wp-content\/uploads\/2018\/03\/seba_garcia_frantisek_strasak.pdf?forcedefault=true\">slajd 23 prezentacije<\/a><\/noindex>).<\/p>\n<h2>Zaklju\u010dci<\/h2>\n<p>\nNapadi na HTTPS ve\u0107inom nisu povezani sa problemima u samom protokolu, ve\u0107 sa podr\u0161kom zastarelih mehanizama \u0161ifrovanja. IT industrija postepeno po\u010dinje da se odri\u010de protokola prethodne generacije i nudi nove alate za otkrivanje ranjivosti. U budu\u0107nosti \u0107e ovi alati postajati sve pametniji.<\/p>\n<h5>Dodatne veze na temu:<\/h5>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/1cloud\/blog\/448760\/\"> Razvoj u oblaku, bezbednost i li\u010dni podaci: sa\u017eetak od 1cloud<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habrahabr.ru\/company\/1cloud\/blog\/315758\/\">SSL sa\u017eetak: Najbolji prakti\u010dni materijali na Habru i ne samo<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habrahabr.ru\/company\/1cloud\/blog\/316266\/\">VPN sa\u017eetak: Uvodna \u0161tiva na Habru i ne samo<\/a><\/noindex><\/li>\n<\/ul>\n<p>Izvor: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/1cloud\/blog\/449866\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u043e\u043b\u043e\u0432\u0438\u043d\u0430 \u0441\u0430\u0439\u0442\u043e\u0432 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442 HTTPS, \u0438 \u0438\u0445 \u0447\u0438\u0441\u043b\u043e \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u043e \u0443\u0432\u0435\u043b\u0438\u0447\u0438\u0432\u0430\u0435\u0442\u0441\u044f. \u041f\u0440\u043e\u0442\u043e\u043a\u043e\u043b \u0441\u043e\u043a\u0440\u0430\u0449\u0430\u0435\u0442 \u0440\u0438\u0441\u043a \u043f\u0435\u0440\u0435\u0445\u0432\u0430\u0442\u0430 \u0442\u0440\u0430\u0444\u0438\u043a\u0430, \u043d\u043e \u043d\u0435 \u0438\u0441\u043a\u043b\u044e\u0447\u0430\u0435\u0442 \u043f\u043e\u043f\u044b\u0442\u043a\u0438 \u0430\u0442\u0430\u043a \u043a\u0430\u043a \u0442\u0430\u043a\u043e\u0432\u044b\u0435. \u041e \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0445 \u0438\u0445 \u043d\u0438\u0445 \u2014 POODLE, BEAST, DROWN \u0438 \u0434\u0440\u0443\u0433\u0438\u0445 \u2014 \u0438 \u0441\u043f\u043e\u0441\u043e\u0431\u0430\u0445 \u0437\u0430\u0449\u0438\u0442\u044b, \u043c\u044b \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0435\u043c \u0432 \u043d\u0430\u0448\u0435\u043c \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u0435. \/ Flickr \/ Sven Graeme \/ CC BY-SA POODLE \u0412\u043f\u0435\u0440\u0432\u044b\u0435 \u043e\u0431 \u0430\u0442\u0430\u043a\u0435 POODLE \u0441\u0442\u0430\u043b\u043e \u0438\u0437\u0432\u0435\u0441\u0442\u043d\u043e [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":24394,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-32603","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.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u043e\u043b\u043e\u0432\u0438\u043d\u0430 \u0441\u0430\u0439\u0442\u043e\u0432 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442 HTTPS, \u0438 \u0438\u0445 \u0447\u0438\u0441\u043b\u043e \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\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\/bs\/blog\/administrirovanie\/potentsialnye-ataki-na-https-i-kak-ot-nih-zashhititsya\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"bs_BA\" \/>\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\u043e\u0442\u0435\u043d\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0435 \u0430\u0442\u0430\u043a\u0438 \u043d\u0430 HTTPS \u0438 \u043a\u0430\u043a \u043e\u0442 \u043d\u0438\u0445 \u0437\u0430\u0449\u0438\u0442\u0438\u0442\u044c\u0441\u044f | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u043e\u043b\u043e\u0432\u0438\u043d\u0430 \u0441\u0430\u0439\u0442\u043e\u0432 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442 HTTPS, \u0438 \u0438\u0445 \u0447\u0438\u0441\u043b\u043e \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u043e.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/potentsialnye-ataki-na-https-i-kak-ot-nih-zashhititsya\" \/>\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=\"2019-10-31T18:47:55+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:47:55+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\udd47Potencijalni napadi na HTTPS i kako se za\u0161tititi od njih | ProHoster","description":"Polovina sajtova koristi HTTPS, a njihov broj konstantno raste.","canonical_url":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/potentsialnye-ataki-na-https-i-kak-ot-nih-zashhititsya","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"bs_BA","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\u043e\u0442\u0435\u043d\u0446\u0438\u0430\u043b\u044c\u043d\u044b\u0435 \u0430\u0442\u0430\u043a\u0438 \u043d\u0430 HTTPS \u0438 \u043a\u0430\u043a \u043e\u0442 \u043d\u0438\u0445 \u0437\u0430\u0449\u0438\u0442\u0438\u0442\u044c\u0441\u044f | ProHoster","og:description":"\u041f\u043e\u043b\u043e\u0432\u0438\u043d\u0430 \u0441\u0430\u0439\u0442\u043e\u0432 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442 HTTPS, \u0438 \u0438\u0445 \u0447\u0438\u0441\u043b\u043e \u0441\u0442\u0430\u0431\u0438\u043b\u044c\u043d\u043e.","og:url":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/potentsialnye-ataki-na-https-i-kak-ot-nih-zashhititsya","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":"2019-10-31T18:47:55+00:00","article:modified_time":"2019-10-31T18:47:55+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"32603","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":"2026-01-21 11:43:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:55:24","updated":"2026-01-21 11:43:20","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts\/32603","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/comments?post=32603"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts\/32603\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/media\/24394"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/media?parent=32603"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/categories?post=32603"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/tags?post=32603"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}