Kyauta Mai Ƙirƙirar Hash

Yadda Yake Aiki

Ƙirƙirar hash yana gudana gaba ɗaya a burauzarka ta amfani da haɗin Web Crypto API (don SHA-1, SHA-256, SHA-384, da SHA-512) da aiwatarwa da aka rubuta da hannu na MD5 da CRC32 — saboda Web Crypto API da gangan ba ya ƙunshi duk waɗannan tsoffin algorithm biyu. Ba a taɓa loda abin da ke ciki na rubutu ko fayil zuwa ko'ina ba.

1. 1
   Ana karanta shigarwa zuwa bytes

   Don shigarwar rubutu, TextEncoder na burauza da aka gina yana canja harafin zuwa jerin byte na UTF-8. Don fayiloli har zuwa 500 MB, hanyar arrayBuffer() na File API tana karanta bayanan binary danye kai tsaye zuwa ƙwaƙwalwa — fayil ɗin ba ya taɓa barin na'urarka ba.
2. 2
   Algorithm shida suna gudana a layi ɗaya

   Ana ba SHA-1, SHA-256, SHA-384, da SHA-512 zuwa crypto.subtle.digest(), aiwatarwar WebCrypto na asali na burauza. Ana lissafta MD5 ta wata aiwatarwar RFC 1321 mai zaman kanta wadda aka gina cikin kayan aikin (WebCrypto da gangan ba ya ƙunshi MD5); don manyan shigarwa yana ba da damar aikin taron kowace 4 MB don tab din ya ci gaba da amsawa. CRC32 yana amfani da wani tebur bincike na shigarwa 256 na IEEE 802.3 da aka riga aka lissafta don sarrafa byte-bayan-byte mai sauri.
3. 3
   Ana nuna digests na hex yayin da suke gamawa

   Ana rubuta sakamakon kowane algorithm zuwa UI nan take da yake warwarewa — algorithm masu sauri kamar CRC32 suna bayyana kusan nan take yayin da SHA-512 a kan babban fayil na iya ɗaukar ɗan lokaci fiye. Duk shida suna gudana lokaci guda ta Promise.all, don haka jimlar lokacin jira ana tantance shi ta mafi hankakin algorithm, ba jimlarsu ba.
4. 4
   Tabbatarwar checksum na zaɓi

   Manna sanannen checksum a filin tabbatarwa kuma kayan aikin yana kwatanta shi da dukkan digests shida da aka lissafta. Yana gano kai tsaye wanne algorithm ya dace (ko ya kamata ya dace) ta ƙidaya haruffan hex — haruffa 32 yana nuna MD5, 40 yana nuna SHA-1, 64 yana nuna SHA-256, da sauransu — sannan yana ba da rahoton dacewa, rashin dacewa, ko tsawon da ba a sani ba.

Kayan Aiki Masu Alaƙa