Why Public Key Crypto Works
Public online security comes from private keys and one-way math, not from keeping the encryption method secret.
A complete interactive classroom, not just a preview.
Start when you are ready to enter this Stage's 10 scenes and explore, respond, and learn as you go.
Why can online banking encrypt passwords with publicly known methods and still stay secure?
- symmetric-key-problem
- Same-key ciphers require the sender and receiver to share a secret, which is hard to do safely at a distance.
- public-key-model
- A public key encrypts for anyone; a matching private key decrypts, so no secret key needs to be sent.
- one-way-function
- A math operation that is easy to compute but extremely hard to reverse, like multiplying two large primes versus factoring their product.
- rsa-mechanics
- RSA turns messages into numbers and uses modular exponentiation; without the private key, decryption requires factoring a huge composite number.
- password-hashing
- Sites usually store a one-way hash of your password, not an encrypted copy they can read; login re-hashes the input and compares hashes.
- tls-authentication
- Browsers verify the bank's certificate with its public key before exchanging session keys, preventing imposters.
If the encryption method is public, attackers can reverse it and decrypt messages.
Show that reversing public encryption requires the private key or solving a hard math problem; knowing the algorithm alone is not enough.
Encryption and password hashing are the same thing.
Distinguish two-way encryption from one-way hashing and explain when each is used.
The password has to be decryptable by the server to log you in.
Explain that login works by re-hashing the entered password and comparing hashes; the original is not decrypted.
- quantum cryptography
- mathematical proofs of RSA
- side-channel attacks
- key exchange protocol details
- Explain why making an encryption algorithm public does not make it unsafe.
- Identify the role of the public key and private key in a public-key exchange.
- Distinguish between encrypting messages and hashing stored passwords.
- For a new online service, judge whether its password handling should use encryption or hashing and explain why.
General curious learners with basic arithmetic; no prior cryptography or deep math background expected.
- 01The Public Encryption PuzzleslideOrientationObserve
Introduce the puzzling fact that banks use publicly known encryption methods and are still secure.
- Public algorithms are visible to everyone
- Banks rely on them every day
- Course question: why is that safe?
- 02What Do You Predict?quizPredictionPredict
Let learners commit to an explanation before seeing the math.
- Choose the most plausible reason for public-key security
- 03The Key-Sharing ProblemslideModel buildingObserve
Show why traditional secret-key encryption is awkward across the internet.
- Symmetric ciphers use one shared secret key
- Sending that key securely is a chicken-and-egg problem
- [Table] Symmetric vs public-key encryption: key count, key sharing, security basis
- 04The Public Key ModelslideModel buildingObserve
Introduce the two-key lock idea: a public key locks, a private key unlocks.
- Public key can be shared openly; private key stays secret
- Anyone can encrypt, but only the owner can decrypt
- Solves key distribution: no secret channel needed
- 05One-Way MathslideModel buildingObserve
Explain the mathematical backbone that makes the private key hard to recover.
- Multiplying two large primes is fast
- Factoring the product is extremely slow
- This one-way asymmetry is the security trapdoor
- 06RSA Key LabinteractiveModel buildingConstruct
Use a simplified RSA simulator to encrypt and decrypt with small numbers.
- Pick small primes to build a key pair
- Encrypt a message with the public key
- Decrypt only with the private key
- 07Check Your UnderstandingquizAssessmentChoose
Check core understanding of public and private keys before applying it.
- Recognize what public/private keys do
- Identify the hard problem that protects RSA
- 08What Would an Attacker Need?quizApplicationApply
Apply the public-key model to realistic attack scenarios and choose what would actually break the system.
- Scenario: stolen certificate vs stolen private key
- Choose which secret, if leaked, defeats encryption
- 09Passwords: Hashed, Not EncryptedslideMisconception repairExplain
Clarify that websites usually hash passwords, not encrypt them, and hashing is one-way.
- Encryption is two-way: ciphertext can be decrypted
- Hashing is one-way: original password cannot be recovered
- Login compares hashes, not decrypted passwords
- 10Why Public Algorithms Stay SecureslideSynthesisExplain
Summarize the full answer: security depends on private keys and hard math, not on hiding the algorithm.
- Security = private key + one-way math
- Public algorithm ≠ public ability to decrypt
- Messages get encrypted; stored passwords get hashed
Discussion threads for a Stage aren't available yet.
