Cryptography Free Course | Cryptography For Cyber Security
This article kicks things off by explaining that this isn’t a deep dive or an advanced cryptography course or class. It’s more of a…
This article kicks things off by explaining that this isn’t a deep dive or an advanced cryptography course or class. It’s more of a practical, beginner-friendly guide to help folks get started in cybersecurity. The video blends modern encryption methods with older, historical ones and walks through live examples using TryHackMe labs including TryHackMe Cryptography basics, TryHackMe Public Key cryptography and TryHackMe Hashing.
Core Definitions in Cryptography
To build a solid base, the video explains key terms:
Key: A secret code needed to turn the scrambled message back into something readable. Without the key, the cipher’s useless.
Plaintext: The original message. Something you can read, like an email or note.
Ciphertext: What the message looks like after it’s scrambled by encryption.
Cipher: The formula used to mess with the message — like AES or others.

Classical Ciphers and Why They’re Weak
The Caesar Cipher gets used as an example here. It’s a very old trick where each letter shifts forward by a set number. To decode, you shift the other way. Easy to break, though — only 25 possible keys in English. Anyone could try them all quickly.

How Symmetric Encryption Works
This method uses one key to lock and unlock. That’s handy, but risky too — how do you share that one key safely?
DES/3DES: Outdated, mostly retired now.
Examples: DES, 3DES, and AES.
AES: Still strong today, with longer key options.

Asymmetric Encryption: Stronger but Slower
Here, two keys get used — a public one and a private one. One scrambles the message, the other unscrambles it.
Diffie-Hellman: Mainly helps with swapping keys in a safe way.
RSA: Old-school and secure but runs slow because of big keys.
ECC: Does the same job with smaller keys.

Math That Makes It All Work
XOR: A math operation used in encryption; it flips bits based on whether they match.
Modulo: Used to find remainders — critical when making asymmetric keys.

Diffie-Hellman Key Exchange in Real Life
Here’s how it goes down:
- Both sides agree on two public values (P and G).
- Each person picks a private number.
- They do some math to make public keys.
- They swap keys.
- Then use those to get to a shared secret. That shared secret? Never actually sent.

SSH Keys and Server Access
Asymmetric encryption powers SSH too. When you connect to a server for the first time, you see a fingerprint. Accept it, and next time your computer checks it quietly.
- You can make SSH keys on your machine.
- The server keeps a copy of your public key in a file called
authorized_keys. - Make sure your file permissions are set right or SSH won’t work.
Digital Signatures Make Things Trustworthy
Here’s the idea:
- Bob signs a document by encrypting its hash with his private key.
- Alice checks it by using Bob’s public key.
- If everything matches, she knows Bob signed it and it hasn’t been changed.
This works kind of like HTTPS certificates, which prove websites are legit thanks to trusted authorities.

Encrypting and Signing with GPG
You can set an expiration date and a passphrase to protect the key.
You can make your own keys.
Encrypt and decrypt files easily.
Encrypted files usually end in .gpg.
Hashing for File Integrity
Hashing creates a fingerprint for files. A small change in the file creates a totally different hash. You can’t reverse it back to the original file — hashing’s only for checking things, not hiding them.
- Good Hashes: SHA256.
- Weak Hashes: MD5 and SHA1 — they’ve got flaws and can collide, meaning two different files might share the same hash.
TryHackMe exercises give you hands-on practice using hashes to verify files and learn how it works.

RSA Encryption Explained
RSA encryption sits at the center of asymmetric cryptography — it’s all about using two keys that work together but do different things. Here’s the breakdown of how it keeps your secrets safe.

Encrypt with Public, Decrypt with Private
Let’s say Alice wants to send Bob a message. She uses Bob’s public key to scramble the message. That public key? It’s out there for anyone to use — no harm in sharing it.
But here’s the trick: once that message’s encrypted, only Bob’s private key can unlock it. That private key is his and his alone. It stays hidden. Always.
Why This Works
Even if someone grabs the scrambled message while it’s traveling through the internet — even if they’ve got Bob’s public key and know RSA like the back of their hand — they still can’t read it. Why? Because cracking RSA means solving a seriously hard math problem. The kind that would take current computers way too long to figure out.
The Math Behind It
RSA depends on how hard it is to break down huge numbers into their prime parts. You multiply two giant primes to make a number that goes into the public key. That’s easy. But going backward — figuring out the original primes from that big number? Takes forever without the right tools. That’s what keeps the private key safe.
So bottom line? RSA lets people share information out in the open without risking privacy. Encrypt with the public key. Only the matching private key can open it. Simple in concept. Super secure in practice.
TryHackMe Cryptography Basics, TryHackMe Public Key Cryptography Basics & TryHackMe Hashing Basics Room Answers
The answers for these room can be found here.