密钥管理与哈希
探索安全管理加密密钥的实践，为密码使用强哈希算法，并避免常见的密码学问题。
密钥管理与哈希 是 CoddyKit 上的免费 Secure Coding & OWASP Top 10 for Backend 课时。 这是第 3 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Secure Coding & OWASP Top 10 for Backend 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Secure Coding & OWASP Top 10 for Backend 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Intro to Cryptographic Keys
Welcome to this lesson on Key Management and Hashing! We'll explore how to protect the secrets that protect your data.
Cryptographic keys are fundamental to secure communication and data storage. Think of them as secret passwords or unique stamps that lock and unlock sensitive information.
Why Key Security Matters
The security of your entire system often depends on the security of your cryptographic keys.
- Data Breaches: If an attacker gains access to your encryption keys, all data encrypted with those keys becomes readable.
- Impersonation: Compromised signing keys can allow attackers to forge identities or tamper with data without detection.
- Trust Erosion: Loss of keys can lead to a complete breakdown of trust in your system's security posture.
Generating Strong Keys
Keys must be truly random and sufficiently long to be secure. Weak or predictable keys are easy for attackers to guess.
Always use cryptographically secure random number generators (CSRNGs) provided by your programming language's standard library. Never roll your own!
Try running this example to see how a secure key can be generated:
import java.security.SecureRandom;
import java.util.Base64;
public class KeyGenerator {
public static void main(String[] args) {
SecureRandom random = new SecureRandom();
byte[] keyBytes = new byte[32]; // 256-bit key
random.nextBytes(keyBytes);
String base64Key = Base64.getEncoder().encodeToString(keyBytes);
System.out.println("Generated Key: " + base64Key);
}
}Secure Key Storage
Once generated, keys need to be stored securely. This is one of the most critical aspects of key management.
- Hardware Security Modules (HSMs): Dedicated physical devices for secure key generation, storage, and cryptographic operations.
- Key Management Services (KMS): Cloud-based services (e.g., AWS KMS, Azure Key Vault) that provide secure key storage and lifecycle management.
- Avoid: Storing keys directly in source code, configuration files, or version control.
Key Rotation for Longevity
Even with the best storage, keys can eventually be compromised. Regular key rotation limits the damage if a key is ever exposed.
Key rotation involves generating a new key, re-encrypting data with the new key, and securely archiving or destroying the old key. This reduces the 'window of exposure' for any single key.
Understanding Hashing
Hashing is a one-way process that transforms input data into a fixed-size string of characters, called a hash or digest.
- One-way: You can't easily reverse a hash to get the original data.
- Fixed-size: No matter the input size, the output hash is always the same length.
- Unique (mostly): A tiny change in input results in a vastly different hash.
Hashing is crucial for verifying data integrity and securely storing passwords.
Hashing Passwords Securely
Never store user passwords in plain text or encrypted form. Always store their hash.
If a database is breached, attackers only get hashes, not the actual passwords. Since hashing is one-way, they can't easily recover the original passwords.
However, simple hashing isn't enough on its own. We need more techniques!
The Power of Salting
A salt is a unique, random string added to a password before it's hashed. Each user gets a different salt.
Salting prevents rainbow table attacks, where attackers pre-compute hashes for common passwords. With salts, even if two users have the same password, their stored hashes will be completely different.
This example conceptually shows how a salt is added before hashing:
import java.security.MessageDigest;
import java.security.NoSuchAlgorithmException;
import java.security.SecureRandom;
import java.util.Base64;
public class PasswordHasher {
public static void main(String[] args) throws NoSuchAlgorithmException {
String password = "mySecretPassword";
// Generate a random salt for each user
SecureRandom random = new SecureRandom();
byte[] saltBytes = new byte[16]; // 128-bit salt
random.nextBytes(saltBytes);
String salt = Base64.getEncoder().encodeToString(saltBytes);
// Combine password and salt, then hash
String saltedPassword = password + salt;
MessageDigest md = MessageDigest.getInstance("SHA-256"); // Illustrative
byte[] hashedPasswordBytes = md.digest(saltedPassword.getBytes());
String hashedPassword = Base64.getEncoder().encodeToString(hashedPasswordBytes);
System.out.println("Password: " + password);
System.out.println("Salt: " + salt);
System.out.println("Hashed Password (with salt): " + hashedPassword);
}
}Modern Hashing Algorithms
For password hashing, don't use general-purpose hash functions like SHA-256 or MD5. They are too fast, making brute-force attacks easier.
Instead, use algorithms specifically designed to be slow and computationally intensive:
- Bcrypt: Widely used and highly recommended.
- Scrypt: Another strong option, especially resistant to GPU-based attacks.
- Argon2: The winner of the Password Hashing Competition, considered state-of-the-art.
These algorithms have adjustable 'work factors' to increase their computational cost over time.
Avoiding Crypto Pitfalls
Cryptography is complex. Common mistakes can severely weaken your security:
- Don't 'Roll Your Own' Crypto: Always use well-vetted, standard cryptographic libraries. Custom implementations are almost always insecure.
- Hardcoding Keys: Never embed encryption keys directly in your code.
- Using Weak Algorithms: Avoid deprecated or known-vulnerable algorithms (e.g., MD5, SHA1 for security, DES, RC4).
- Improper Randomness: Don't use non-cryptographically secure random number generators for security tasks.
Test Your Knowledge
Which of the following are recommended best practices for managing cryptographic keys and passwords?
Recap & Next Steps
In this lesson, we've covered the vital aspects of cryptographic key management and secure password hashing.
- Keys: Generate strong, random keys, store them securely (HSM/KMS), and rotate them regularly.
- Hashing: Always hash passwords using unique salts and slow, purpose-built algorithms like bcrypt, scrypt, or Argon2.
- Avoid Pitfalls: Never create your own crypto, hardcode keys, or use weak algorithms.
By following these practices, you significantly strengthen your backend applications against data breaches and unauthorized access. Keep learning and stay secure!
常见问题解答
「密钥管理与哈希」课时是免费的吗？
是的 — 「密钥管理与哈希」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Secure Coding & OWASP Top 10 for Backend 课程的其余内容，请升级到 CoddyKit PRO。 Secure Coding & OWASP Top 10 for Backend 课程共包含 4 节课。
「密钥管理与哈希」这节课中我会学到什么？
探索安全管理加密密钥的实践，为密码使用强哈希算法，并避免常见的密码学问题。 你通过在浏览器中直接运行的动手代码来练习 Secure Coding & OWASP Top 10 for Backend，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Secure Coding & OWASP Top 10 for Backend 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Secure Coding & OWASP Top 10 for Backend 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 3 节课，共 4 节。
「密钥管理与哈希」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Secure Coding & OWASP Top 10 for Backend 课中编写并运行代码吗？
能。每节 Secure Coding & OWASP Top 10 for Backend 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。