Update index.md #23
Update index.md #23
Conversation
There was a problem hiding this comment.
I gave you some initial feedback as inline comments. I also have some high-level observations:
s/number system/numeral system/g- The text in the image
number_systems.svgis a bit off-centre. Make the figures larger so the text fits. - There's no need to leave an empty line after each sentence. Just write them on separate consecutive lines so they show up in the same paragraph. Only leave empty lines when you want to start a new paragraph.
Co-authored-by: Teodor Dutu <[email protected]>
Co-authored-by: Teodor Dutu <[email protected]>
Co-authored-by: Teodor Dutu <[email protected]>
Co-authored-by: Teodor Dutu <[email protected]>
Co-authored-by: Teodor Dutu <[email protected]>
Co-authored-by: Teodor Dutu <[email protected]>
|
@gabrielmocanu look at the rich diff of the README and you'll see the images. @Adoie yes, you'll have to squash these commits, but after you've added the challenges. |
There was a problem hiding this comment.
Follow the conventions in our template-public repo for storing challenges. You don't need README.md files for them, but:
- rename challenge folders (eg:
ASCII Artbecomesascii-art) - change solution script names to
solution.py - use
READNE.mdinstead ofsol.md - rename all public files using lowercase letters and underscores (eg.:
The Truth.txtbecomesthe_truth.txt)
Then I'll have another look.
Co-authored-by: Teodor Dutu <[email protected]>
…oject.txt to data-representation/activities/ascii-art/public/tommys_art_project.txt
…presentation/activities/ascii-art/sol/solution.py
…ata-representation/activities/infinity-hashes/sol/README.md
…h.txt to data-representation/activities/infinity-hashes/public/the_truth.txt
…epresentation/activities/froggified/sol/README.md
…t to data-representation/activities/froggified/public/froggified.txt
…ata-representation/activities/enconding-train/sol/solution.py
…ings.txt to data-representation/activities/enconding-train/public/my_encodings.txt
There was a problem hiding this comment.
I like the challenges. The session text is also nice. Look at the README.md in the template repo. Use the same syntax for your solution READMEs:
# Activity Name: Solution
## Vulnerability
(This section may not fit. Omit it if it doesn't)
## Exploit
Describe your solution here.
And don't forget to add the challenges to the private repo as well. Follow the structure already present in the repo and in the template-internal repo.
| First, we observe that we have `binary` text, so we decode it and get the fake flag: `SSS{are_you_a_computer}`. | ||
| Next up, we see that the text looks like `ASCII`, so we decode it as `decimal`, thus getting the next fake flag: `SSS{nope_still_a_human}`. | ||
| After that, we see that all digits higher than 7 are gone, so we immediately think of `octal`, which will get us to the next fake flag: `SSS{you_look_like_you_know_linux_permissions}`. | ||
| We see a lot of `0x`s, so we know to decode from `hexadecimal` and we get to the last fake flag: `SSS{you_love_tic_tac_toe_huh}`. |
There was a problem hiding this comment.
Don't place flags in files. Let the students follow this tutorial to find them. Furthermore, this task can be solved with a script.
No description provided.