Tabbatar da Sarrafa Password a Banki na Kamfanoni: Hashing Mai Algorithms da yawa da Haɓakawa tare da hsh

Taƙaitaccen bayanin gudanarwa. Tabbatar da gaskiya na banki da aka gina kan samfurin barazana na 2018 ba ya dacewa da manufa a ƙarƙashin tsarin doka na 2026 ba. Fashin GPU-accelerated, yawan ASIC, da kusancin sararin post-quantum sun rushe iyakar aminci na PBKDF2 da scrypt na farkon ma'auni; Mataki na 5 na DORA ya juya wannan ruɓewa zuwa alhaki da hukumar ta hau alhakinsa. hsh, tari na open-source pure-Rust, yana magance matsalar a matakai uku kafada da kafada: dispatcher na verify_and_upgrade da ke sake-hash shaidar da aka adana zuwa ma'aunin Argon2id na yanzu kan kowace shiga mai nasara ba tare da taga kiyayewa ba; laushin peppering da HSM- ko KMS-interlocked yake da shi wanda ke sa cin amana na database kawai bai samar da komai mai fasawa ba; da jerin samar da kayayyaki mai aminci na ƙwaƙwalwa wanda ke kawar da farfajiyar harin foreign-function-interface na asali ga tarukan cryptography na C-backed. Sakamakon shine tushen da ke biyan DORA, horon haɗarin aiki na Basel III, alhakin manyan manajoji na SM&CR, da sararin ƙaura na post-quantum na NIST IR 8547 — ba tare da shirin sake-saiti mai yawa da tarihi ya buƙata don haɓaka gidan tabbatar da gaskiya ba.

Mafi yawan tabbatar da gaskiya na banki na kamfanoni har yanzu ya dogara da laushin password da aka taurara zuwa samfurin barazana na 2018. Kayan aikin da ke karya shi sun ci gaba. Yayin da gonakin GPU ke faɗaɗa kuma kwamfutoci na quantum masu mahimmancin cryptography (CRQCs) ke kusantowa, hashing na gado — PBKDF2, scrypt na farko — yana ruɓewa a cikin kowace awa na ƙididdiga da maharan ke kashewa a layin fashin offline. Ruɓewar tana shiru: babu abin da ke cikin database na samarwa ya gaya maka cewa hash ɗin da ya kasance mai ƙarfi jiya ba haka ba ne yanzu.

A ƙarƙashin Dokar Juriya ta Aiki ta Dijital (DORA), barin tsoffin kadarorin cryptography da ba a juya ba a samarwa ba bashi na fasaha ba ne yanzu. Alhakin doka ne da aka ambata.

hsh yana rufe gibin. Tari na pure-Rust ne, yana sarrafa nau'ikan hash da yawa kafada da kafada kuma yana haɓaka shaidun masu rauni a tashi yayin zaman shiga mai aiki. Tsarin tabbatar da gaskiya yana daidaitawa zuwa umarnin juriya na 2026 ba tare da taga kiyayewa ba, ba tare da turbiya na tilas ba, ba tare da daƙiƙa ɗaya na lokacin sauke ba.

01. Matsalar Ruɓewar Cryptography a Banki

Don fahimtar buƙatar tari kamar hsh, dole ne mutum ya fahimci tsawon rayuwar password hash. Algorithms ba sa tsufa cikin alheri; suna ruɓewa dangane da kayan aikin da ake samu don karya su.

Gibin saurin ASIC/GPU. Algorithms kamar PBKDF2 an ƙera su don zama masu tsada ga CPUs. Yau, maharan suna amfani da GPUs masu daidaitawa sosai don aiwatar da harin ƙamus na offline. Tsohuwar hash da aka samar a 2018 ta fi rauni sosai a kan maƙiyi na 2026.

Haɗarin ƙaurar big-bang. Lokacin da CISO ya yanke shawarar haɓaka daga PBKDF2 zuwa algorithm mai ƙarfin ƙwaƙwalwa kamar Argon2id, ba zai iya juya hashes don sake encrypt ɗin su ba. Mafita na gargajiya — tilasta turbiya na password na masu amfani miliyoyi — yana haifar da matsi mai yawa na abokan ciniki da haɗarin aiki.

