Encryption & Secure Communication

Hash Function

About 5 min read

What Is a Hash Function

A hash function takes arbitrary-length input data and produces a fixed-length output called a hash value (or digest). The same input always yields the same hash, but recovering the original data from the hash is computationally infeasible - a property known as one-way resistance.

For example, SHA-256 converts hello into 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824, a 64-character hexadecimal string. Changing even one character in the input produces a completely different hash (the avalanche effect), giving no clue about the original input.

Hashing differs from encryption. Encryption is reversible with a key; hashing is not. This irreversibility is precisely why hash functions are chosen for password storage and data integrity verification.

Algorithm Comparison

MD5 (128-bit)
Published as RFC 1321 in 1992. Fast but collision resistance is broken. RFC 6151 (2011) states that MD5 is no longer acceptable where collision resistance is required, such as digital signatures.
SHA-1 (160-bit)
Theoretical collision attacks demonstrated in 2005; CWI Amsterdam and Google announced an actual collision in February 2017 (SHAttered). Still found in legacy systems; NIST announced on December 15, 2022 that SHA-1 should be phased out by December 31, 2030.
SHA-256 (256-bit)
The flagship of the SHA-2 family. No known collision attacks. Widely used in TLS certificates, blockchain, and file verification. The standard choice for general-purpose hashing.
bcrypt
Designed specifically for password storage. Features a configurable cost factor that intentionally slows computation, resisting GPU-accelerated brute-force attacks. Automatically generates and embeds a salt.

SHA-256 is used for general data verification; for password storage, the OWASP Password Storage Cheat Sheet lists Argon2id first, then scrypt, bcrypt for legacy systems, and PBKDF2 where FIPS-140 compliance is required. MD5 and SHA-1 are not suitable where collision resistance is required, such as digital signatures.

Password Storage

Web services must never store passwords in plaintext. If the database leaks, every user's password would be exposed. The correct approach is to hash passwords before storage and compare hashes during login.

However, simple hashing is insufficient. Identical passwords produce identical hashes, enabling attackers to use precomputed lookup tables (rainbow tables) to reverse hashes back to passwords.

The defense is salting: appending a random string unique to each password before hashing. Even identical passwords produce different hashes with different salts, rendering rainbow tables useless. bcrypt and Argon2 handle salt generation automatically. Combined with a password manager generating long random passwords, the risk of rainbow table or brute-force attacks is further reduced.

Blockchain Applications

Blockchain leverages hash function properties by including the previous block's hash in each new block, forming a chain. Altering any block changes its hash, breaking the chain from that point forward. Recalculating all subsequent blocks requires overwhelming the entire network's computing power.

Bitcoin mining (Proof of Work) is a competition to find an input whose SHA-256 hash meets specific criteria (a certain number of leading zeros). Due to the one-way property, the only approach is brute-force trial, and this computational cost secures the blockchain.

Rainbow Table Attacks and Salting

Rainbow table attacks use massive precomputed tables mapping common passwords to their hash values. Leaked hashes are matched against these tables to recover original passwords.

  • Salt: A random value appended to each password before hashing. Different salts produce different hashes even for identical passwords, invalidating precomputed tables.
  • Pepper: An application-wide secret value added alongside the salt. Even if the database leaks, the pepper stored separately makes hash reversal significantly harder.
  • Stretching: Repeating the hash computation many times to increase the time per hash. bcrypt's cost factor and PBKDF2's iteration count implement this approach; the OWASP Password Storage Cheat Sheet lists 600,000 or more iterations for PBKDF2 with HMAC-SHA-256.

Common Misconceptions

Hashing and encryption are the same thing
Encryption is reversible with a key; hashing is a one-way operation. Passwords should be hashed (not encrypted) for storage, while communication should be encrypted for transit protection.
SHA-256 hashing is sufficient for password storage
SHA-256 is too fast for password hashing - attackers can try large numbers of guesses quickly, for example with GPUs. Password storage uses intentionally slow algorithms such as bcrypt or Argon2.
Share

Related Terms

Related Articles