🔑 Encryption Keys

An encryption key is a piece of data — usually a very long number — that the encryption algorithm uses to scramble plain text into cipher text. The same key (or a matching key) is needed to reverse the process. Without the correct key, the cipher text is effectively impossible to read, even if an attacker has the encrypted data and knows which algorithm was used.

There are two fundamentally different approaches to using keys:

🔑 Symmetric Encryption — One Key for Both

Symmetric encryption uses the same key for both encryption and decryption. Imagine a padlock where the same physical key both locks and unlocks it. The sender encrypts the data with the key, sends the cipher text, and the receiver decrypts it with the same key. This is fast and efficient, but has one major problem: how do you safely share the key with the other person? If you send the key over the internet, an attacker could intercept it and then decrypt everything.

Common symmetric algorithms include AES (Advanced Encryption Standard), which uses key sizes of 128, 192, or 256 bits. AES-256 is the gold standard — it is used by governments and banks worldwide. Breaking AES-256 by trying every possible key would take longer than the age of the universe, even with the fastest supercomputers.

🔑🔑 Asymmetric Encryption — Two Different Keys

Asymmetric encryption uses a pair of keys: a public key and a private key. They are mathematically linked but different. Data encrypted with the public key can only be decrypted with the matching private key, and vice versa. The public key can be shared openly with anyone — it is like a letterbox slot that anyone can drop a letter into. The private key is kept secret — it is the only key that opens the letterbox.

This solves the key-sharing problem: the server publishes its public key openly. Your browser uses it to encrypt data. Only the server's private key can decrypt it. Even if an attacker has the public key and the cipher text, they cannot decrypt the data without the private key.

How HTTPS uses BOTH: In practice, HTTPS uses asymmetric encryption at the start (during the TLS handshake) to safely exchange a symmetric key. Then all actual data is encrypted with the fast symmetric key (AES-256). This gives you the best of both worlds: the security of asymmetric key exchange and the speed of symmetric data encryption.