Jerin samar da C-library. A tarihi, middleware na banki ya dogara ga libraries kamar argonautica ko ɗanyen C bindings don hashing. Waɗannan libraries suna ɗauke da haɗarin jerin samar da kayayyaki na ɓoye: buffer overflow ɗaya na ƙwaƙwalwa a cikin sashin tabbatar da gaskiya na iya haifar da remote code execution (RCE) a layin mafi ƙwararru na tarin banki.

Kwatancen algorithm — juriya na kayan aiki da farfajiyar daidaitawa

Algorithms guda uku da bankin zai gamu da su a aikace a cikin tarin ƙaura sun bambanta ƙasa da zaɓin primitive na cryptography kuma fiye da yadda suke tsufa a ƙarƙashin matsi na kayan aiki. Tebur ɗin da ke ƙasa ya taƙaita matsayin aikace-aikace.

Abin da za a ɗauka don tsarin ƙaura kunkuntar ne: PBKDF2 wani yanayi ne na verify-side, ba write-side makoma ba. Kowace shiga mai nasara akan rikodin PBKDF2 ya kamata ya samar da rikodin Argon2id a fitar.

02. Tabaron Gine-ginen hsh na 2026

An tsara tari a cikin laushi na asali biyar, kowanne an ƙera shi don rage takamaiman nau'in haɗari na aiki.

Teburi 1: Laushi na gine-ginen hsh da rage haɗari

03. Hanyar Sake Hashing Ba tare da Lokacin Sauke ba

Tsarin verify_and_upgrade yana magance ƙaurar bayanai ta hanyar tsarin dispatching mai hankali, mai sane da yanayi wanda ke buƙatar sifili na lokacin sauke database.

Lokacin da mai amfani ya gabatar da shaidunsa, hsh yana karanta string na Password Hashing Competition (PHC) da aka adana. Idan ya ƙunshi hash na gado (misali, saitin PBKDF2 da ya tsufa), tsarin yana aiwatar da kwararar ƙasa:

1. Ganewa: Yana parse algorithm na gado da takamaiman ma'aunansa.
2. Tabbatarwa: Yana tabbatar da password ɗin da ake tuhuma a kan hash na gado.
3. Haɓaka a Lokacin Ainihi: Bayan dacewa mai nasara, yana ɗaukar plaintext password ɗin da ake tuhuma a cikin ƙwaƙwalwa kuma nan da nan yana ƙididdige sabon hash ta amfani da manufar Argon2id mai tsaro sosai.
4. Tabbatarwa: Yana mayar da sabon string na PHC zuwa aikace-aikacen banki, wanda ya rubuta a kan rikodin gado a cikin database.

Wannan tsari ya fi gaba ɗaya a fili ga mai amfani na ƙarshe. Yana ƙaurar manyan asusu masu aiki zuwa matakin tsaro mafi koli a rana ɗaya, yana rage ƙofar harin banki na halitta a kan lokaci.

Jerin da ke ƙasa yana nuna abin da ke faruwa yayin abu ɗaya na shiga lokacin da rikodin da aka adana yana kan algorithm na gado. Mai amfani ba ya ganin canji; gidan tabbatar da gaskiya na banki yana ƙarfafa da rikodi ɗaya.

sequenceDiagram
    actor User
    participant Frontend
    participant Auth as Authentication Service (hsh)
    participant DB as Database
    User->>Frontend: Submit username + password
    Frontend->>Auth: authenticate(user, password)
    Auth->>DB: SELECT password_hash FROM users
    DB-->>Auth: PHC string (legacy: PBKDF2)
    Note over Auth: Detect legacy algorithm prefix
    Auth->>Auth: verify(password, legacy_hash)
    Note over Auth: Re-hash with Argon2id
    Auth->>DB: UPDATE password_hash = new PHC
    DB-->>Auth: write confirmed
    Auth-->>Frontend: 200 OK
    Frontend-->>User: Login successful

