{"id":55510,"date":"2020-01-22T00:00:00","date_gmt":"2020-01-21T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/linux-udalenie-pula-blokirovok-dev-random"},"modified":"2020-02-18T14:03:38","modified_gmt":"2020-02-18T11:03:38","slug":"linux-udalenie-pula-blokirovok-dev-random","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/linux-udalenie-pula-blokirovok-dev-random","title":{"rendered":"Linux: eliminarea unui pool de blocare \/dev\/random","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Dup\u0103 cum se \u0219tie, \/dev\/random, un generator de numere aleatoare criptografic securizate (CSPRNG), are o problem\u0103 nepl\u0103cut\u0103 - bloc\u0103rile. \u00cen acest articol, se discut\u0103 despre cum poate fi rezolvat\u0103 aceast\u0103 problem\u0103. <\/p>\n

\u00cen ultimele c\u00e2teva luni, metodele de generare a numerelor aleatoare din kernel au fost pu\u021bin revizuite, dar problemele din acest subsistem au fost abordate pe o perioad\u0103 mai lung\u0103. timp.<\/a><\/noindex>Cele mai recent modific\u0103ri<\/a><\/noindex> au fost f\u0103cute cu scopul de a preveni blocarea prelungit\u0103 a apelului de sistem getrandom() la \u00eenc\u0103rcarea sistemului, dar cauza de baz\u0103 a fost comportamentul blocant al rezervorului de numere aleatoare. O actualizare recent\u0103 ar fi eliminat acest rezervor, iar se a\u0219tepta ca aceasta s\u0103 fie direc\u021bionat\u0103 c\u0103tre kernelul principal. <\/p>\n

Andy Lutomirski a publicat a treia versiune a patch-ului la sf\u00e2r\u0219itul lunii decembrie. Acesta face \u201edou\u0103 modific\u0103ri semantice de baz\u0103 \u00een API-urile aleatoare ale Linux\u201d<\/i>. Patch-ul adaug\u0103 un nou flag GRND_INSECURE la apelul de sistem getrandom() (de\u0219i Lutomirski se refer\u0103 la el ca getentropy(), care este implementat \u00een glibc prin getrandom() cu flag-uri fixe); acest flag determin\u0103 apelul s\u0103 returneze \u00eentotdeauna cantitatea de date solicitate, f\u0103r\u0103 a garanta c\u0103 acestea sunt aleatoare. Kernelul va face tot posibilul s\u0103 ofere cele mai bune date aleatoare de care dispune \u00een acel moment. \u201eProbabil cel mai bine pe care putem s\u0103-l facem este s\u0103-l numim 'INSECURE' (nesigur), pentru a \u00eempiedica utilizarea acestui API pentru lucruri care au nevoie de securitate.\u201d<\/i> (nesigur), pentru a preveni utilizarea acestui API pentru lucruri care necesit\u0103 securitate.<\/a><\/noindex><\/p>\n

Patch-urile elimin\u0103 de asemenea rezervorul blocant. \u00cen prezent, kernelul men\u021bine dou\u0103 rezervoruri de date aleatoare, unul corespunz\u00e2nd \/dev\/random \u0219i cel\u0103lalt - \/dev\/urandom, a\u0219a cum este descris \u00een aceast\u0103 pe care l-a\u021bi citit<\/a><\/noindex> 2015. Rezervorul blocant este rezervorul pentru \/dev\/random; citirea pentru acest dispozitiv va fi blocat\u0103 (a\u0219a cum sugereaz\u0103 numele) p\u00e2n\u0103 c\u00e2nd din sistem a fost colectat\u0103 o 'suficient\u0103' entropie pentru a satisface cererea. \u00cen continuare, citirile din acest fi\u0219ier sunt de asemenea blocate, dac\u0103 rezervorul nu con\u021bine suficient\u0103 entropie. <\/p>\n

Eliminarea piscinei de blocare \u00eenseamn\u0103 c\u0103 citirea din \/dev\/random se comport\u0103 ca getrandom() cu valoarea flags zero (\u0219i transform\u0103 flagul GRND_RANDOM \u00een noop). Dup\u0103 ini\u021bializarea generatorului criptografic de numere aleatorii (CRNG), citirea din \/dev\/random \u0219i apelurile getrandom(…,0) nu vor bloca \u0219i vor returna cantitatea solicitat\u0103 de date aleatorii.<\/p>\n

Lutomirski spune: \u201eConsider c\u0103 pool-ul de blocare Linux \u0219i-a consumat existen\u021ba. CRNG Linux genereaz\u0103 ie\u0219iri care sunt suficient de bune pentru a fi utilizate chiar \u0219i pentru generarea de chei. Pool-ul de blocare nu este mai puternic \u00een niciun sens semnificativ, iar pentru men\u021binerea sa este nevoie de mult\u0103 infrastructur\u0103 de valoare discutabil\u0103.\u201d <\/i><\/p>\n

Modific\u0103rile au fost f\u0103cute cu scopul de a se asigura c\u0103 programele existente nu vor suferi, iar de fapt, problemele cu a\u0219teptarea \u00eendelungat\u0103 pentru lucruri precum generarea cheilor GnuPG vor deveni mai pu\u021bin frecvente.<\/p>\n

\u201eAceste serii nu ar trebui s\u0103 afecteze niciun program existent. \/dev\/urandom r\u0103m\u00e2ne neschimbat. \/dev\/random este \u00eenc\u0103 blocat imediat dup\u0103 \u00eenc\u0103rcare, dar se blocheaz\u0103 mai pu\u021bin dec\u00e2t \u00eenainte. getentropy() cu flag-uri existente va returna un rezultat care va fi la fel de adecvat pentru scopuri practice ca \u0219i \u00eenainte.\u201d<\/i> <\/p>\n

Lutomirski a subliniat c\u0103 r\u0103m\u00e2ne deschis\u0103 \u00eentrebarea dac\u0103 nucleul ar trebui s\u0103 furnizeze a\u0219a-numitele \u201enumere aleatoare adev\u0103rate\u201d, ceea ce \u00eentr-o anumit\u0103 m\u0103sur\u0103 trebuia s\u0103 fac\u0103 pool-ul de blocare. El vede \u00een asta un singur motiv: \u201erespectarea standardelor guvernamentale\u201d. Lutomirski a sugerat c\u0103, dac\u0103 nucleul trebuie s\u0103 asigure acest lucru, atunci ar trebui s\u0103 fie realizat printr-o interfa\u021b\u0103 complet diferit\u0103 sau ar trebui mutat \u00een spa\u021biul utilizatorului, oferindu-i posibilitatea de a extrage mostre brute de evenimente care pot fi utilizate pentru a crea un astfel de pool de blocare. <\/p>\n

Stephan M\u00fcller a sugerat c\u0103 setul s\u0103u de patch-uri<\/a><\/noindex> generatorul de numere aleatorii Linux (LRNG) (\u00een prezent a fost lansat\u0103 versiunea 26) poate fi o modalitate de a furniza numere aleatorii adev\u0103rate pentru aplica\u021biile care au nevoie de acestea. LRNG este \u201ecomplet conform cerin\u021belor \u201eRecomand\u0103rilor privind sursele de entropie utilizate pentru generarea de bi\u021bi aleatori\u201d SP800-90B\u201d, ceea ce \u00eel face o solu\u021bie pentru problemele standardelor de stat.
\nMatthew Garrett a contestat termenul \u201edate aleatorii adev\u0103rate\u201d, subliniind c\u0103 dispozitivele alese pot fi, \u00een principiu, modelate suficient de precis pentru a le face previzibile: \u201enoi nu selec\u021bion\u0103m aici evenimente cuantice\u201d.<\/p>\n

M\u00fcller a r\u0103spuns c\u0103 acest termen provine din standardul german AIS 31 pentru descrierea generatorului de numere aleatorii, care pur \u0219i simplu produce rezultate \u201ecu aceea\u0219i vitez\u0103 cu care sursa de zgomot de baz\u0103 produce entropie\u201d. <\/p>\n

Pe l\u00e2ng\u0103 ne\u00een\u021belegerile terminologiei, prezen\u021ba unui pool de blocare, a\u0219a cum este sugerat de patch-urile LRNG, va duce pur \u0219i simplu la diverse probleme, mai ales dac\u0103 este accesibil f\u0103r\u0103 privilegii. <\/p>\n

A\u0219a cum a spus Lutomski: \u201eAcest lucru nu rezolv\u0103 problema. Dac\u0103 doi utilizatori diferi\u021bi ruleaz\u0103 programe stupide, cum ar fi gnupg, se vor epuiza unul pe cel\u0103lalt. V\u0103d c\u0103 \u00een prezent exist\u0103 dou\u0103 probleme principale cu \/dev\/random: este predispus la DoS (adic\u0103 epuizarea resurselor, influen\u021be d\u0103un\u0103toare sau ceva de genul acesta), \u0219i, din moment ce nu sunt necesare privilegii pentru utilizarea lui, este de asemenea predispus la abuzuri. Gnupg este gre\u0219it, este un colaps complet. Dac\u0103 ad\u0103ug\u0103m o nou\u0103 interfa\u021b\u0103 neprivilegiat\u0103, care va fi utilizat\u0103 de gnupg \u0219i programe similare, vom pierde din nou.\u201d<\/i> <\/p>\n

M\u00fcller a men\u021bionat c\u0103 ad\u0103ugarea getrandom() va permite acum GnuPG s\u0103 foloseasc\u0103 aceast\u0103 interfa\u021b\u0103, deoarece va asigura garan\u021bia necesar\u0103 c\u0103 pool-ul a fost ini\u021bializat. Pe baza discu\u021biilor cu dezvoltatorul GnuPG Werner Koch, M\u00fcller consider\u0103 c\u0103 garan\u021bia este singura cauz\u0103 pentru care GnuPG cite\u0219te \u00een prezent direct din \/dev\/random. Dar dac\u0103 exist\u0103 o interfa\u021b\u0103 neprivilegiat\u0103, care este predispus\u0103 la atacuri de tip denial of service (a\u0219a cum este \/dev\/random \u00een prezent), atunci, conform lui Lutomski, aceasta va fi utilizat\u0103 necorespunz\u0103tor de unele aplica\u021bii. <\/p>\n

Teodor Tsao (Theodore Yue Tak Ts’o), dezvoltatorul subsistemului de numere aleatorii Linux, pare s\u0103 fi schimbat p\u0103rerea cu privire la necesitatea unei piscine de blocare. El a spus c\u0103 eliminarea acestei piscine va permite s\u0103 sc\u0103p\u0103m eficient de ideea c\u0103 Linux are un generator adev\u0103rat de numere aleatorii (TRNG): \u201enu este o nebunie, deoarece acesta este exact ceea ce au f\u0103cut \u00eentotdeauna *BSD\".<\/i><\/p>\n

De asemenea, el este \u00eengrijorat c\u0103 furnizarea unui mecanism TRNG va servi doar ca momeal\u0103 pentru dezvoltatorii de aplica\u021bii \u0219i consider\u0103 c\u0103, av\u00e2nd \u00een vedere diferitele tipuri de hardware acceptate de Linux, este imposibil s\u0103 garantezi TRNG \u00een nucleu. Problema nu va fi rezolvat\u0103 nici m\u0103car de posibilitatea de a lucra cu hardware-ul doar pe baza privilegiilor de root: \u201eDezvoltatorii aplica\u021biilor indic\u0103 faptul c\u0103 aplica\u021bia lor, din motive de securitate, trebuie s\u0103 fie instalat\u0103 ca root, deoarece astfel pute\u021bi ob\u021bine acces la \u201ecu adev\u0103rat bune\u201d numere aleatorii\".<\/i><\/p>\n

M\u00fcller a \u00eentrebat dac\u0103 Tsao a renun\u021bat la implementarea pool-ului de blocare, pe care el \u00eensu\u0219i l-a propus acum mult timp. Tsao a r\u0103spuns c\u0103 pl\u0103nuie\u0219te s\u0103 aplice patch-urile lui Lutomski \u0219i se opune cu fermitate relu\u0103rii interfe\u021bei de blocare \u00een nucleu. <\/p>\n

\u201eNucleul nu poate oferi nicio garan\u021bie cu privire la faptul c\u0103 sursa de zgomot a fost caracterizat\u0103 corect. Singurul lucru pe care \u00eel poate ob\u021bine dezvoltatorul GPG sau OpenSSL este o senza\u021bie vag\u0103 c\u0103 TRUERANDOM este \u201emai bun\u201d, iar deoarece doresc mai mult\u0103 securitate, cu siguran\u021b\u0103 vor \u00eencerca s\u0103-l utilizeze. La un moment dat, se va bloca, iar c\u00e2nd un alt utilizator inteligent (poate un specialist \u00een distribu\u021bie) \u00eel va introduce \u00een scriptul init, sistemele se vor opri \u0219i utilizatorilor nu le va r\u0103m\u00e2ne dec\u00e2t s\u0103 se pl\u00e2ng\u0103 lui Linus Torvalds\u201d.<\/i> <\/p>\n

Tsao pledeaz\u0103, de asemenea, pentru a oferi criptografilor \u0219i celor care au cu adev\u0103rat nevoie de TRNG o modalitate de a-\u0219i colecta propria entropie \u00een spa\u021biul utilizatorului, pentru a o folosi dup\u0103 bunul plac. El spune c\u0103 procesul de colectare a entropiei nu este unul pe care nucleul s\u0103-l poat\u0103 realiza pe toate tipurile de hardware pe care le accept\u0103, \u00een plus, nucleul \u00eensu\u0219i nu poate evalua cantitatea de entropie furnizat\u0103 de diverse surse. <\/p>\n

\u201eNucleul nu ar trebui s\u0103 amestece diferite surse de zgomot, \u0219i, desigur, nu ar trebui s\u0103 \u00eencerce s\u0103 afirme c\u0103 \u0219tie c\u00e2te bi\u021bi de entropie prime\u0219te atunci c\u00e2nd \u00eencearc\u0103 s\u0103 joace un fel de \u201ejoc zgomotos de entropie\u201d pe o arhitectur\u0103 CPU simpl\u0103 la maximum pentru cazurile de utilizare IoT\/Embedded, c\u00e2nd totul este desincronizat cu un singur generator master, atunci c\u00e2nd nu exist\u0103 instruc\u021biuni CPU pentru a reorganiza sau redenumi registrele etc.\u201c.<\/p>\n

\u201eSe poate vorbi despre furnizarea unor instrumente care \u00eencearc\u0103 s\u0103 fac\u0103 aceste calcule, dar astfel de lucruri ar trebui s\u0103 fie realizate pe echipamentul fiec\u0103rui utilizator, ceea ce pentru majoritatea utilizatorilor distribuitorului este pur \u0219i simplu nepractic. Dac\u0103 \u00eens\u0103 aceasta este destinat\u0103 doar criptografilor, atunci s\u0103 se fac\u0103 \u00een spa\u021biul lor utilizator. \u0218i s\u0103 nu simplific\u0103m GPG, OpenSSL etc., pentru ca toat\u0103 lumea s\u0103 zic\u0103: \u201evrem \u201everitabil\u0103 aleatorie\u201d \u0219i nu ne mul\u021bumim cu mai pu\u021bin\u201d. Se poate discuta despre modul \u00een care le oferim criptografilor interfe\u021be astfel \u00eenc\u00e2t s\u0103 poat\u0103 ob\u021bine informa\u021biile necesare datorit\u0103 accesului la sursele primare de zgomot, separate \u0219i denumite, \u0219i, poate, c\u0103 \u00eentr-un fel sursa de zgomot se va putea autentifica \u00een bibliotec\u0103 sau \u00een aplica\u021bia din spa\u021biul utilizatorului.\u201c.<\/i><\/p>\n

A avut loc o mic\u0103 discu\u021bie despre cum ar putea ar\u0103ta o astfel de interfa\u021b\u0103, deoarece, de exemplu, pentru unele evenimente ar putea exista consecin\u021be \u00een ceea ce prive\u0219te securitatea. Cao a subliniat c\u0103 codurile de scanare a tastaturii (adic\u0103 a tastelor ap\u0103sate) se amestec\u0103 \u00een pool ca parte a colect\u0103rii entropiei: \u201eMutarea acestui lucru \u00een spa\u021biul utilizatorului, chiar \u0219i printr-un apel de sistem privilegiat, ar fi, cel pu\u021bin, imprudent\u201d. Este foarte posibil ca \u0219i alte timpi de evenimente s\u0103 poat\u0103 crea o scurgere de informa\u021bii prin canale secundare. <\/p>\n

Astfel, se creeaz\u0103 senza\u021bia c\u0103 problema de lung\u0103 durat\u0103 a subsistemului de numere aleatorii din Linux este pe calea de a fi rezolvat\u0103. Modific\u0103rile pe care subsistemul de numere aleatorii le-a suferit recent au dus \u00een realitate doar la probleme DoS \u00een timpul utiliz\u0103rii sale. Acum, \u00eens\u0103, au ap\u0103rut metode eficiente de a ob\u021bine cele mai bune numere aleatorii pe care nucleul le poate oferi. Dac\u0103 TRNG este \u00een continuare dorit pentru Linux, aceast\u0103 lips\u0103 va trebui rezolvat\u0103 \u00een viitor, dar, cel mai probabil, nu se va face \u00een interiorul nucleului \u00een sine. <\/p>\n

Pu\u021bin publicitate \ud83d\ude42<\/h3>\n

\nMul\u021bumim c\u0103 r\u0103m\u00e2ne\u021bi cu noi. V\u0103 plac articolele noastre? Dori\u021bi s\u0103 vede\u021bi mai multe materiale interesante? Sus\u021bine\u021bi-ne, efectu\u00e2nd o comand\u0103 sau recomand\u00e2ndu-ne prietenilor, VPS cloud pentru dezvoltatori de la 4,99 $<\/a><\/noindex>, un echivalent unic pentru serverele entry-level, care a fost creat de noi pentru voi:<\/b> Toat\u0103 adev\u0103rul despre VPS (KVM) E5-2697 v3 (6 nuclee) 10GB DDR4 480GB SSD 1Gbps de la 19 $ sau cum s\u0103 \u00eemp\u0103r\u021bi\u021bi corect un server?<\/a><\/noindex> (sunt disponibile op\u021biuni cu RAID1 \u0219i RAID10, p\u00e2n\u0103 la 24 nuclee \u0219i p\u00e2n\u0103 la 40GB DDR4).<\/p>\n

Dell R730xd la jum\u0103tate de pre\u021b \u00een centrul de date Equinix Tier IV din Amsterdam?<\/b> Numai la noi 2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB de la 199 $<\/a><\/noindex> \u00een Olanda! Dell R420 \u2014 2x E5-2430 2.2Ghz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 de la 99 $!<\/b><\/b> Citi\u021bi despre Cum s\u0103 construi\u021bi o infrastructur\u0103 de clas\u0103 enterprise folosind servere Dell R730xd E5-2650 v4 la pre\u021buri foarte mici de 9000 \u20ac?<\/a><\/noindex>
\n
Sursa: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u041a\u0430\u043a \u0438\u0437\u0432\u0435\u0441\u0442\u043d\u043e, \u0443 \/dev\/random, \u043a\u0440\u0438\u043f\u0442\u043e\u0433\u0440\u0430\u0444\u0438\u0447\u0435\u0441\u043a\u0438 \u0441\u0442\u043e\u0439\u043a\u043e\u0433\u043e \u0433\u0435\u043d\u0435\u0440\u0430\u0442\u043e\u0440\u0430 \u043f\u0441\u0435\u0432\u0434\u043e\u0441\u043b\u0443\u0447\u0430\u0439\u043d\u044b\u0445 \u0447\u0438\u0441\u0435\u043b (CSPRNG), \u0438\u043c\u0435\u0435\u0442\u0441\u044f \u043e\u0434\u043d\u0430 \u043d\u0435\u043f\u0440\u0438\u044f\u0442\u043d\u0430\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u2013 \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u043a\u0438. \u0412 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f, \u043a\u0430\u043a\u0438\u043c \u043e\u0431\u0440\u0430\u0437\u043e\u043c \u043c\u043e\u0436\u043d\u043e \u0435\u0435 \u0440\u0435\u0448\u0438\u0442\u044c. \u0417\u0430 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0435 \u043d\u0435\u0441\u043a\u043e\u043b\u044c\u043a\u043e \u043c\u0435\u0441\u044f\u0446\u0435\u0432 \u0441\u0440\u0435\u0434\u0441\u0442\u0432\u0430 \u0433\u0435\u043d\u0435\u0440\u0430\u0446\u0438\u0438 \u0441\u043b\u0443\u0447\u0430\u0439\u043d\u044b\u0445 \u0447\u0438\u0441\u0435\u043b \u0432 \u044f\u0434\u0440\u0435 \u0431\u044b\u043b\u0438 \u043d\u0435\u043c\u043d\u043e\u0433\u043e \u043f\u0435\u0440\u0435\u0440\u0430\u0431\u043e\u0442\u0430\u043d\u044b, \u043d\u043e \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0432 \u044d\u0442\u043e\u0439 \u043f\u043e\u0434\u0441\u0438\u0441\u0442\u0435\u043c\u0435 \u0440\u0435\u0448\u0430\u043b\u0438\u0441\u044c \u043d\u0430 \u043f\u0440\u043e\u0442\u044f\u0436\u0435\u043d\u0438\u0438 \u0431\u043e\u043b\u0435\u0435 \u0448\u0438\u0440\u043e\u043a\u0438\u0445 \u0432\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0445 \u0440\u0430\u043c\u043e\u043a. \u0421\u0430\u043c\u044b\u0435 \u043f\u043e\u0441\u043b\u0435\u0434\u043d\u0438\u0435 \u0438\u0437\u043c\u0435\u043d\u0435\u043d\u0438\u044f \u0431\u044b\u043b\u0438 \u0441\u0434\u0435\u043b\u0430\u043d\u044b […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-55510","post","type-post","status-publish","format-standard","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\udd47Linux: eliminarea grupului de blocare \/dev\/random | ProHoster","description":"Dup\u0103 cum se \u0219tie, \/dev\/random, un generator de numere aleatoare criptografic securizate (CSPRNG), are o problem\u0103 nepl\u0103cut\u0103 - bloc\u0103rile. \u00cen acest articol, se discut\u0103 despre cum poate fi rezolvat\u0103 aceast\u0103 problem\u0103.","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/linux-udalenie-pula-blokirovok-dev-random","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\udd47Linux: \u0443\u0434\u0430\u043b\u0435\u043d\u0438\u0435 \u043f\u0443\u043b\u0430 \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u043e\u043a \/dev\/random | ProHoster","og:description":"\u041a\u0430\u043a \u0438\u0437\u0432\u0435\u0441\u0442\u043d\u043e, \u0443 \/dev\/random, \u043a\u0440\u0438\u043f\u0442\u043e\u0433\u0440\u0430\u0444\u0438\u0447\u0435\u0441\u043a\u0438 \u0441\u0442\u043e\u0439\u043a\u043e\u0433\u043e \u0433\u0435\u043d\u0435\u0440\u0430\u0442\u043e\u0440\u0430 \u043f\u0441\u0435\u0432\u0434\u043e\u0441\u043b\u0443\u0447\u0430\u0439\u043d\u044b\u0445 \u0447\u0438\u0441\u0435\u043b (CSPRNG), \u0438\u043c\u0435\u0435\u0442\u0441\u044f \u043e\u0434\u043d\u0430 \u043d\u0435\u043f\u0440\u0438\u044f\u0442\u043d\u0430\u044f \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u2013 \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u043a\u0438. \u0412 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f, \u043a\u0430\u043a\u0438\u043c \u043e\u0431\u0440\u0430\u0437\u043e\u043c \u043c\u043e\u0436\u043d\u043e \u0435\u0435 \u0440\u0435\u0448\u0438\u0442\u044c.","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/linux-udalenie-pula-blokirovok-dev-random","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-01-21T21:00:00+00:00","article:modified_time":"2020-02-18T11:03:38+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"55510","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 19:43:30","updated":"2022-10-02 22:01:02","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/55510","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=55510"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/55510\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=55510"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=55510"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=55510"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}