Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cyber Security Cards › Revision Cards

How Passwords Are Stored

How Passwords Are Stored How systems should store passwords safely: not as plain text, but as a hash (a one-way fingerprint). A salt is a random value added to each password before hashing, so two equal passwords get different hashes. A slow hash (bcrypt) is slow on purpose, so guessing is hard. On

How Passwords Are Stored How systems should store passwords safely: not as plain text, but as a hash (a one-way fingerprint). A salt is a random value added to each password before hashing, so two equal passwords get different hashes. A slow hash (bcrypt) is slow on purpose, so guessing is hard. On
How Passwords Are Stored · Download PNG
Read card text

What this card says

What it is

How systems should store passwords safely: not as plain text, but as a hash (a one-way fingerprint).

Key terms

A salt is a random value added to each password before hashing, so two equal passwords get different hashes.

A slow hash (bcrypt) is slow on purpose, so guessing is hard.

Why it matters for security

On Linux, hashes live in /etc/shadow, readable only by root.

Plain text or fast hashes (MD5) are unsafe.

MethodWhat it storesSafe?
Plain textThe password itselfNever – one leak exposes everyone
Hash (MD5, SHA1)A one-way fingerprintWeak now – fast to crack, no salt
Salted hashHash + a unique random "salt" per userBetter – stops precomputed tables
Slow hash (bcrypt, Argon2, PBKDF2)Salted hash that is deliberately slowBest – cracking becomes very expensive

Learn more in the lesson: 22.1 How Passwords Are Stored

See all Ravi Sir's Cyber Security Cards