Tsarin aiwatarwa — verify_and_upgrade dispatch

Farfajiyar haɗawa a cikin sabis na tabbatar da gaskiya ƙarami ne. Hanyar code na gado ta kasance a matsayin fallback; sabuwar hanyar code ita ce dispatcher.

use hsh::{Hasher, UpgradeResult};

struct UserRecord {
    username: String,
    password_hash: String, // PHC string
}

async fn authenticate(user: UserRecord, password_attempt: &str) -> Result<bool, AuthError> {
    let hasher = Hasher::new();
    match hasher.verify_and_upgrade(password_attempt, &user.password_hash) {
        Ok(UpgradeResult::Verified(is_valid)) => Ok(is_valid),
        Ok(UpgradeResult::Upgraded(new_hash)) => {
            db::update_user_hash(&user.username, new_hash).await?;
            Ok(true)
        }
        Err(_) => Err(AuthError::InvalidCredentials),
    }
}

Kaddarori uku suna da mahimmanci:

• Saninya na yanayi. verify_and_upgrade yana duba prefix na PHC string. Idan alamar algorithm ɗin ta gado ce, tari ɗin yana fara sake-hashing ta atomatik a kan manufar Argon2id da aka saita. Babu reshe a cikin code mai kira.
• Atomicity. Sake-hashing yana faruwa ne kawai bayan tabbatar da gado ya yi nasara, a cikin abu ɗaya na tabbatar da gaskiya. Babu wani aikin batch daban, babu taga ƙaura da aka tsara, kuma babu ƙaurar bulk mai lalata don juyawa baya.
• Tabbatarwa. Bambancin UpgradeResult::Upgraded yana ɗauke da sabon PHC string. Aikace-aikacen yana tabbatar da shi ta hanyar bayanai iri ɗaya da ke akwai don rikodin gado — babu farfajiyar rubuta a layi ɗaya, babu yarjejeniyar rubutawa mataki biyu.

Hanyoyin gazawa. Idan rubutun database ya gaza ko KMS bai isa ba a takaice yayin rubutun haɓakawa, zaman har yanzu yana yin nasara a kan hash na gado kuma rikodin yana kasancewa akan tsohon algorithm. Shiga mai nasara na gaba yana sake gwada haɓakawa. Babu yanayin rabin-ƙaurar kuma babu gazawa mai gani ga mai amfani — ƙaurar tana monotonic a fadin abubuwan shiga, kuma kuɗin kowane rikodi na gazawar haɓakawa shine kawai sake gwadawa ɗaya akan shiga ta gaba.

04. Hashes Masu Peppered ta hanyar HSM / KMS Interlock

Hashing na password na yau da kullum yana karewa daga zubar bayanai na database kai tsaye, amma idan maharin ya sami duka database (hashes da salts), zai iya aiwatar da fashin offline.

hsh yana gabatar da laushin tsaro mai ƙarfi na "peppered". Ta hanyar haɗawa da Hardware Security Modules (HSMs) ko Key Management Services (KMS) na cloud-native, ana naɗe samar da Argon2id na ƙarshe a cryptography tare da maɓalli mai babban entropy wanda ba ya barin iyakar kayan aiki masu aminci. Idan an fitar da database na mai amfani, maharin yana da blobs masu encrypted kawai. Ba zai iya fara fashin passwords ba tare da kuma cin amana ga kayan aikin HSM na banki da aka ware a zahiri ba.

Zane na gine-gine da ke ƙasa yana bin hanyar sirri. Pepper ba ya taɓa shiga database; database ba ya riƙe wani abu mai iya warwarewa shi kaɗai. Ɗakunan ajiya biyu na iya gaza da kansu — tsarin yana rasa sirri kawai idan duka biyu sun gaza tare.

sequenceDiagram
    participant App as Application Server
    participant HSM as HSM (Hardware Security Module)
    participant DB as Database
    Note over HSM: Pepper sealed in hardware<br/>never exits boundary
    App->>HSM: get_secret("production-password-pepper")
    HSM-->>App: pepper (in-memory, request-scoped)
    Note over App: Argon2::new_with_secret(&pepper, ...)
    App->>App: hash(password + salt) consuming pepper
    Note over App: Pepper consumed via secret param<br/>not via string concat
    App->>DB: STORE PHC string (uncrackable blob)
    Note over App: Pepper dropped from memory
    Note over DB,HSM: DB breach alone yields<br/>nothing crackable

