การเข้ารหัสและการทำแฮชข้อมูล

Welcome to Data Encryption & Hashing! In today's digital world, protecting sensitive information is paramount. Whether it's user passwords, personal data, or financial details, securing this data is a core responsibility for any developer.

This lesson will equip you with the knowledge and tools to implement robust data protection strategies in your Node.js applications.

Before diving into techniques, let's understand two fundamental concepts:

• Encryption: A two-way process that transforms data (plaintext) into an unreadable format (ciphertext) using a key. It's reversible, meaning the ciphertext can be converted back to plaintext with the correct key.
• Hashing: A one-way process that transforms data of any size into a fixed-size string of characters (a hash value or digest). It's irreversible; you cannot get the original data back from its hash.

They serve different purposes!

Symmetric encryption uses the same secret key for both encrypting and decrypting data. It's fast and efficient, making it suitable for encrypting large amounts of data.

Common algorithms include AES (Advanced Encryption Standard). The key must be kept secret and securely exchanged between parties.

Node.js's built-in crypto module allows us to perform symmetric encryption. Here's an example using AES-256-CBC, a strong symmetric algorithm.

Note: In a real application, the encryption key should be securely generated and stored (e.g., in environment variables) and the IV should be random for each encryption.

Asymmetric encryption, also known as public-key cryptography, uses a pair of keys: a public key and a private key.

• Public key: Can be shared with anyone. Used for encryption.
• Private key: Must be kept secret. Used for decryption.

If you encrypt data with someone's public key, only they can decrypt it with their private key. This is slower than symmetric encryption but crucial for secure communication and digital signatures.

When storing user passwords, NEVER encrypt them. Instead, always hash them. If an attacker gains access to your database, they would ideally only find irreversible hashes, not decryptable passwords.

A good hashing algorithm for passwords should be:

• One-way: Impossible to reverse.
• Collision-resistant: Extremely unlikely for two different inputs to produce the same hash.
• Slow: Deliberately designed to be computationally intensive to deter brute-force attacks.

To further enhance password security, we use salts. A salt is a unique, random string added to a password before it's hashed.

Why use salts?

• Prevents Rainbow Table Attacks: Without salts, attackers could pre-compute hashes for common passwords (rainbow tables).
• Unique Hashes: Even if two users have the same password, their salted hashes will be different.

The salt is usually stored alongside the hash.

bcrypt is a widely recommended library for hashing passwords in Node.js because it's designed to be slow and integrates salting automatically.

It handles generating a unique salt and performing multiple rounds of hashing (controlled by saltRounds, a work factor) to make brute-force attacks more difficult.

While encryption and hashing protect data at rest (stored in a database), it's equally important to protect data while it's moving between systems (data in transit).

TLS/SSL (Transport Layer Security/Secure Sockets Layer) protocols provide encryption for network communication. When you visit a website using HTTPS, your browser and the server use TLS/SSL to encrypt all data exchanged, preventing eavesdropping and tampering.

Which of the following statements about encryption and hashing are TRUE?

Great job! You've learned the fundamentals of data encryption and hashing:

• Encryption protects sensitive data, making it reversible with a key.
• Hashing provides one-way transformation, ideal for password storage and data integrity.
• Symmetric encryption uses a single key, while asymmetric encryption uses public/private key pairs.
• Always use strong, salted hashing (like bcrypt) for passwords.
• TLS/SSL secures data in transit over networks.

Implementing these practices is vital for building secure Node.js applications!