generated from mwc/lab_encryption
Lab Encryption Submission
Yes, writing my own code helped me understand the problem better. At first, I was just following the examples, but then once I created my own crack_caesar function, I had to really think about how the Caesar cipher worked and how it could be used to find the secret number. I honestly had a very hard time figuring out Checkpoint 2. But, with help, I had to line up the letters in the plaintext and the ciphertext.
This commit is contained in:
@@ -20,6 +20,10 @@
|
|||||||
## Checkpoint 2
|
## Checkpoint 2
|
||||||
|
|
||||||
5. What is the polyalphabetic secret word?
|
5. What is the polyalphabetic secret word?
|
||||||
|
PYTHON
|
||||||
|
|
||||||
6. Decrypt this message, which was encrypted using the same secret word:
|
6. Decrypt this message, which was encrypted using the same secret word:
|
||||||
"EbZhdaV[h^bTpchhQnhig]X[VmhhRP]ftXVnRfjVY]fgtO_X]("
|
"EbZhdaV[h^bTpchhQnhig]X[VmhhRP]ftXVnRfjVY]fgtO_X]("
|
||||||
|
The treasure is a worthless ball of aluminum foil.
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user