{"id":97349,"date":"2020-10-17T14:42:14","date_gmt":"2020-10-17T12:42:14","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/minimizacziya-riskov-ispolzovaniya-dns-over-tls-dot-i-dns-over-https-doh"},"modified":"2020-10-17T14:42:14","modified_gmt":"2020-10-17T12:42:14","slug":"minimizacziya-riskov-ispolzovaniya-dns-over-tls-dot-i-dns-over-https-doh","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/minimizacziya-riskov-ispolzovaniya-dns-over-tls-dot-i-dns-over-https-doh","title":{"rendered":"Minimizimi i rreziqeve t\u00eb p\u00ebrdorimit t\u00eb DNS-over-TLS (DoT) dhe DNS-over-HTTPS (DoH)","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"MinimizimiMinimizimi i rreziqeve t\u00eb p\u00ebrdorimit t\u00eb DoH dhe DoT<\/p>\n

Mbrojtja ndaj DoH dhe DoT<\/h2>\n

A kontrolloni trafikun tuaj DNS? Organizatat investojn\u00eb shum\u00eb koh\u00eb, para dhe p\u00ebrpjekje p\u00ebr t\u00eb siguruar rrjetet e tyre. Megjithat\u00eb, nj\u00eb nga fushat q\u00eb shpesh nuk merr v\u00ebmendjen e duhur \u00ebsht\u00eb DNS. <\/p>\n

Nj\u00eb p\u00ebrmbledhje e mir\u00eb e rreziqeve q\u00eb sjell DNS \u00ebsht\u00eb prezantimi i Verisign<\/a><\/noindex> n\u00eb konferenc\u00ebn Infosecurity. <\/p>\n

\"Minimizimi31% e klasave t\u00eb studiuara t\u00eb programeve t\u00eb k\u00ebrkesave kan\u00eb p\u00ebrdorur DNS p\u00ebr exchange \u00e7elesh. Konkluzionet e studimit<\/p>\n

31% e klasave t\u00eb studiuara t\u00eb programeve t\u00eb k\u00ebrkesave kan\u00eb p\u00ebrdorur DNS p\u00ebr exchange \u00e7elesh.<\/p>\n

Problemi \u00ebsht\u00eb serioz. Sipas laboratorit hulumtues Palo Alto Networks Unit 42, rreth 85% e viruseve p\u00ebrdorin DNS p\u00ebr t\u00eb vendosur nj\u00eb kanal operimi dhe kontrolli, duke lejuar keqb\u00ebr\u00ebsit t\u00eb fusin leht\u00ebsisht malware n\u00eb rrjetin tuaj dhe t\u00eb vjedhin t\u00eb dh\u00ebna. Q\u00eb nga krijimi i tij, trafiku DNS ka qen\u00eb kryesisht i paenkriptuar dhe leht\u00eb mund t\u00eb analizohej nga mekanizmat e siguris\u00eb NGFW. <\/p>\n

\u041f\u043e\u044f\u0432\u0438\u043b\u0438\u0441\u044c \u043d\u043e\u0432\u044b\u0435 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u044b \u0434\u043b\u044f DNS, \u043d\u0430\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u043d\u044b\u0435 \u043d\u0430 \u043f\u043e\u0432\u044b\u0448\u0435\u043d\u0438\u0435 \u043a\u043e\u043d\u0444\u0438\u0434\u0435\u043d\u0446\u0438\u0430\u043b\u044c\u043d\u043e\u0441\u0442\u0438 DNS \u0441\u043e\u0435\u0434\u0438\u043d\u0435\u043d\u0438\u0439. \u041e\u043d\u0438 \u0430\u043a\u0442\u0438\u0432\u043d\u043e \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u044e\u0442\u0441\u044f \u0432\u0435\u0434\u0443\u0449\u0438\u043c\u0438 \u043f\u043e\u0441\u0442\u0430\u0432\u0449\u0438\u043a\u0430\u043c\u0438 \u0431\u0440\u0430\u0443\u0437\u0435\u0440\u043e\u0432 \u0438 \u0434\u0440\u0443\u0433\u0438\u043c\u0438 \u043f\u043e\u0441\u0442\u0430\u0432\u0449\u0438\u043a\u0430\u043c\u0438 \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u043d\u043e\u0433\u043e \u043e\u0431\u0435\u0441\u043f\u0435\u0447\u0435\u043d\u0438\u044f. \u0421\u043a\u043e\u0440\u043e \u0432 \u043a\u043e\u0440\u043f\u043e\u0440\u0430\u0442\u0438\u0432\u043d\u044b\u0445 \u0441\u0435\u0442\u044f\u0445 \u043d\u0430\u0447\u043d\u0435\u0442\u0441\u044f \u0440\u043e\u0441\u0442 \u0437\u0430\u0448\u0438\u0444\u0440\u043e\u0432\u0430\u043d\u043d\u043e\u0433\u043e DNS-\u0442\u0440\u0430\u0444\u0438\u043a\u0430. \u0417\u0430\u0448\u0438\u0444\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0439 \u0442\u0440\u0430\u0444\u0438\u043a DNS, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043d\u0435 \u0430\u043d\u0430\u043b\u0438\u0437\u0438\u0440\u0443\u0435\u0442\u0441\u044f \u0441\u0440\u0435\u0434\u0441\u0442\u0432\u0430\u043c\u0438 \u0434\u043e\u043b\u0436\u043d\u044b\u043c \u043e\u0431\u0440\u0430\u0437\u043e\u043c \u0438 \u0440\u0430\u0437\u0440\u0435\u0448\u0435\u043d, \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442 \u0443\u0433\u0440\u043e\u0437\u0443 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0434\u043b\u044f \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u0442\u0430\u043a\u043e\u0439 \u0443\u0433\u0440\u043e\u0437\u043e\u0439 \u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u043a\u0440\u0438\u043f\u0442\u043e\u043b\u043e\u043a\u0435\u0440\u044b, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0442 DNS \u0434\u043b\u044f \u043e\u0431\u043c\u0435\u043d\u0430 \u043a\u043b\u044e\u0447\u0430\u043c\u0438 \u0448\u0438\u0444\u0440\u043e\u0432\u0430\u043d\u0438\u044f. \u0410\u0442\u0430\u043a\u0443\u044e\u0449\u0438\u0435 \u0441\u0435\u0439\u0447\u0430\u0441 \u0442\u0440\u0435\u0431\u0443\u044e\u0442 \u0432\u044b\u043a\u0443\u043f \u0432 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043c\u0438\u043b\u043b\u0438\u043e\u043d\u043e\u0432 \u0434\u043e\u043b\u043b\u0430\u0440\u043e\u0432 \u0437\u0430 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0434\u043e\u0441\u0442\u0443\u043f\u0430 \u043a \u0432\u0430\u0448\u0438\u043c \u0434\u0430\u043d\u043d\u044b\u043c. \u0412 \u043a\u043e\u043c\u043f\u0430\u043d\u0438\u0438 Garmin, \u043d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u0437\u0430\u043f\u043b\u0430\u0442\u0438\u043b\u0438 10 \u043c\u0438\u043b\u043b\u0438\u043e\u043d\u043e\u0432 \u0434\u043e\u043b\u043b\u0430\u0440\u043e\u0432.<\/p>\n

Me konfigurimin e duhur, NGFW mund t\u00eb ndalojn\u00eb ose mbrojn\u00eb p\u00ebrdorimin e DNS-over-TLS (DoT) dhe mund t\u00eb p\u00ebrdoren p\u00ebr t\u00eb ndaluar DNS-over-HTTPS (DoH), duke lejuar q\u00eb t\u00eb analizohet e gjith\u00eb trafiku DNS n\u00eb rrjetin tuaj.<\/p>\n

\u00c7far\u00eb \u00ebsht\u00eb DNS e enkriptuar?<\/h2>\n

\u00c7far\u00eb \u00ebsht\u00eb DNS<\/p>\n

Sistema i emrave t\u00eb domain-it (DNS) t\u00eb transformon emrat e domain-eve q\u00eb jan\u00eb t\u00eb leht\u00eb p\u00ebr t'u lexuar (p.sh., adresa www.paloaltonetworks.com<\/a><\/noindex> ) n\u00eb IP-n\u00eb (p\u00ebr shembull, n\u00eb 34.107.151.202). Kur nj\u00eb p\u00ebrdorues shkruan nj\u00eb em\u00ebr domain n\u00eb shfletuesin e uebit, shfletuesi d\u00ebrgon nj\u00eb k\u00ebrkes\u00eb DNS n\u00eb serverin DNS, duke k\u00ebrkuar IP-n\u00eb e lidhur me k\u00ebt\u00eb em\u00ebr domain. N\u00eb p\u00ebrgjigje, serveri DNS kthen IP-n\u00eb q\u00eb do t\u00eb p\u00ebrdor\u00eb ky shfletues.<\/p>\n

K\u00ebrkesat dhe p\u00ebrgjigjet DNS d\u00ebrgohen n\u00ebp\u00ebr rrjet n\u00eb form\u00ebn e tekstit t\u00eb zakonsh\u00ebm n\u00eb shkruar t\u00eb hapur, gj\u00eb q\u00eb e b\u00ebn at\u00eb t\u00eb ndjesh\u00ebm ndaj spiunazhit ose modifikimit t\u00eb p\u00ebrgjigjeve dhe ridrejtimit t\u00eb shfletuesit n\u00eb servera t\u00eb d\u00ebmsh\u00ebm. Kriptimi i DNS e b\u00ebn m\u00eb t\u00eb v\u00ebshtir\u00eb ndjekjen e k\u00ebrkesave DNS ose modifikimin e tyre gjat\u00eb transferimit. Kriptimi i k\u00ebrkesave dhe p\u00ebrgjigjeve DNS ju mbron nga sulmet Man-in-the-Middle, duke kryer gjithashtu funksionet e nj\u00eb protokolli tradicional DNS (sistemi i emrave t\u00eb domain-eve) me tekst t\u00eb hapur. <\/p>\n

N\u00eb vitet e fundit jan\u00eb zbatuar dy protokolle kriptimi DNS:<\/p>\n

    \n
  1. \n

    DNS-over-HTTPS (DoH)<\/p>\n<\/li>\n

  2. \n

    DNS-over-TLS (DoT) <\/p>\n<\/li>\n<\/ol>\n

    \u042d\u0442\u0438 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u044b \u0438\u043c\u0435\u044e\u0442 \u043e\u0434\u043d\u0443 \u043e\u0431\u0449\u0443\u044e \u0447\u0435\u0440\u0442\u0443: \u043d\u0430\u043c\u0435\u0440\u0435\u043d\u043d\u043e \u043f\u0440\u044f\u0447\u0443\u0442 DNS-\u0437\u0430\u043f\u0440\u043e\u0441\u044b \u043e\u0442 \u043b\u044e\u0431\u043e\u0433\u043e \u043f\u0435\u0440\u0435\u0445\u0432\u0430\u0442\u0430… \u0438 \u043e\u0442 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u0438\u043a\u043e\u0432 \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0438 \u0432 \u0442\u043e\u043c \u0447\u0438\u0441\u043b\u0435. \u041f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u044b \u0432 \u043e\u0441\u043d\u043e\u0432\u043d\u043e\u043c \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0442 \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b TLS (Transport Layer Security) \u0434\u043b\u044f \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f \u0437\u0430\u0448\u0438\u0444\u0440\u043e\u0432\u0430\u043d\u043d\u043e\u0433\u043e \u0441\u043e\u0435\u0434\u0438\u043d\u0435\u043d\u0438\u044f \u043c\u0435\u0436\u0434\u0443 \u043a\u043b\u0438\u0435\u043d\u0442\u043e\u043c, \u0432\u044b\u043f\u043e\u043b\u043d\u044f\u044e\u0449\u0438\u043c \u0437\u0430\u043f\u0440\u043e\u0441\u044b, \u0438 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u043c, \u0440\u0430\u0437\u0440\u0435\u0448\u0430\u044e\u0449\u0438\u043c \u0437\u0430\u043f\u0440\u043e\u0441\u044b DNS, \u0447\u0435\u0440\u0435\u0437 \u043f\u043e\u0440\u0442, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u043e\u0431\u044b\u0447\u043d\u043e \u043d\u0435 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u0434\u043b\u044f \u0442\u0440\u0430\u0444\u0438\u043a\u0430 DNS.<\/p>\n

    Privat\u00ebsia e k\u00ebrkesave DNS \u00ebsht\u00eb nj\u00eb avantazh i madh i k\u00ebtyre protokolleve. Megjithat\u00eb, ato krijojn\u00eb probleme p\u00ebr sigurin\u00eb, e cila duhet t\u00eb monitoroj\u00eb trafikun rrjetor dhe t\u00eb zbuloj\u00eb dhe bllokoj\u00eb lidhjet e d\u00ebmshme. Duke qen\u00eb se protokollet ndryshojn\u00eb n\u00eb implementimin e tyre, metodat e analiz\u00ebs do t\u00eb jen\u00eb t\u00eb ndryshme p\u00ebr DoH dhe DoT.<\/p>\n

    DNS over HTTPS (DoH)<\/h2>\n

    \"MinimizimiDNS brenda HTTPS<\/p>\n

    DoH p\u00ebrdor portin e njohur 443 p\u00ebr HTTPS, p\u00ebr t\u00eb cilin n\u00eb RFC \u00ebsht\u00eb specifikuar qart\u00eb se q\u00ebllimi \u00ebsht\u00eb \"t\u00eb p\u00ebrzihet trafiku DoH me trafikun tjet\u00ebr HTTPS n\u00eb t\u00eb nj\u00ebjt\u00ebn lidhje\", \"t\u00eb v\u00ebshtir\u00ebsohet analiza e trafikut DNS\" dhe, k\u00ebshtu, t\u00eb kalohen masat e kontrollit korporativ ( RFC 8484 DoH, seksioni 8.1<\/a><\/noindex> ). Protocoli DoH p\u00ebrdor enkriptimin TLS dhe sintaks\u00ebn e k\u00ebrkesave, t\u00eb ofruara nga standardet e zakonshme HTTPS dhe HTTP\/2, duke shtuar k\u00ebrkesat dhe p\u00ebrgjigjet DNS mbi k\u00ebrkesat standarde HTTP.<\/p>\n

    Rreziqet e lidhura me DoH<\/h2>\n

    N\u00ebse nuk mund t\u00eb dalloni trafikun normal HTTPS nga k\u00ebrkesat DoH, aplikacionet brenda organizat\u00ebs tuaj mund (dhe do t\u00eb) anashkalojn\u00eb konfigurimet lokale DNS, duke redirektuar k\u00ebrkesat n\u00eb servera t\u00eb tret\u00eb q\u00eb p\u00ebrgjigjen p\u00ebr k\u00ebrkesat DoH, duke anashkaluar \u00e7do mbik\u00ebqyrje, q\u00eb do t\u00eb thot\u00eb se shkat\u00ebrron mund\u00ebsin\u00eb e kontrollit mbi trafikun DNS. Idealisht, ju duhet t\u00eb kontrolloni DoH duke p\u00ebrdorur funksionet e dekriptimt HTTPS. <\/p>\n

    DHE Google dhe Mozilla kan\u00eb realizuar mund\u00ebsit\u00eb DoH<\/a><\/noindex> n\u00eb versionet e fundit t\u00eb shfletuesve t\u00eb tyre, dhe t\u00eb dy kompanit\u00eb punojn\u00eb p\u00ebr p\u00ebrdorimin e DoH si parazgjedhje p\u00ebr t\u00eb gjitha k\u00ebrkesat DNS. Microsoft gjithashtu \u00ebsht\u00eb duke zhvilluar plane<\/a><\/noindex> p\u00ebr integrimin e DoH n\u00eb sistemet e veta operative. Nj\u00eb minus \u00ebsht\u00eb se jo vet\u00ebm kompanit\u00eb e respektuara t\u00eb zhvillimit t\u00eb softuerit, por edhe kriminel\u00ebt filluan t\u00eb p\u00ebrdorin DoH si nj\u00eb mjet p\u00ebr t\u00eb anashkaluar masat tradicionale t\u00eb mbrojtjes s\u00eb rrjetit t\u00eb kompanis\u00eb. ( P\u00ebr shembull, shikoni artikujt e m\u00ebposht\u00ebm: PsiXBot tani p\u00ebrdor Google DoH<\/a><\/noindex> , PsiXBot poqon t\u00eb zhvillohet me infrastruktur\u00eb t\u00eb rinovuar DNS<\/a><\/noindex> dhe analiza e backdoor-it Godlua<\/a><\/noindex> .) N\u00eb \u00e7do rast, si trafiku i mir\u00eb ashtu edhe ai keqdash\u00ebs DoH do t\u00eb mbeten t\u00eb paduksh\u00ebm, duke l\u00ebn\u00eb organizat\u00ebn t\u00eb verb\u00ebr ndaj p\u00ebrdorimit t\u00eb keq t\u00eb DoH si nj\u00eb kanal p\u00ebr menaxhimin e malware (C2) dhe vjedhjen e t\u00eb dh\u00ebnave t\u00eb ndjeshme.<\/p>\n

    Sigurimi i dukshm\u00ebris\u00eb dhe kontrollit t\u00eb trafikut DoH<\/h2>\n

    Si zgjidhja m\u00eb e mir\u00eb p\u00ebr t\u00eb kontrolluar DoH, ne rekomandojm\u00eb t\u00eb konfiguroni n\u00eb NGFW dekriptimin e trafikut HTTPS dhe bllokimin e trafikut DoH (emri i aplikacionit: dns-over-https). <\/p>\n

    S\u00eb pari, sigurohuni q\u00eb NGFW t\u00eb jet\u00eb i konfiguruar p\u00ebr dekriptimin e HTTPS, sipas udh\u00ebzimeve p\u00ebr praktikat m\u00eb t\u00eb mira t\u00eb dekriptimit<\/a><\/noindex>.<\/p>\n

    S\u00eb dyti, krijoni nj\u00eb rregull p\u00ebr trafikun e aplikacionit \u201cdns-over-https\u201d, si\u00e7 \u00ebsht\u00eb treguar m\u00eb posht\u00eb:<\/p>\n

    \"MinimizimiRregulli i NGFW t\u00eb Palo Alto Networks p\u00ebr bllokimin e DNS-over-HTTPS<\/p>\n

    Si sihtezoni si alternative te nd\u00ebrmjetme (n\u00ebse organizata juaj nuk e ka zbatuar plot\u00ebsisht dekriptimin HTTPS), NDGFW mund t\u00eb konfigurohet p\u00ebr t\u00eb aplikuar veprimin \"ndalo\" n\u00eb identifikuesin e aplikacionit \"dns-over-https\", por efekti do t\u00eb jet\u00eb i kufizuar n\u00eb bllokimin e disa server\u00ebve t\u00eb njohur t\u00eb DoH sipas emrit t\u00eb tyre t\u00eb domainit, pasi pa dekriptimin e HTTPS, trafiku DoH nuk mund t\u00eb verifikohet plot\u00ebsisht (shih.  Applipedia nga Palo Alto Networks<\/a><\/noindex>   dhe k\u00ebrkoni p\u00ebr fraz\u00ebn \"dns-over-https\").<\/p>\n

    DNS mbi TLS (DoT)<\/h2>\n

    \"MinimizimiDNS brenda TLS<\/p>\n

    Nd\u00ebrsa protokolli DoH synon t\u00eb p\u00ebrzihet me trafikun tjet\u00ebr n\u00eb t\u00eb nj\u00ebjtin port, DoT, nga ana tjet\u00ebr, n\u00eb m\u00ebnyr\u00eb default e p\u00ebrdor nj\u00eb port t\u00eb ve\u00e7ant\u00eb, t\u00eb rezervuar p\u00ebr k\u00ebt\u00eb q\u00ebllim t\u00eb vet\u00ebm, duke ndaluar madje p\u00ebrdorimin e t\u00eb nj\u00ebjtit port p\u00ebr trafikun tradicional t\u00eb p\u00ebrmbajtur DNS ( RFC 7858, Seksioni 3.1<\/a><\/noindex> ).<\/p>\n

    Protokolli DoT p\u00ebrdor protokollin TLS p\u00ebr t\u00eb siguruar enkriptimin, duke inkapsuluar k\u00ebrkesat standarde t\u00eb protokollit DNS, me trafik q\u00eb p\u00ebrdor portin e njohur 853 ( RFC 7858, seksioni 6<\/a><\/noindex> ).  \u041f\u0440\u043e\u0442\u043e\u043a\u043e\u043b DoT \u0431\u044b\u043b \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0430\u043d, \u0447\u0442\u043e\u0431\u044b \u0443\u043f\u0440\u043e\u0441\u0442\u0438\u0442\u044c \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u044f\u043c \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u0430\u0442\u044c \u0442\u0440\u0430\u0444\u0438\u043a \u043f\u043e \u043f\u043e\u0440\u0442\u0443, \u043b\u0438\u0431\u043e \u0441\u043e\u0433\u043b\u0430\u0448\u0430\u0442\u044c\u0441\u044f \u043d\u0430 \u0435\u0433\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435, \u043d\u043e \u0432\u043a\u043b\u044e\u0447\u0438\u0442\u044c \u0440\u0430\u0441\u0448\u0438\u0444\u0440\u043e\u0432\u043a\u0443 \u043d\u0430 \u044d\u0442\u043e\u043c \u043f\u043e\u0440\u0442\u0443.<\/p>\n

    Rreziqet e lidhura me DoT<\/h2>\n

    Google ka implementuar DoT n\u00eb klientin e tij Android 9 Pie dhe versione m\u00eb t\u00eb vonshme<\/a><\/noindex> , me parametrin e automatik t\u00eb p\u00ebrdorimit t\u00eb DoT-s\u00eb t\u00eb aktivizuar nga default, n\u00ebse \u00ebsht\u00eb n\u00eb dispozicion. N\u00ebse keni vler\u00ebsuar rreziqet dhe jeni t\u00eb gatsh\u00ebm t\u00eb p\u00ebrdorni DoT n\u00eb nivel organizativ, at\u00ebher\u00eb administrator\u00ebt e rrjetit duhet t\u00eb lejojn\u00eb shprehimisht trafikun e daljes n\u00eb portin 853 p\u00ebrmes perimetrin e tyre p\u00ebr k\u00ebt\u00eb protokoll t\u00eb ri.<\/p>\n

    Sigurimi i dukshm\u00ebris\u00eb dhe kontrollit t\u00eb trafikut DoT<\/h2>\n

    Si praktik\u00ebn m\u00eb t\u00eb mir\u00eb p\u00ebr t\u00eb kontrolluar DoT, ne rekomandojm\u00eb \u00e7do alternativ\u00eb nga t\u00eb lartp\u00ebrmendurat, duke u bazuar n\u00eb nevojat e organizat\u00ebs tuaj:<\/p>\n