{"id":97639,"date":"2020-10-20T02:42:56","date_gmt":"2020-10-20T00:42:56","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/vsyo-chto-vy-hoteli-znat-o-bezopasnom-sbrose-parolej-chast-2"},"modified":"2020-10-20T02:42:56","modified_gmt":"2020-10-20T00:42:56","slug":"vsyo-chto-vy-hoteli-znat-o-bezopasnom-sbrose-parolej-chast-2","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/vsyo-chto-vy-hoteli-znat-o-bezopasnom-sbrose-parolej-chast-2","title":{"rendered":"Gjith\u00e7ka q\u00eb d\u00ebshironit t\u00eb dinit rreth riparimit t\u00eb sigurt t\u00eb fjal\u00ebkalimeve. Pjesa 2","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Autentifikimi i dyfisht\u00eb<\/h2>\n

\nGjith\u00e7ka q\u00eb keni lexuar n\u00eb pjes\u00ebs s\u00eb par\u00eb<\/a><\/noindex> ka t\u00eb b\u00ebj\u00eb me identifikimin n\u00eb baz\u00eb t\u00eb asaj q\u00eb dikush di<\/em><\/strong>. Ai e di adres\u00ebn e tij t\u00eb post\u00ebs elektronike, di si t\u00eb hyj\u00eb n\u00eb t\u00eb (dmth. e di fjal\u00ebkalimin e tij p\u00ebr post\u00ebn elektronike) dhe di p\u00ebrgjigjet e pyetjeve sekrete. <\/p>\n

\u00abDija\u00bb konsiderohet nj\u00eb faktor autentifikimi; dy faktor\u00ebt e tjer\u00eb t\u00eb zakonsh\u00ebm jan\u00eb ajo q\u00eb keni<\/em><\/strong>, p\u00ebr shembull, nj\u00eb pajisje fizike, dhe ajo q\u00eb jeni<\/em><\/strong>, p\u00ebr shembull, gishti i dor\u00ebs ose irisi i syrit.<\/p>\n

\"Gjith\u00e7ka
\n<\/a><\/noindex>
\nN\u00eb shumic\u00ebn e rasteve, kryerja e identifikimit biologjik \u00ebsht\u00eb e pamundur, ve\u00e7an\u00ebrisht kur flasim p\u00ebr sigurin\u00eb e aplikacioneve n\u00eb internet, prandaj n\u00eb autentifikimin me dy faktor\u00eb (two factor authentication, 2FA) zakonisht p\u00ebrdoret atributi i dyt\u00eb \u2014 \u00abajo q\u00eb keni\u00bb. Nj\u00eb nga opsionet e njohura t\u00eb k\u00ebtij faktori t\u00eb dyt\u00eb \u00ebsht\u00eb nj\u00eb token fizik, p\u00ebr shembull, RSA SecurID<\/a><\/noindex>:<\/p>\n

\"Gjith\u00e7ka
\nT\u00eb dh\u00ebnat fizike shpesh p\u00ebrdoren p\u00ebr autentifikim n\u00eb VPN-t\u00eb korporative dhe sh\u00ebrbimet financiare. P\u00ebr autentifikimin n\u00eb sh\u00ebrbim, duhet t\u00eb p\u00ebrdorni si fjal\u00ebkalimin ashtu edhe kodin n\u00eb token (i cili shpesh ndryshon) n\u00eb kombinim me PIN-in. Teoretikisht, p\u00ebr identifikimin, nj\u00eb sulmues duhet t\u00eb dij\u00eb fjal\u00ebkalimin, t\u00eb ket\u00eb tokenin dhe gjithashtu t\u00eb dij\u00eb PIN-in e tokenit. N\u00eb skenarin e rikthimit t\u00eb fjal\u00ebkalimit, vet\u00eb fjal\u00ebkalimi, \u00ebsht\u00eb e qart\u00eb, nuk dihet, megjithat\u00eb posedimi i tokenit mund t\u00eb p\u00ebrdoret p\u00ebr t\u00eb konfirmuar pron\u00ebsin\u00eb e llogaris\u00eb. Sigurisht, ashtu si n\u00eb \u00e7do implementim mbrojt\u00ebs, kjo nuk siguron \"mbrojtje nga budallenjt\u00eb\"<\/a><\/noindex>, por padyshim rrit barrier\u00ebn p\u00ebr hyrjen.<\/p>\n

Nj\u00eb nga problemet kryesore t\u00eb k\u00ebtij qasje \u00ebsht\u00eb kostoja dhe logjistika e zbatimit; po flasim p\u00ebr transferimin e pajisjeve fizike te \u00e7do klient dhe p\u00ebr t\u00eb m\u00ebsuar ata me procesin e ri. P\u00ebr m\u00eb tep\u00ebr, p\u00ebrdoruesit duhet t\u00eb ken\u00eb nj\u00eb pajisje me vete, gj\u00eb q\u00eb n\u00eb rastin e nj\u00eb tokeni fizik nuk \u00ebsht\u00eb gjithmon\u00eb e mundur. Nj\u00eb tjet\u00ebr mund\u00ebsi \u00ebsht\u00eb t\u00eb implementohet verifikimi i dyfisht\u00eb p\u00ebrmes SMS, i cili n\u00eb rastin e 2FA mund t\u00eb funksionoj\u00eb si konfirmim se personi q\u00eb kryen procesin e rikthimit ka telefonin mobil t\u00eb pronarit t\u00eb llogaris\u00eb. K\u00ebshtu e b\u00ebn Google:<\/p>\n

\"Gjith\u00e7ka
\nPo ashtu \u00ebsht\u00eb e nevojshme t\u00eb p\u00ebrfshihet verifikimi me dy shkall\u00eb<\/a><\/noindex>, por kjo do t\u00eb thot\u00eb se kur t\u00eb b\u00ebni rikthimin e ardhsh\u00ebm t\u00eb fjal\u00ebkalimit, telefoni juaj mobil mund t\u00eb b\u00ebhet faktor i dyt\u00eb i verifikimit. M\u00eb lejoni ta demonstroj k\u00ebt\u00eb n\u00eb shembullin tim t\u00eb iPhone p\u00ebr shkak t\u00eb arsyeve q\u00eb do t\u00eb b\u00ebhen t\u00eb qarta s\u00eb shpejti:<\/p>\n

\"Gjith\u00e7ka
\nPas identifikimit t\u00eb adres\u00ebs s\u00eb post\u00ebs elektronike t\u00eb llogaris\u00eb Google, p\u00ebrcaktohet se 2FA \u00ebsht\u00eb aktivizuar dhe ne mund t\u00eb rikthejm\u00eb llogarin\u00eb p\u00ebrmes verifikimit, i cili d\u00ebrgohet p\u00ebrmes SMS n\u00eb telefonin mobil t\u00eb pronarit t\u00eb llogaris\u00eb:<\/p>\n

\"Gjith\u00e7ka
\nTani na nevojitet t\u00eb zgjedhim fillimin e procesit t\u00eb rikthimit:<\/p>\n

\"Gjith\u00e7ka
\nKy veprim sjell d\u00ebrgimin e nj\u00eb emaili n\u00eb adres\u00ebn e regjistruar:<\/p>\n

\"Gjith\u00e7ka
\nKy email p\u00ebrmban URL-n\u00eb e rikuperimit:<\/p>\n

\"Gjith\u00e7ka
\nKur qaseni n\u00eb URL-n\u00eb e rikuperimit, nj\u00eb SMS d\u00ebrgohet dhe faqja k\u00ebrc\u00ebnon t\u00eb k\u00ebrkoj\u00eb kodin:<\/p>\n

\"Gjith\u00e7ka
\nJa ky SMS:<\/p>\n

\"Gjith\u00e7ka
\nPas futjes s\u00eb tij n\u00eb shfletues, kthehemi n\u00eb procesin klasik t\u00eb rikuperimit t\u00eb fjal\u00ebkalimit:<\/p>\n

\"Gjith\u00e7ka
\nMund t\u00eb duket pak e tep\u00ebrt, dhe n\u00eb t\u00eb v\u00ebrtet\u00eb \u00ebsht\u00eb, por forma konfirmon se personi q\u00eb po rikuperon ka akses n\u00eb adres\u00ebn e emailit dhe numrin e telefonit t\u00eb llogaridh\u00ebn\u00ebsit. Por kjo mund t\u00eb jet\u00eb deri n\u00eb n\u00ebnt\u00eb her\u00eb m\u00eb e sigurt se rikuperimi i fjal\u00ebkalimit vet\u00ebm p\u00ebrmes emailit. Megjithat\u00eb, ka disa probleme...<\/p>\n

Problemi ka t\u00eb b\u00ebj\u00eb me smartfon\u00ebt. Pajisja e treguar m\u00eb posht\u00eb mund t\u00eb verifikoj\u00eb vet\u00ebm nj\u00eb faktor autentikimi - ajo mund t\u00eb marr\u00eb SMS, por jo email:<\/p>\n

\"Gjith\u00e7ka
\nMegjithat\u00eb, kjo pajisje mund t\u00eb marr\u00eb SMS dhe<\/em> t\u00eb marr\u00eb email p\u00ebr rikuperimin e fjal\u00ebkalimit:<\/p>\n

\"Gjith\u00e7ka
\nProblemi \u00ebsht\u00eb se ne e shohim emailin si faktor t\u00eb par\u00eb t\u00eb autentifikimit, dhe SMS (apo edhe nj\u00eb aplikacion q\u00eb gjeneron kode) si t\u00eb dyt\u00eb, por sot ato jan\u00eb t\u00eb bashkuara n\u00eb nj\u00eb pajisje. Natyrisht, kjo do t\u00eb thot\u00eb se n\u00ebse dikush arrin t\u00eb hyj\u00eb n\u00eb smartfonin tuaj, at\u00ebher\u00eb t\u00eb gjitha k\u00ebto leht\u00ebsi do t\u00eb kthehen n\u00eb nj\u00eb kanal; ky faktor i dyt\u00eb \"\u00e7far\u00eb keni\" do t\u00eb thot\u00eb gjithashtu se ju e keni edhe faktorin e par\u00eb. Dhe gjith\u00e7ka \u00ebsht\u00eb e mbrojtur nga nj\u00eb PIN prej kat\u00ebr shifrash... n\u00ebse telefoni ka ndonj\u00ebher\u00eb nj\u00eb PIN. dhe<\/em> ai \u00ebsht\u00eb bllokuar.<\/p>\n

Po, funksioni 2FA i realizuar nga Google sigurisht q\u00eb ofron mbrojtje shtes\u00eb, por ai nuk \u00ebsht\u00eb i mbrojtur \"nga budallai\", dhe me siguri nuk varet nga dy kanale t\u00eb plota dhe autonom.<\/p>\n

Rivendosja me em\u00ebr t\u00eb p\u00ebrdoruesit p\u00ebrball\u00eb rivendosjes me adres\u00eb emaili.<\/h2>\n

\nA duhet t\u00eb lejohet rivendosja vet\u00ebm me adres\u00eb emaili? Apo p\u00ebrdoruesi duhet t\u00eb ket\u00eb mund\u00ebsin\u00eb t\u00eb kryej\u00eb rivendosje dhe p\u00ebrmes emrit? Problemi me rivendosjen me em\u00ebr p\u00ebrdoruesi \u00ebsht\u00eb se nuk ka asnj\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb njoftuar p\u00ebrdoruesin p\u00ebr emrin e gabuar t\u00eb p\u00ebrdoruesit, pa zbuluar<\/em> se dikush tjet\u00ebr mund t\u00eb ket\u00eb nj\u00eb llogari me k\u00ebt\u00eb em\u00ebr. N\u00eb seksionin e m\u00ebparsh\u00ebm, riciklimi p\u00ebrmes emailit garantonte q\u00eb pronari legjitim i k\u00ebtij emaili do t\u00eb merrte gjithmon\u00eb p\u00ebrgjigje pa e zbuluar publikisht ekzistenc\u00ebn e tij n\u00eb sistem. Me ndihm\u00ebn e vet\u00ebm emrit t\u00eb p\u00ebrdoruesit, kjo nuk \u00ebsht\u00eb e mundur.<\/p>\n

Prandaj, p\u00ebrgjigjja \u00ebsht\u00eb e shkurt\u00ebr: vet\u00ebm emaili. N\u00ebse p\u00ebrpiqeni t\u00eb kryeni riciklimin vet\u00ebm me emrin e p\u00ebrdoruesit, do t\u00eb ken\u00eb ndodhur raste kur p\u00ebrdoruesi do t\u00eb mbetet n\u00eb konfuzion se \u00e7far\u00eb ka ndodhur. ose<\/em> do t\u00eb zbulojn\u00eb ekzistenc\u00ebn e llogarive. Po, \u00ebsht\u00eb vet\u00ebm emri i p\u00ebrdoruesit, jo adresa e emailit dhe po, \u00e7do person mund t\u00eb zgjedh\u00eb ndonj\u00eb em\u00ebr p\u00ebrdoruesi (t\u00eb disponuesh\u00ebm), por p\u00ebrs\u00ebri ekziston nj\u00eb mund\u00ebsi e madhe q\u00eb do t\u00eb zbulojn\u00eb indirekt pronar\u00ebt e llogarive p\u00ebr shkak t\u00eb prirjes s\u00eb p\u00ebrdoruesve p\u00ebr t\u00eb p\u00ebrdorur p\u00ebrs\u00ebrit\u00ebshem emrin.<\/p>\n

Cili \u00ebsht\u00eb procesi, kur dikush harron emrin e p\u00ebrdoruesit? N\u00ebse supozojm\u00eb se emri i p\u00ebrdoruesit nuk \u00ebsht\u00eb menj\u00ebher\u00eb adresa e-mail (dhe kjo ndodh shpesh), procesi \u00ebsht\u00eb si\u00e7 fillon nj\u00eb riaktive e fjal\u00ebkalimit \u2014 ne shkruajm\u00eb adres\u00ebn e emailit dhe m\u00eb pas d\u00ebrgojm\u00eb nj\u00eb mesazh n\u00eb at\u00eb adres\u00eb, pa zbuluar ekzistenc\u00ebn e saj. Ndryshimi i vetem \u00ebsht\u00eb se k\u00ebsaj here mesazhi p\u00ebrmban vet\u00ebm emrin e p\u00ebrdoruesit, dhe jo URL-n\u00eb e riaktivizimit t\u00eb fjal\u00ebkalimit. Ose do t\u00eb ket\u00eb nj\u00eb mesazh n\u00eb email q\u00eb tregon se nuk ekziston nj\u00eb llogari p\u00ebr k\u00ebt\u00eb adres\u00eb.<\/p>\n

Verifikimi i identitetit dhe sakt\u00ebsia e adresave t\u00eb e-mailit<\/h2>\n

\nNj\u00eb aspekt ky\u00e7 i riaktiveve t\u00eb fjal\u00ebkalimeve, dhe madje ndoshta aspekti<\/em> m\u00eb i r\u00ebnd\u00ebsish\u00ebm \u00ebsht\u00eb verifikimi i identitetit t\u00eb personit q\u00eb p\u00ebrpiqet t\u00eb b\u00ebj\u00eb riaktivizimin. A \u00ebsht\u00eb v\u00ebrtet pronari legjitim i llogaris\u00eb, apo dikush po p\u00ebrpiqet ta thyej\u00eb at\u00eb ose t'i shkaktoj\u00eb probleme pronarit?<\/p>\n

Evident se se-maili \u00ebsht\u00eb kanali m\u00eb i p\u00ebrshtatsh\u00ebm dhe m\u00eb i p\u00ebrhapur p\u00ebr verifikimin e identitetit. Ai nuk \u00ebsht\u00eb i mbrojtur nga keqp\u00ebrdorimi i paqart\u00eb (\"nga budallai\"), dhe ekziston nj\u00eb num\u00ebr i madh rastesh kur thjesht mund\u00ebsia p\u00ebr t\u00eb marr\u00ebn\u00eb emaile n\u00eb adres\u00ebn e pronarit t\u00eb llogaris\u00eb nuk \u00ebsht\u00eb e mjaftueshme, n\u00ebse k\u00ebrkohet nj\u00eb siguri m\u00eb e lart\u00eb p\u00ebr identifikim (prandaj p\u00ebrdoret 2FA), megjithat\u00eb pothuajse gjithmon\u00eb \u00ebsht\u00eb pika fillestare e procesit t\u00eb rikuperimit.<\/p>\n

N\u00ebse emaili do t\u00eb luaj\u00eb nj\u00eb rol n\u00eb sigurimin e besueshm\u00ebris\u00eb, at\u00ebher\u00eb e para q\u00eb duhet t\u00eb b\u00ebni \u00ebsht\u00eb t\u00eb siguroheni q\u00eb adresa e emailit t\u00eb jet\u00eb v\u00ebrtet e sakt\u00eb. N\u00ebse dikush gabon nj\u00eb simbol, \u00ebsht\u00eb e qart\u00eb se rikuperimi nuk do t\u00eb filloj\u00eb. Procesi i verifikimit t\u00eb emailit n\u00eb momentin e regjistrimit \u00ebsht\u00eb nj\u00eb m\u00ebnyr\u00eb e besueshme p\u00ebr t\u00eb verifikuar sakt\u00ebsin\u00eb e adres\u00ebs. T\u00eb gjith\u00eb e kemi par\u00eb k\u00ebt\u00eb n\u00eb praktik\u00eb: regjistroheni, ju d\u00ebrgohet nj\u00eb email me nj\u00eb URL unik, n\u00eb t\u00eb cilin duhet t\u00eb klikoni, i cili konfirmon se ju jeni me t\u00eb v\u00ebrtet\u00eb pronari i k\u00ebtij llogarie emaili. Pamund\u00ebsia p\u00ebr t\u00eb hyr\u00eb n\u00eb sistem deri sa t\u00eb p\u00ebrfundoj\u00eb ky proces siguron nj\u00eb motivim p\u00ebr t\u00eb konfirmuar adres\u00ebn.<\/p>\n

Si n\u00eb rastin e shum\u00eb aspekteve t\u00eb tjera t\u00eb siguris\u00eb, nj\u00eb model i till\u00eb ul p\u00ebrdorshm\u00ebrin\u00eb n\u00eb k\u00ebmbim t\u00eb ofrimit t\u00eb nj\u00eb niveli t\u00eb shtuar sigurie n\u00eb lidhje me identitetin e p\u00ebrdoruesit. Kjo mund t\u00eb jet\u00eb e pranueshme p\u00ebr nj\u00eb faqe q\u00eb p\u00ebrdoruesi e vler\u00ebson shum\u00eb dhe do t\u00eb ishte i gatsh\u00ebm t\u00eb shtonte nj\u00eb hap tjet\u00ebr n\u00eb proces (sh\u00ebrbime me pages\u00eb, bankari, etj.), por gj\u00ebra t\u00eb tilla mund ta ndalin p\u00ebrdoruesin n\u00ebse e percepton llogarin\u00eb si 't\u00eb p\u00ebrkohshme' dhe e p\u00ebrdor, p\u00ebr shembull, thjesht si nj\u00eb mjet p\u00ebr t\u00eb komentuar nj\u00eb postim.<\/p>\n

Identifikimi i atij q\u00eb iniciuan procesin e rikthimit<\/h2>\n

\nMund t\u00eb ket\u00eb sigurisht arsye p\u00ebr p\u00ebrdorim t\u00eb keq t\u00eb funksionit t\u00eb rikthimit, dhe keqb\u00ebr\u00ebsit mund ta p\u00ebrdorin at\u00eb n\u00eb shum\u00eb m\u00ebnyra t\u00eb ndryshme. Nj\u00eb truk i thjesht\u00eb q\u00eb mund t\u00eb p\u00ebrdorim p\u00ebr t\u00eb ndihmuar n\u00eb konfirmimin e burimit t\u00eb k\u00ebrkes\u00ebs (ky truk zakonisht<\/em> funksionon) \u2014 \u00ebsht\u00eb t\u00eb shtojm\u00eb n\u00eb emailin me ofert\u00ebn p\u00ebr rikthim IP-n\u00eb e adres\u00ebs q\u00eb k\u00ebrkon. Kjo i ofron marr\u00ebsit disa<\/em> informacione p\u00ebr identifikimin e burimit t\u00eb k\u00ebrkes\u00ebs.<\/p>\n

Ja nj\u00eb shembull nga funksioni i rikthimit q\u00eb po integroj tani n\u00eb ASafaWeb:<\/p>\n

\"Gjith\u00e7ka
\nLinku \u00abfind out more\u00bb (\u00abM\u00ebso m\u00eb shum\u00eb\u00bb) e \u00e7on p\u00ebrdoruesin n\u00eb faqen ip-adress.com<\/a><\/noindex>, e cila raporton informacion si vendndodhjen dhe organizat\u00ebn e k\u00ebrkuesit p\u00ebr rikuperim:<\/p>\n

\"Gjith\u00e7ka
\nNatyrisht, \u00e7do kush q\u00eb do t\u00eb fsheh\u00eb identitetin e tij ka shum\u00eb m\u00ebnyra p\u00ebr t\u00eb mashtuar IP-n\u00eb e tij t\u00eb v\u00ebrtet\u00eb, megjithat\u00eb kjo \u00ebsht\u00eb nj\u00eb m\u00ebnyr\u00eb e leht\u00eb p\u00ebr t\u00eb shtuar nj\u00eb identifikim t\u00eb pjessh\u00ebm t\u00eb k\u00ebrkuesit, dhe n\u00eb shumic\u00ebn<\/em> t\u00eb rasteve kjo do t'ju jap\u00eb nj\u00eb ide t\u00eb mjaftueshme se kush do t\u00eb kryej\u00eb k\u00ebrkes\u00ebn p\u00ebr rikuperimin e fjal\u00ebkalimit.<\/p>\n

Njoftimi p\u00ebr ndryshime n\u00ebp\u00ebrmjet post\u00ebs elektronike<\/h2>\n

\nKy post \u00ebsht\u00eb i mbushur me nj\u00eb tem\u00eb \u2014 komunikimi; informoni pronarin e llogaris\u00eb sa m\u00eb shum\u00eb p\u00ebr at\u00eb q\u00eb ndodh n\u00eb \u00e7do hap t\u00eb procesit, pa zbuluar ndonj\u00eb gj\u00eb q\u00eb mund t\u00eb p\u00ebrdoret p\u00ebr q\u00ebllime t\u00eb k\u00ebqija. E nj\u00ebjta gj\u00eb vlen edhe p\u00ebr situaten kur fjal\u00ebkalimi n\u00eb t\u00eb v\u00ebrtet\u00eb \u00ebsht\u00eb ndryshuar \u2014 informoni pronarin!<\/em><\/strong><\/p>\n

Arsyet p\u00ebr ndryshimin e fjal\u00ebkalimit mund t\u00eb jen\u00eb dy burime:<\/p>\n

    \n
  1. Ndryshimi i fjal\u00ebkalimit pas hyrjes n\u00eb sistem, sepse p\u00ebrdoruesi d\u00ebshiron nj\u00eb fjal\u00ebkalim t\u00eb ri<\/li>\n
  2. Rikuperimi i fjal\u00ebkalimit pa hyrje n\u00eb sistem, sepse p\u00ebrdoruesi e ka harruar at\u00eb<\/li>\n<\/ol>\n

    \nMegjith\u00ebse ky post \u00ebsht\u00eb n\u00eb t\u00ebr\u00ebsi i fokusuar te rikthimi i fjal\u00ebkalimit, njoftimi n\u00eb rastin e par\u00eb zvog\u00eblon rrezikun q\u00eb dikush t\u00eb ndryshoj\u00eb fjal\u00ebkalimin pa dijenin\u00eb e pronarit t\u00eb ligjsh\u00ebm. Si mund t\u00eb ndodh\u00eb kjo? Nj\u00eb skenar mjaft i zakonsh\u00ebm \u00ebsht\u00eb marrja e fjal\u00ebkalimit t\u00eb pronarit t\u00eb ligjsh\u00ebm (nj\u00eb fjal\u00ebkalim i rib\u00ebr\u00eb nga nj\u00eb burim tjet\u00ebr; nj\u00eb fjal\u00ebkalim i marr\u00eb p\u00ebrmes keylogging; nj\u00eb fjal\u00ebkalim i leht\u00eb p\u00ebr t'u gjetur, etj.), pas s\u00eb cil\u00ebs sulmuesi vendos ta ndryshoj\u00eb at\u00eb, k\u00ebshtu q\u00eb duke e bllokuar pronarin. Pa nj\u00eb njoftim me email, pronari aktual nuk do t\u00eb dij\u00eb p\u00ebr ndryshimin e fjal\u00ebkalimit.<\/p>\n

    Sigurisht, n\u00eb rastin e rikthimit t\u00eb fjal\u00ebkalimit, pronari tashm\u00eb duhet ta ket\u00eb iniciuar procesin vet\u00eb (ose t\u00eb ket\u00eb anashkaluar mjetet e verifikimit t\u00eb identitetit t\u00eb p\u00ebrmendura m\u00eb sip\u00ebr), k\u00ebshtu q\u00eb nd\u00ebrrimi nuk duhet<\/em> mund t\u00eb jet\u00eb nj\u00eb surpriz\u00eb p\u00ebr t\u00eb, megjithat\u00eb konfirmimi me email do t\u00eb jet\u00eb nj\u00eb reagim pozitiv dhe nj\u00eb kontroll shtes\u00eb. P\u00ebr m\u00eb tep\u00ebr, kjo siguron nj\u00ebsi me skenarin e p\u00ebrshkruar m\u00eb lart.<\/p>\n

    O, dhe p\u00ebr rastin n\u00ebse kjo nuk \u00ebsht\u00eb ende e qart\u00eb \u2014 mos e d\u00ebrgoni nj\u00eb fjal\u00ebkalim t\u00eb ri p\u00ebrmes post\u00ebs!<\/em><\/strong> Dikush mund t\u00eb qesh\u00eb p\u00ebr k\u00ebt\u00eb, por di\u00e7ka e till\u00eb ndodh<\/a><\/noindex>:<\/p>\n

    \"Gjith\u00e7ka<\/p>\n

    Log\u00eb, log\u00eb, log\u00eb dhe pak m\u00eb shum\u00eb log\u00eb<\/h2>\n

    \nFunksioni i rivendosjes s\u00eb fjal\u00ebkalimit \u00ebsht\u00eb t\u00ebrheq\u00ebs p\u00ebr sulmuesit: nj\u00eb sulmues d\u00ebshiron t\u00eb ket\u00eb qasje n\u00eb llogarin\u00eb e nj\u00eb personi tjet\u00ebr ose thjesht t\u00eb shkaktoj\u00eb shqet\u00ebsim p\u00ebr pronarin e llogaris\u00eb\/sistemit. Shum\u00eb nga praktikat e p\u00ebrmendura m\u00eb sip\u00ebr lejojn\u00eb reduktimin e mund\u00ebsive p\u00ebr abuzim, por nuk parandalojn\u00eb ato dhe me siguri nuk do t\u00eb ndalin njer\u00ebzit nga p\u00ebrpjekja p\u00ebr t\u00eb p\u00ebrdorur funksionin n\u00eb m\u00ebnyr\u00eb t\u00eb pap\u00ebrshtatshme.<\/p>\n

    P\u00ebr t\u00eb njohur sjelljen keqdash\u00ebse, nj\u00eb praktik\u00eb e \u00e7muar \u00ebsht\u00eb regjistrimi, dhe kam n\u00eb mendje regjistrimin shum\u00eb t\u00eb detajuar<\/em><\/strong>. Regjistroni p\u00ebrpjekjet e d\u00ebshtuara p\u00ebr t\u00eb hyr\u00eb n\u00eb sistem, rivendosjet e fjal\u00ebkalimeve, ndryshimin e fjal\u00ebkalimeve (dmth. kur p\u00ebrdoruesi \u00ebsht\u00eb tashm\u00eb i lidhur) dhe praktikisht gjith\u00e7ka q\u00eb mund t\u00eb ndihmoj\u00eb n\u00eb kuptimin e asaj q\u00eb po ndodh; kjo do t'ju ndihmoj\u00eb shum\u00eb n\u00eb t\u00eb ardhmen. Regjistroni n\u00eb log t\u00eb pakt\u00ebn pjes\u00eb<\/em> procesit, p\u00ebr shembull, nj\u00eb funksion i mir\u00eb riaktivizimi duhet t\u00eb p\u00ebrfshij\u00eb iniciimin e riaktivizimit p\u00ebrmes faqes s\u00eb internetit (regjistroni k\u00ebrkesat dhe p\u00ebrpjekjet e ky\u00e7jes p\u00ebr riaktivizimin me emrin e p\u00ebrdoruesit ose emailin e gabuar), regjistroni vizit\u00ebn n\u00eb faqen e internetit p\u00ebr URL-n\u00eb e riaktivizimit (duke p\u00ebrfshir\u00eb p\u00ebrpjekjet p\u00ebr t\u00eb p\u00ebrdorur nj\u00eb token t\u00eb pavlefsh\u00ebm), dhe m\u00eb pas regjistroni n\u00eb log suksesin ose d\u00ebshtimin e p\u00ebrgjigjes ndaj pyetjes sekrete.<\/p>\n

    Kur flas p\u00ebr regjistrimin, kam parasysh jo vet\u00ebm regjistrimin e faktit t\u00eb ngarkes\u00ebs s\u00eb faqes, por edhe mbledhjen e sa m\u00eb shum\u00eb informacioni, n\u00ebse nuk \u00ebsht\u00eb konfidencial<\/em><\/strong>. Djem, ju lutem, mos e regjistroni fjal\u00ebkalimin n\u00eb log!<\/em><\/strong> N\u00eb log duhet t\u00eb regjistrohet identiteti i p\u00ebrdoruesit t\u00eb autorizuar (ai do t\u00eb jet\u00eb i autorizuar n\u00ebse ai ndryshon<\/em> fjal\u00ebkalimin ekzistues ose p\u00ebrpiqet t\u00eb riaktivizoj\u00eb fjal\u00ebkalimin e t\u00eb tjer\u00ebve<\/em> pas ky\u00e7jes n\u00eb sistem), \u00e7far\u00ebdo emrash p\u00ebrdoruesish ose adresash emaili q\u00eb ai provon plus \u00e7do token riaktivizimi q\u00eb ai p\u00ebrpiqet t\u00eb p\u00ebrdor\u00eb. Por gjithashtu ia vlen t\u00eb regjistrohen n\u00eb log aspekte t\u00eb tilla si adresat IP dhe, n\u00ebse \u00ebsht\u00eb e mundur, madje edhe titujt e k\u00ebrkesave. Kjo ju lejon t\u00eb rivendosni jo vet\u00ebm \u00e7far\u00eb<\/em> p\u00ebrdoruesi (ose sulmuesi) p\u00ebrpiqet t\u00eb b\u00ebj\u00eb, por edhe kush<\/em> ai \u00ebsht\u00eb i till\u00eb.<\/p>\n

    Delegimi i p\u00ebrgjegj\u00ebsis\u00eb te ekzekutor\u00eb t\u00eb tjer\u00eb<\/h2>\n

    \nN\u00ebse mendoni se t\u00eb gjitha k\u00ebto paraqesin nj\u00eb volum t\u00eb madh pune, nuk jeni t\u00eb vetmuar. N\u00eb t\u00eb v\u00ebrtet\u00eb, nd\u00ebrtimi i nj\u00eb sistemi t\u00eb besuesh\u00ebm p\u00ebr menaxhimin e llogarive \u00ebsht\u00eb nj\u00eb detyr\u00eb e v\u00ebshtir\u00eb. Problemi nuk \u00ebsht\u00eb se \u00ebsht\u00eb shum\u00eb teknik, thjesht ka shum\u00eb nuanca. Nuk p\u00ebrfshin vet\u00ebm rivendosjen e fjal\u00ebkalimeve, ekziston nj\u00eb proces i plot\u00eb regjistrimi, ruajtja e sigurt e fjal\u00ebkalimeve, p\u00ebrpunimi i p\u00ebrpjekjeve t\u00eb shumta t\u00eb gabuara p\u00ebr t\u00eb hyr\u00eb n\u00eb sistem etj., etj. Nd\u00ebrsa un\u00eb promovoj iden\u00eb e p\u00ebrdorimit t\u00eb funksionalitetit t\u00eb gatsh\u00ebm si ofruesi i an\u00ebtar\u00ebsis\u00eb ASP.NET,<\/a><\/noindex>, p\u00ebrve\u00e7 saj, duhet b\u00ebr\u00eb shum\u00eb m\u00eb tep\u00ebr.<\/p>\n

    Sot ekzistojn\u00eb shum\u00eb ofrues t\u00eb jasht\u00ebm, t\u00eb cil\u00ebt me k\u00ebnaq\u00ebsi marrin p\u00ebrsip\u00ebr t\u00eb gjitha mundimet dhe hipotetizojn\u00eb t\u00eb gjitha k\u00ebto n\u00eb nj\u00eb sh\u00ebrbim t\u00eb menaxhuar. Mes k\u00ebtyre sh\u00ebrbimeve jan\u00eb OpenID, OAuth dhe madje edhe Facebook. Disa njer\u00ebz e besojn\u00eb pa kufi k\u00ebt\u00eb model<\/a><\/noindex> (OpenID n\u00eb t\u00eb v\u00ebrtet\u00eb ka qen\u00eb shum\u00eb i suksessh\u00ebm n\u00eb Stack Overflow), megjithat\u00eb t\u00eb tjer\u00eb n\u00eb kuptimin e v\u00ebrtet\u00eb e konsiderojn\u00eb at\u00eb nj\u00eb makth.<\/a><\/noindex>.<\/p>\n

    Pa dyshim, nj\u00eb sh\u00ebrbim si OpenID zgjidh shum\u00eb probleme p\u00ebr zhvilluesit, por gjithashtu, pa dyshim, shton t\u00eb reja. A kan\u00eb ata ndonj\u00eb rol? Po, por \u00ebsht\u00eb evidente se nuk po shohim nj\u00eb p\u00ebrdorim masiv t\u00eb sh\u00ebrbimeve t\u00eb ofruesve t\u00eb autentifikimit. Bankat, linjat ajrore dhe madje edhe dyqanet \u2014 t\u00eb gjitha realizojn\u00eb mekanizma t\u00eb tyre t\u00eb autentifikimit, dhe \u00ebsht\u00eb e qart\u00eb se ka arsye shum\u00eb t\u00eb forta p\u00ebr k\u00ebt\u00eb.<\/p>\n

    Rivendosja e keqe<\/h2>\n

    \nNj\u00eb aspekt i r\u00ebnd\u00ebsish\u00ebm i \u00e7do nj\u00eb nga shembujt e m\u00ebsip\u00ebrm \u00ebsht\u00eb se fjal\u00ebkalimi i vjet\u00ebr konsiderohet i padobish\u00ebm vet\u00ebm pas konfirmimit t\u00eb identitetit t\u00eb pronarit t\u00eb llogaris\u00eb<\/em><\/strong>. Kjo \u00ebsht\u00eb e r\u00ebnd\u00ebsishme, sepse po t\u00eb ishte e mundur t\u00eb rivendosej llogaria deri te<\/em> pa verifikimin e identifikimit, do t\u00eb jepte mund\u00ebsi p\u00ebr veprime t\u00eb ndryshme t\u00eb keqia.<\/p>\n

    Ja nj\u00eb shembull: dikush merr pjes\u00eb n\u00eb ankande n\u00eb nj\u00eb faqe ankandi, dhe af\u00ebr fundit t\u00eb procesit t\u00eb ankandeve ai bllokon konkurrent\u00ebt, duke iniciuar procesin e rivendosjes, duke eliminuar k\u00ebshtu ata nga ankandi. Sigurisht, n\u00ebse nj\u00eb funksion rivendosjeje i dizajnuar keq mund t\u00eb keqp\u00ebrdoret, kjo mund t\u00eb \u00e7oj\u00eb n\u00eb rezultate serioze negative. Duhet t\u00eb v\u00ebreni se bllokimi i llogarive p\u00ebrmes p\u00ebrpjekjeve t\u00eb gabuara p\u00ebr t'u ky\u00e7ur \u00ebsht\u00eb nj\u00eb situat\u00eb e ngjashme, por kjo \u00ebsht\u00eb nj\u00eb tem\u00eb p\u00ebr nj\u00eb postim tjet\u00ebr.<\/p>\n

    Si\u00e7 e p\u00ebrmenda m\u00eb sip\u00ebr, n\u00ebse u jepet p\u00ebrdoruesve anonim mund\u00ebsia p\u00ebr t\u00eb rivendosur fjal\u00ebkalimin e \u00e7do llogarije, thjesht duke e ditur adres\u00ebn e saj t\u00eb post\u00ebs elektronike, at\u00ebher\u00eb kjo \u00ebsht\u00eb nj\u00eb situat\u00eb ideale p\u00ebr nj\u00eb sulm t\u00eb tipit \"refuzim sh\u00ebrbimi\". Kjo mund t\u00eb mos jet\u00eb ajo DoS<\/a><\/noindex>, me t\u00eb cil\u00ebn jemi m\u00ebsuar t\u00eb flasim, por nuk ka m\u00ebnyr\u00eb m\u00eb t\u00eb shpejt\u00eb p\u00ebr t\u00eb bllokuar aksesin n\u00eb nj\u00eb llogari sesa me nj\u00eb funksion rivendosjeje fjal\u00ebkalimi t\u00eb menduar keq.<\/p>\n

    Pika m\u00eb e dob\u00ebt<\/h2>\n

    \nNga pik\u00ebpamja e mbrojtjes s\u00eb nj\u00eb llogarie, gjith\u00e7ka e shkruajtur m\u00eb sip\u00ebr \u00ebsht\u00eb e shk\u00eblqyer, megjithat\u00eb duhet gjithmon\u00eb t\u00eb mbani mend ekosistemin q\u00eb rrethon llogarin\u00eb q\u00eb po e mbrojm\u00eb. Le t\u00eb japim nj\u00eb shembull:<\/p>\n

    ASafaWeb \u00ebsht\u00eb hostuar n\u00eb nj\u00eb sh\u00ebrbim fantastik t\u00eb ofruar nga AppHarbor. Procesi i rikthimit t\u00eb llogaris\u00eb s\u00eb hostimit zhvillohet si n\u00eb vijim:<\/p>\n

    Hapi 1:<\/strong><\/p>\n

    \"Gjith\u00e7ka
    \nHapi 2:<\/strong><\/p>\n

    \"Gjith\u00e7ka
    \nHapi 3:<\/strong><\/p>\n

    \"Gjith\u00e7ka
    \nHapi 4:<\/strong><\/p>\n

    \"Gjith\u00e7ka
    \nPas leximit t\u00eb gjith\u00eb informacionit t\u00eb m\u00ebparsh\u00ebm, \u00ebsht\u00eb e leht\u00eb t\u00eb kuptohet se cilat aspekte do t\u2019i realizonim ndryshe n\u00eb nj\u00eb bot\u00eb t\u00eb p\u00ebrkryer. megjithat\u00eb, k\u00ebtu dua t\u00eb them se n\u00ebse publikohem nj\u00eb site si ASafaWeb n\u00eb sh\u00ebrbimin AppHarbor, dhe pastaj shpik disa pyetje dhe p\u00ebrgjigje sekrete t\u00eb shk\u00eblqyera, shtoj nj\u00eb faktor t\u00eb dyt\u00eb t\u00eb autentikimit dhe b\u00ebj gjith\u00e7ka sipas rregullave, kjo nuk e anashkalon faktin se pika m\u00eb e dob\u00ebt e t\u00eb gjith\u00eb procesit do t\u00eb jet\u00eb n\u00eb gjendje ta prish\u00eb at\u00eb. N\u00ebse dikush arrin t\u00eb autentikohet n\u00eb AppHarbor duke p\u00ebrdorur informacionin tim, ai do t\u00eb mund t\u00eb ndryshoj\u00eb fjal\u00ebkalimin p\u00ebr \u00e7do llogari ASafaWeb n\u00eb m\u00ebnyr\u00ebn q\u00eb d\u00ebshiron!<\/p>\n

    Kuptimi \u00ebsht\u00eb se q\u00ebndrueshm\u00ebria e implementimit t\u00eb mbrojtjes duhet t\u00eb shqyrtohet n\u00eb m\u00ebnyr\u00eb holistike: duhet t\u00eb modelojm\u00eb k\u00ebrc\u00ebnimet p\u00ebr \u00e7do pik\u00eb hyrjeje t\u00eb sistemit, edhe n\u00ebse \u00ebsht\u00eb nj\u00eb proces i sip\u00ebrfaqsh\u00ebm, si\u00e7 \u00ebsht\u00eb hyrja n\u00eb sistemin AppHarbor. Kjo duhet t\u00eb m\u00eb jap\u00eb nj\u00eb ide t\u00eb mir\u00eb se sa p\u00ebrpjekje duhet t\u00eb investoj n\u00eb procesin e rikthimit t\u00eb fjal\u00ebkalimit ASafaWeb.<\/p>\n

    Lidhim gjith\u00e7ka s\u00eb bashku<\/h2>\n

    \nKy post p\u00ebrmban nj\u00eb sasi t\u00eb madhe informacioni, prandaj dua ta p\u00ebrmbledh n\u00eb nj\u00eb diagram\u00eb vizuale t\u00eb thjesht\u00eb:<\/p>\n

    \"Gjith\u00e7ka
    \nMos harroni se duhet t\u00eb b\u00ebni loggimin sa m\u00eb t\u00eb detajuar t\u00eb secilit nga k\u00ebto pika. Kjo \u00ebsht\u00eb gjith\u00e7ka, \u00ebsht\u00eb e thjesht\u00eb!<\/p>\n

    P\u00ebrfundimet<\/h2>\n

    \nPosti im duket gjith\u00ebp\u00ebrfshir\u00ebs, megjithat\u00eb ekzistojn\u00eb shum\u00eb materiale shtes\u00eb q\u00eb mund t\u00eb<\/em> i p\u00ebrfshija n\u00eb t\u00eb, por vendosa t\u00eb heq dor\u00eb nga kjo p\u00ebr shkak t\u00eb shkurt\u00ebsis\u00eb: roli i adres\u00ebs s\u00eb emailit t\u00eb ndihm\u00ebs, situata kur humbni qasje n\u00eb emailin e lidhur me llogarin\u00eb (p.sh., kur e l\u00ebni pun\u00ebn), dhe shum\u00eb t\u00eb tjera. Si\u00e7 thash\u00eb m\u00eb par\u00eb, funksioni i rinovimit nuk \u00ebsht\u00eb kaq i komplikuar, thjesht ka shum\u00eb k\u00ebndv\u00ebshtrime mbi t\u00eb.<\/p>\n

    Edhe pse rinovimi nuk \u00ebsht\u00eb kaq i v\u00ebshtir\u00eb, shpesh implementohet gabimisht. M\u00eb lart ne pam\u00eb disa shembuj kur implementimi mund<\/em> ka sjell\u00eb probleme, dhe ka shum\u00eb m\u00eb tep\u00ebr raste kur nj\u00eb rinovim i gabuar v\u00ebrtet<\/em> ka shkaktuar probleme. S\u00eb fundmi u zbulua se rinovimi i fjal\u00ebkalimit u p\u00ebrdor p\u00ebr t\u00eb vjedhur bitcoin me vler\u00eb 87 mij\u00eb dollar\u00eb.<\/a><\/noindex>Ky \u00ebsht\u00eb nj\u00eb rezultat shum\u00eb negativ!<\/p>\n

    Prandaj, jini t\u00eb kujdessh\u00ebm me funksionet tuaja t\u00eb rinovimit, modeloni k\u00ebrc\u00ebnimet<\/a><\/noindex> n\u00eb pika t\u00eb ndryshme, dhe gjat\u00eb projektimit t\u00eb funksioneve mos hiqni kapelen tuaj t\u00eb zez\u00eb, sepse ka nj\u00eb mund\u00ebsi t\u00eb madhe q\u00eb dikush tjet\u00ebr ta vendos\u00eb at\u00eb!<\/p>\n

    <\/p>\n

    Si reklam\u00eb<\/h4>\n

    \nVDSina<\/b> ofron servera t\u00eb lir\u00eb me qira<\/a><\/noindex> me pages\u00eb ditore, \u00e7do server i lidhur me nj\u00eb lidhje interneti prej 500 Megabit dhe i mbrojtur falas nga sulmet DDoS!<\/p>\n

    \"Gjith\u00e7ka<\/a><\/noindex>
    \n
    Burimi:     habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

    \u0414\u0432\u0443\u0445\u0444\u0430\u043a\u0442\u043e\u0440\u0430\u044f \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u044f \u0412\u0441\u0451 \u043f\u0440\u043e\u0447\u0438\u0442\u0430\u043d\u043d\u043e\u0435 \u0432\u0430\u043c\u0438 \u0432 \u043f\u0435\u0440\u0432\u043e\u0439 \u0447\u0430\u0441\u0442\u0438 \u043a\u0430\u0441\u0430\u043b\u043e\u0441\u044c \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043d\u0430 \u043e\u0441\u043d\u043e\u0432\u0430\u043d\u0438\u0438 \u0442\u043e\u0433\u043e, \u0447\u0442\u043e \u0437\u043d\u0430\u0435\u0442 \u0437\u0430\u043f\u0440\u0430\u0448\u0438\u0432\u0430\u044e\u0449\u0438\u0439. \u041e\u043d \u0437\u043d\u0430\u0435\u0442 \u0441\u0432\u043e\u0439 \u0430\u0434\u0440\u0435\u0441 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u043d\u043d\u043e\u0439 \u043f\u043e\u0447\u0442\u044b, \u0437\u043d\u0430\u0435\u0442, \u043a\u0430\u043a \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c \u043a \u043d\u0435\u0439 \u0434\u043e\u0441\u0442\u0443\u043f (\u0442.\u0435. \u0437\u043d\u0430\u0435\u0442 \u0441\u0432\u043e\u0439 \u043f\u0430\u0440\u043e\u043b\u044c \u043e\u0442 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u043d\u043d\u043e\u0439 \u043f\u043e\u0447\u0442\u044b) \u0438 \u0437\u043d\u0430\u0435\u0442 \u043e\u0442\u0432\u0435\u0442\u044b \u043d\u0430 \u0441\u0435\u043a\u0440\u0435\u0442\u043d\u044b\u0435 \u0432\u043e\u043f\u0440\u043e\u0441\u044b. \u00ab\u0417\u043d\u0430\u043d\u0438\u0435\u00bb \u0441\u0447\u0438\u0442\u0430\u0435\u0442\u0441\u044f \u043e\u0434\u043d\u0438\u043c \u0444\u0430\u043a\u0442\u043e\u0440\u043e\u043c \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438; \u0434\u0432\u0443\u043c\u044f \u0434\u0440\u0443\u0433\u0438\u043c\u0438 \u0440\u0430\u0441\u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0451\u043d\u043d\u044b\u043c\u0438 \u0444\u0430\u043a\u0442\u043e\u0440\u0430\u043c\u0438 \u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u0442\u043e, \u0447\u0442\u043e \u0443 \u0432\u0430\u0441 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":97640,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-97639","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Gjith\u00e7ka q\u00eb d\u00ebshironi t\u00eb dini p\u00ebr rivendosjen e sigurt t\u00eb fjal\u00ebkalimeve. Pjesa 2 | ProHoster","description":"Dyfaktori i autenticitetit. \u00c7do gj\u00eb q\u00eb keni lexuar n\u00eb pjes\u00ebn e par\u00eb ka t\u00eb b\u00ebj\u00eb me identifikimin bazuar n\u00eb at\u00eb q\u00eb e di k\u00ebrkuesi. Ai e di adres\u00ebn e tij t\u00eb emailit, di si t\u00eb qasje n\u00eb t\u00eb (dmth. e di fjal\u00ebkalimin e tij t\u00eb emailit) dhe di p\u00ebrgjigjet p\u00ebr pyetje sekrete. \u2018Dija\u2019 konsiderohet si nj\u00eb faktor autentikimi; dy faktor\u00eb t\u00eb tjer\u00eb t\u00eb zakonsh\u00ebm jan\u00eb q\u00eb ju keni","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/vsyo-chto-vy-hoteli-znat-o-bezopasnom-sbrose-parolej-chast-2","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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\u0412\u0441\u0451, \u0447\u0442\u043e \u0432\u044b \u0445\u043e\u0442\u0435\u043b\u0438 \u0437\u043d\u0430\u0442\u044c \u043e \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u043c \u0441\u0431\u0440\u043e\u0441\u0435 \u043f\u0430\u0440\u043e\u043b\u0435\u0439. \u0427\u0430\u0441\u0442\u044c 2 | ProHoster","og:description":"\u0414\u0432\u0443\u0445\u0444\u0430\u043a\u0442\u043e\u0440\u0430\u044f \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u044f \u0412\u0441\u0451 \u043f\u0440\u043e\u0447\u0438\u0442\u0430\u043d\u043d\u043e\u0435 \u0432\u0430\u043c\u0438 \u0432 \u043f\u0435\u0440\u0432\u043e\u0439 \u0447\u0430\u0441\u0442\u0438 \u043a\u0430\u0441\u0430\u043b\u043e\u0441\u044c \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438 \u043d\u0430 \u043e\u0441\u043d\u043e\u0432\u0430\u043d\u0438\u0438 \u0442\u043e\u0433\u043e, \u0447\u0442\u043e \u0437\u043d\u0430\u0435\u0442 \u0437\u0430\u043f\u0440\u0430\u0448\u0438\u0432\u0430\u044e\u0449\u0438\u0439. \u041e\u043d \u0437\u043d\u0430\u0435\u0442 \u0441\u0432\u043e\u0439 \u0430\u0434\u0440\u0435\u0441 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u043d\u043d\u043e\u0439 \u043f\u043e\u0447\u0442\u044b, \u0437\u043d\u0430\u0435\u0442, \u043a\u0430\u043a \u043f\u043e\u043b\u0443\u0447\u0438\u0442\u044c \u043a \u043d\u0435\u0439 \u0434\u043e\u0441\u0442\u0443\u043f (\u0442.\u0435. \u0437\u043d\u0430\u0435\u0442 \u0441\u0432\u043e\u0439 \u043f\u0430\u0440\u043e\u043b\u044c \u043e\u0442 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u043d\u043d\u043e\u0439 \u043f\u043e\u0447\u0442\u044b) \u0438 \u0437\u043d\u0430\u0435\u0442 \u043e\u0442\u0432\u0435\u0442\u044b \u043d\u0430 \u0441\u0435\u043a\u0440\u0435\u0442\u043d\u044b\u0435 \u0432\u043e\u043f\u0440\u043e\u0441\u044b. \u00ab\u0417\u043d\u0430\u043d\u0438\u0435\u00bb \u0441\u0447\u0438\u0442\u0430\u0435\u0442\u0441\u044f \u043e\u0434\u043d\u0438\u043c \u0444\u0430\u043a\u0442\u043e\u0440\u043e\u043c \u0430\u0443\u0442\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0446\u0438\u0438; \u0434\u0432\u0443\u043c\u044f \u0434\u0440\u0443\u0433\u0438\u043c\u0438 \u0440\u0430\u0441\u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0451\u043d\u043d\u044b\u043c\u0438 \u0444\u0430\u043a\u0442\u043e\u0440\u0430\u043c\u0438 \u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u0442\u043e, \u0447\u0442\u043e \u0443 \u0432\u0430\u0441","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/vsyo-chto-vy-hoteli-znat-o-bezopasnom-sbrose-parolej-chast-2","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-10-20T00:42:56+00:00","article:modified_time":"2020-10-20T00:42:56+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"97639","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 10:16:25","updated":"2022-10-03 07:14:42"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/97639","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=97639"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/97639\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/97640"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=97639"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=97639"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=97639"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}