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:
14
answers.md
14
answers.md
@@ -4,22 +4,26 @@
|
||||
|
||||
0. `secrets/secret0.txt` is encrypted using a Caesar Cipher. What is
|
||||
its secret number?
|
||||
78
|
||||
78
|
||||
1. `secrets/secret1.txt` is encrypted using a Caesar Cipher. What is
|
||||
its secret number?
|
||||
1
|
||||
1
|
||||
2. `secrets/secret2.txt` is encrypted using a Caesar Cipher. What is
|
||||
its secret number?
|
||||
44
|
||||
44
|
||||
3. `secrets/secret3.txt` is encrypted using a Caesar Cipher. What is
|
||||
its secret number?
|
||||
59
|
||||
59
|
||||
4. `secrets/secret4.txt` is encrypted using a Caesar Cipher. What is
|
||||
its secret number?
|
||||
32
|
||||
32
|
||||
## Checkpoint 2
|
||||
|
||||
5. What is the polyalphabetic secret word?
|
||||
PYTHON
|
||||
|
||||
6. Decrypt this message, which was encrypted using the same secret word:
|
||||
"EbZhdaV[h^bTpchhQnhig]X[VmhhRP]ftXVnRfjVY]fgtO_X]("
|
||||
The treasure is a worthless ball of aluminum foil.
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user