In secure password storage systems, techniques like salting and peppering are often used.
Suppose a system stores passwords like this:

For each user, a unique salt is randomly generated and stored along with the password hash.

Additionally, the system uses a single global secret pepper, not stored in the database, but hardcoded into the backend server.

Which of the following statements are correct?

Question

In secure password storage systems, techniques like salting and peppering are often used.
Suppose a system stores passwords like this:

For each user, a unique salt is randomly generated and stored along with the password hash.

Additionally, the system uses a single global secret pepper, not stored in the database, but hardcoded into the backend server.

Which of the following statements are correct?

BlackTom AI · Accepted Answer

Salt is a per-user random value appended to (or combined with) the password before hashing, e.g., H(password || salt), and a pepper is a single global secret combined with the password and salt, e.g., H(password || salt || pepper), where the pepper is not stored in the database.

1) Relevant concepts
- Salting: unique random salt per user stored with the hash. Prevents identical passwords producing identical hashes and defeats precomputed rainbow tables because an attacker would need tables for each salt.
- Peppering: a global secret kept out of the database (e.g., in server code or environment). It adds an extra unknown factor an attacker must know to verify guesses offline.
- Threat model distinctions: database compromise vs. server compromise. If only the DB is leaked (hashes + salts), pepper protects; if server (and pepper) is also compromised, pepper gives no additional protection.

2) Step-by-step reasoning
- With salting: stored values are (salt_i, hash_i). To check a guess g against user i, attacker computes H(g || salt_i) and compares to hash_i. Because salt_i differs per user, precomputing H(g || salt) for many salts is impractical, so rainbow tables are ineffective.
- With pepper: stored values are (salt_i, hash_i) but pepper is not in DB. To verify a guess g, attacker must compute H(g || salt_i || pepper). Without the pepper, their computed value will not match hash_i, so the leak of DB alone is insufficient to verify guesses.
- Edge cases: pepper must be kept secret and high entropy; if attacker also compromises the server or obtains the pepper, pepper gives no protection. Salts do not prevent brute-force: attackers can still try guesses offline, but they must compute the hash per salt (which slows large-scale attacks and prevents rainbow tables).

3) Why the chosen options are correct
- "Peppering adds extra protection..." is correct because a leaked DB without the pepper prevents straightforward verification of guesses.
- "Salting prevents attackers from using precomputed rainbow tables..." is correct because unique salts require per-salt precomputation, which defeats generic rainbow tables and ensures identical passwords hash differently.

4) Why the other options are incorrect
- "Pepper is typically stored next to the salt and hash..." is wrong: if pepper were stored with the DB, it ceases to be a secret and gives no extra protection.
- "If an attacker steals the database but not the backend server, they can still easily brute-force the passwords because the salt is public." is misleading/incorrect: salts are public by design, and while they do not stop brute-force attempts entirely, they prevent rainbow tables and force attackers to compute per-user hashes, making large-scale precomputed attacks infeasible. Saying "easily brute-force" overstates the impact of public salts.

Conclusion: The correct choices are the two listed in the provided answer: Peppering adds extra protection — even if the database is stolen, passwords are harder to crack without server access; and Salting prevents attackers from using precomputed rainbow tables effectively, even if two users have the same password. Confirmed.

类似问题

Which of the following statements correctly explain the effect of salt in authentication systems?

Scenario:Passwords are stored in a database as hashes. Even if the database is compromised, original passwords cannot be recovered. Question: Which cryptographic concept is applied?

To protect passwords in the case when an attacker obtains the password database, _ is used to prevent ___ of the passwords.

When designing a secure system, why is hashing preferred over encryption for storing passwords?

An important technique to mitigate password dictionary attacks is to ___________.

__________ is a technique used to help protect against attacks exposing the contents of the server where password information is stored.

The best way to store passwords is:

更多留学生实用工具

智能学习助手

风格化写作助手

论文查重助手

文献引用助手

课堂转译助手

课堂笔记助手

Quiz搜索助手

学校历年真题

智能刷题助手

智能匹配练习

希望你的学习变得更简单