Tsarin aiwatarwa — Argon2id mai peppered da HSM ke goyon baya

Ana samun pepper daga HSM a lokacin buƙata, ba daga fayil ɗin saiti ba. Argon2::new_with_secret yana cinye shi ta hanyar ma'aunin sirri na algorithm, ba ta haɗakar string ba.

use argon2::{
    Argon2, Algorithm, Version, Params,
    PasswordHasher, PasswordVerifier,
    password_hash::{PasswordHash, SaltString, rand_core::OsRng},
};

async fn authenticate_with_hsm(
    user: UserRecord,
    password_attempt: &str,
) -> Result<bool, AuthError> {
    let pepper = hsm::client::get_secret("production-password-pepper").await?;
    let hasher = Argon2::new_with_secret(
        &pepper,
        Algorithm::Argon2id,
        Version::V0x13,
        Params::default(),
    )
    .map_err(|_| AuthError::Internal)?;

    let parsed = PasswordHash::new(&user.password_hash)
        .map_err(|_| AuthError::InvalidCredentials)?;
    if hasher.verify_password(password_attempt.as_bytes(), &parsed).is_ok() {
        if is_legacy_hash(&user.password_hash) {
            let new_hash = hasher
                .hash_password(
                    password_attempt.as_bytes(),
                    &SaltString::generate(&mut OsRng),
                )
                .map_err(|_| AuthError::Internal)?
                .to_string();
            db::update_user_hash(&user.username, new_hash).await?;
        }
        return Ok(true);
    }
    Err(AuthError::InvalidCredentials)
}

Sakamako uku da suka dace da DORA suna fitowa daga wannan siffa:

• Juyawar maɓalli a matsayin matsalar sarrafa-maɓalli. Pepper yana zaune a baya iyakar HSM/KMS, ba a cikin database ba. Juyawa ya zama canjin sarrafa-maɓalli, ba yaƙin sake-hashing a fadin gidan masu amfani ba. Sabbin hashes suna ɗaure da sigar pepper ta yanzu; tsoffin hashes suna tabbatarwa a ƙarƙashin sigar da aka ɗaure har sai sun haɓaka a zahiri.
• Rabuwar ayyuka. Asalin sabis ɗin da ke karanta pepper dole ne a iya bita kuma a sami iyaka mafi ƙarancin gata. Cikakken fitarwar database ba tare da daidai grant na HSM ba ba ya samar da komai mai fasawa. Cin amana na HSM-grant ba tare da database ba ba ya samar da komai mai magancewa. Radius ɗin fashewar kowace gazawar ɗaya ya iyakance.
• Guji bug ɗin tsawaita tsayi da haɗawa. Yin amfani da ma'aunin sirri na Argon2 maimakon haɗakar string yana cire dukan rukunin gotchas na cryptography — tsawaita-tsayi, haɗakar UTF-8 mai-rashin daidaitawa, bug ɗin tsarin salt/pepper — daga farfajiyar aiwatarwa.

05. Daidaita Doka: DORA, Basel III, da SM&CR

• DORA Articles 5 da 6: Yana buƙatar cibiyoyin kuɗi su kiyaye tsarin sarrafa haɗarin ICT. Dabarar da ta dogara ga tsoffin hashes na password masu shekara goma da ba a juya ba ta saɓa waɗannan ƙa'idodi. hsh yana ba da hanyar da aka rubuta, ta atomatik don ci gaba da haɓaka kariyar cryptography.
• Basel III: Yana danganta babban birnin doka da yiwuwar da girman abubuwan asara. Ta hanyar aiwatar da Argon2id tare da HSM interlock, an rage girman cin amana na database sosai, yana goyon bayan muhawara masu auna don ƙananan rabon babban birnin haɗarin aiki.
• Alhakin SM&CR: Amincewa da gine-gine da ke aiki da magance ruɓewar cryptography yana ba manyan manajojin da aka ambata sarkar rage haɗari mai tabbatarwa, mai rubutawa.

