Weekly Challenges

Solve the challenge, share your solution and summit the ranks of our Community!

Also available in | Français | Português | Español | 日本語
IDEAS WANTED

Want to get involved? We're always looking for ideas and content for Weekly Challenges.

SUBMIT YOUR IDEA
SOLVED

Challenge #163: Caesar Cipher (on the way to Kryptos)

nivi_s
8 - Asteroid

Challenge #163 Solved!

 

Spoiler
clipboard_image_0.png
OllieClarke
15 - Aurora
15 - Aurora

This was fun 🙂

Spoiler
Challenge 163.png
Inactive User
Not applicable
 
justindavis
10 - Fireball
Spoiler
challenge_163_solution_justindavis.PNG
ZenonH
8 - Asteroid

Took a short crack at Part II, but after realizing my route didn't really offer a solution without building a macro I decided to stop there. 

Spoiler
ZHSOL.png
Rags1982
10 - Fireball
 
tiffany_chen
8 - Asteroid

A lot of fun!

Spoiler
Annotation 2019-12-29 120920.pngAnnotation 2019-12-29 120944.png
SueDonim
8 - Asteroid

Bit of brute force on Part II since I haven't learned iterative macros yet, but I got it and it is replicable.  I have to admit, I am impressed with Caesar's command of the English language.  The man was truly ahead of his time

 

Spoiler
Part I:
Process:
- Created input table with ROT-13 transformation
- RegEx on "." split to rows
- Find and Replace message to ROT-13
- Summarize concatenation (with no separators) to see answer to message
- Find and Replace message to ROT-13 to ensure transfers back
- Join to ensure message is same as original


Answer- Part I.PNGMySolution - Part I.PNG

Part II:
Process:
- Created a brute force table with all 26 transformations
- RegEx on "." split to rows
- Add RecordIDs (not needed)
- Filter for various ROTs (iterated by hand)
- Find and Replace message to ROT chosen
- Summarize concatenation (with no separators) to see answer to message

Answer- Part II.PNGMySolution - Part II.PNG
BruteForceTable.PNG
michalklofac
7 - Meteor

I didn't feel like making a macro so I approached part 2 by parsing the string into individual characters, transposing this so that there is a single character per line, and then joining based on both the ROT-number and the actual character to be decoded. I then looked for "Caesar" to identify the correct results (as it was supposed to be signed).

 

Spoiler
Screenshot (66).png

Screenshot (65).png

mbogusz
9 - Comet

Well, I don't think I'll ever forget lowercase chars are numbered 97-122 now.

 

What's great about this is it can encode/decode thousand-page documents in the same amount of time (or less) what Caesar's army would've spent decoding his 20-letter message.

Spoiler
2020-01-09 20_08_10-Greenshot.png