Tambayoyin da ake yawan yi

Shin hsh yana shirye don samarwa don hanyar tabbatar da gaskiya na banki na matakin koli? Laburaren open-source ne, an rubuta shi, kuma yana yin amfani da Argon2id ta hanyar argon2 crate ɗaya da ke ƙarƙashin yanayin password-hashing na RustCrypto. Karɓuwa a matakin koli yana bin himmar bankin: bita na lambar mai zaman kanta, tabbatarwa na ginin sake-aikatawa, ɗaure jerin dogaro, gwajin haɗakar mai siyar da HSM, da amincewar Risk na Aiki. hsh yana ba da tushen; bankin yana ba da tabbacin ƙaddamarwa.

Yaya verify_and_upgrade ke guje wa haɗarin ƙaurar bulk? Verifier yana duba PHC string a lokacin parse, yana gudanar da algorithm na gado don tabbatar da password, kuma — idan algorithm da aka adana ko saitin ma'auni ƙasa ne da bene na yanzu — yana sake-hash plaintext a ƙarƙashin Argon2id tare da pepper na HSM da ke ɗaure kuma yana rubuta sabon PHC string baya cikin atom. Mai amfani yana fuskantar shiga ta yau da kullum. Gidan yana ƙarfafa da rikodi ɗaya kowace tabbatar da gaskiya mai nasara. Babu yaƙin sake-saiti, babu taga kiyayewa, babu abin da ya faru na haɗarin aiki.

Me ke faruwa ga asusu masu sake-aiki da ba sa shiga? Rikodin da ba sa tabbatar da gaskiya ba sa sake-hash. Bankuna suna magance wannan da manufofi guda biyu masu dacewa: ƙofar dormancy da aka rubuta (yawancin watanni 18–24) bayan haka ana sarrafa juya asusun a ƙarƙashin yaƙin sake-saiti mai sarrafawa, da gudanar da sake-hash na roba yayin kiyayewa da aka tsara don asusu a cikin ɗimbin da aka bayyana (mai ƙimar koli, mai-gata-koli, an tsara su). Duka biyu manufofi ne, ba halayen laburare ba; hsh yana yin rikodin yanke shawara na dispatch a cikin telemetry na audit don mai mallakar aikin ya tabbatar da ɗauke.

Shin pepper na HSM yana gabatar da matsala guda ɗaya na gazawa akan hanyar tabbatar da gaskiya? HSM ɗaya da yake sa hannu kan saƙonnin biya kuma yana juya maɓallai da KMS ke goyon baya yana kan hanyar. Haɗarin yayi daidai da matsayin bankin da ke akwai; hsh yana gadon shi maimakon gabatar da shi. Magunguna na yau da kullum ne: ma'auratan HSM HA, yankuna na KMS na ajiyar zafi, samar da pepper a lokacin buƙata tare da fall-back na karya-da'ira zuwa yanayin karatu-kawai, da littafin aiki da aka bayyana don rashin samuwar HSM. Pepper shine ma'aunin sirri na argon2, ana cinye shi a cikin tsari kuma a jefa shi daga ƙwaƙwalwa bayan amfani.

A ina hsh yake zama dangane da ƙaurar post-quantum? hsh shine tari na password-da-sirri-hashing, ba primitive na key-encapsulation ko sa hannu ba. Canjin PQC da aka rubuta a cikin NIST IR 8547 yana hari kafa-maɓalli (ML-KEM, FIPS 203) da sa hannu (ML-DSA, FIPS 204; SLH-DSA, FIPS 205). Laushin hashing da hsh yake ɗauke yawanci orthogonal ne ga wannan ƙaurar. Su biyu sun haɗu a matakin tushe — duka biyu suna so jerin samar da kayayyaki na cryptography mai aminci na ƙwaƙwalwa, mai-iya-bita, mai-sake-aikatawa — wanda yake daidai matsayin da hsh ke baiwa yanzu.

Kammalawa

Hashing na password mai turawa-da-mantawa ya kare. DORA ya matsar da rashin aiki na cryptography daga bashi na fasaha zuwa cikin alhakin doka da aka ambata, kuma lankwasan kayan aiki yana ƙara tsanani kowace shekara. Gudunmawar hsh ba algorithm mai ƙarfi ba ce — Argon2id ya kasance ana samunsa shekaru. Gudunmawar shine injin aiki don ƙaura zuwa gare shi ba tare da tsara lokacin sauke ba, ba tare da tilasta turbiya na masu amfani ba, kuma ba tare da amincewa da C-based FFI shims tare da hanyar tabbatar da gaskiya ta banki ba.

Lambar tushe ta hsh ana samunta a ƙarƙashin lasisi biyu na MIT da Apache 2.0.

Manazarta

Basel Committee on Banking Supervision (2011). Basel III: A global regulatory framework for more resilient banks and banking systems. Bank for International Settlements. Available at: https://www.bis.org/publ/bcbs189.pdf

Biryukov, A., Dinu, D., Khovratovich, D., and Josefsson, S. (2021). RFC 9106: Argon2 Memory-Hard Function for Password Hashing and Proof-of-Work Applications. Internet Engineering Task Force. Available at: https://datatracker.ietf.org/doc/html/rfc9106

European Parliament and Council (2022). Regulation (EU) 2022/2554 on digital operational resilience for the financial sector (DORA). Available at: https://eur-lex.europa.eu/eli/reg/2022/2554/oj

Financial Conduct Authority (2015). Senior Managers and Certification Regime (SM&CR). Available at: https://www.fca.org.uk/firms/senior-managers-certification-regime

National Institute of Standards and Technology (2024). Initial Public Draft — Transition to Post-Quantum Cryptography Standards (NIST IR 8547). Available at: https://csrc.nist.gov/pubs/ir/8547/ipd

OWASP Foundation (2024). Password Storage Cheat Sheet. Available at: https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html

An sake duba ta ƙarshe 2026-06-22.

Bita ta ƙarshe 2026-06-23.

# Tabbatar da Sarrafa Password a Banki na Kamfanoni: Hashing Mai Algorithms da yawa da Haɓakawa tare da hsh — Sebastien Rousseau

> Originally published at [https://sebastienrousseau.com/ha/2026-06-22-hsh-zero-downtime-cryptographic-stewardship-rust-banking-2026/](https://sebastienrousseau.com/ha/2026-06-22-hsh-zero-downtime-cryptographic-stewardship-rust-banking-2026/)

hsh tari ne na pure-Rust na cryptography da ke ba bankunan matakin koli damar ƙaurar tsoffin hashes na password zuwa Argon2id ba tare da lokacin sauke ba, tare da haɗa HSM peppering.

Read the full article on sebastienrousseau.com: https://sebastienrousseau.com/ha/2026-06-22-hsh-zero-downtime-cryptographic-stewardship-rust-banking-2026/

Tabbatar da Sarrafa Password a Banki na Kamfanoni: Hashing Mai Algorithms da yawa da Haɓakawa tare da hsh — Sebastien Rousseau

hsh tari ne na pure-Rust na cryptography da ke ba bankunan matakin koli damar ƙaurar tsoffin hashes na password zuwa Argon2id ba tare da lokacin sauke ba, tare da haɗa HSM peppering.

https://sebastienrousseau.com/ha/2026-06-22-hsh-zero-downtime-cryptographic-stewardship-rust-banking-2026/

Tabbatar da Sarrafa Password a Banki na Kamfanoni: Hashing Mai Algorithms da yawa da Haɓakawa tare da hsh — Sebastien Rousseau

hsh tari ne na pure-Rust na cryptography da ke ba bankunan matakin koli damar ƙaurar tsoffin hashes na password zuwa Argon2id ba tare da lokacin sauke ba, tare da haɗa HSM peppering.

Ga abubuwan da ya kamata a lura da su na dabarun:

- 01. Matsalar Ruɓewar Cryptography a Banki. Don fahimtar buƙatar tari kamar hsh, dole ne mutum ya fahimci tsawon rayuwar password hash.
- 02. Tabaron Gine-ginen hsh na 2026. An tsara tari a cikin laushi na asali biyar, kowanne an ƙera shi don rage takamaiman nau'in haɗari na aiki.
- 03. Hanyar Sake Hashing Ba tare da Lokacin Sauke ba. Tsarin verify_and_upgrade yana magance ƙaurar bayanai ta hanyar tsarin dispatching mai hankali, mai sane da yanayi wanda ke buƙatar sifili na lokacin sauke database.
- 04. Hashes Masu Peppered ta hanyar HSM / KMS Interlock. Hashing na password na yau da kullum yana karewa daga zubar bayanai na database kai tsaye, amma idan maharin ya sami duka database (hashes da salts), zai iya aiwatar da fashin offline.

Menene hanyar ƙungiyar ku wajen magance ƙalubalen da aka kawo a wannan rubuce-rubucen?

→ https://sebastienrousseau.com/ha/2026-06-22-hsh-zero-downtime-cryptographic-stewardship-rust-banking-2026/

#Hsh #CryptographyNaRust #PasswordHashing #Argon2id #TsaronBanki

Sebastien Rousseau | CC-BY-4.0

@online{rousseau2026tabbatar,
  author  = {Rousseau, Sebastien},
  title   = {{Tabbatar da Sarrafa Password a Banki na Kamfanoni: Hashing Mai Algorithms da yawa da Haɓakawa tare da hsh — Sebastien Rousseau}},
  year    = {2026},
  url     = {https://sebastienrousseau.com/ha/2026-06-22-hsh-zero-downtime-cryptographic-stewardship-rust-banking-2026/},
  urldate = {2026}
}

TY  - GEN
AU  - Rousseau, Sebastien
TI  - Tabbatar da Sarrafa Password a Banki na Kamfanoni: Hashing Mai Algorithms da yawa da Haɓakawa tare da hsh — Sebastien Rousseau
PY  - 2026
UR  - https://sebastienrousseau.com/ha/2026-06-22-hsh-zero-downtime-cryptographic-stewardship-rust-banking-2026/
ER  -

Rousseau S. Tabbatar da Sarrafa Password a Banki na Kamfanoni: Hashing Mai Algorithms da yawa da Haɓakawa tare da hsh — Sebastien Rousseau. sebastienrousseau.com. 2026 Jun 22. Available from: https://sebastienrousseau.com/ha/2026-06-22-hsh-zero-downtime-cryptographic-stewardship-rust-banking-2026/

Rousseau, Sebastien. "Tabbatar da Sarrafa Password a Banki na Kamfanoni: Hashing Mai Algorithms da yawa da Haɓakawa tare da hsh — Sebastien Rousseau." sebastienrousseau.com. June 22, 2026. https://sebastienrousseau.com/ha/2026-06-22-hsh-zero-downtime-cryptographic-stewardship-rust-banking-2026/.

Rousseau, S. (2026, June 22). Tabbatar da Sarrafa Password a Banki na Kamfanoni: Hashing Mai Algorithms da yawa da Haɓakawa tare da hsh — Sebastien Rousseau. sebastienrousseau.com. https://sebastienrousseau.com/ha/2026-06-22-hsh-zero-downtime-cryptographic-stewardship-rust-banking-2026/

Tabbatar da Sarrafa Password a Banki na Kamfanoni: Hashing Mai Algorithms da yawa da Haɓakawa tare da hsh — Sebastien Rousseau

hsh tari ne na pure-Rust na cryptography da ke ba bankunan matakin koli damar ƙaurar tsoffin hashes na password zuwa Argon2id ba tare da lokacin sauke ba, tare da haɗa HSM peppering.

Originally published at https://sebastienrousseau.com/ha/2026-06-22-hsh-zero-downtime-cryptographic-stewardship-rust-banking-2026/ by Sebastien Rousseau.
Licensed under CC-BY-4.0.

SEBASTIEN ROUSSEAU · FOUNDER · ENGINEER