From 821b81f28afd85eeb51d67fecda29ff77036c9b3 Mon Sep 17 00:00:00 2001 From: mli Date: Sun, 26 Jan 2020 23:39:35 +0100 Subject: [PATCH] fix links --- writeups/mli/hxp-36c3-ctf.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/writeups/mli/hxp-36c3-ctf.md b/writeups/mli/hxp-36c3-ctf.md index 0fb207b..f1c7e69 100644 --- a/writeups/mli/hxp-36c3-ctf.md +++ b/writeups/mli/hxp-36c3-ctf.md @@ -155,9 +155,9 @@ I kept track of the map using an array and printed it on each move): ### Solution/Exploit -Code which I used to connect/walk around/store state locally see +Code which I used to connect/walk around/store state locally see [exploit.py](hxp-36c3-ctf/exploit.py) -I wrote all characters of the flag (well all which I encountered) to this file: , for example the output from one run was `[['f', 'h'], ['f', 'x'], ['f', 'n'], ['f', 'p'], ['f', 'n'], ['f', 'w']]` (we can see some of the characters of the actual flag `hxp{and_n0w_try_t0_c4tch_m3_w1th0ut_dy1ng}`). Unfortunately I did not manage to find out the order of the flag characters. +I wrote all characters of the flag (well all which I encountered) to this file: [flagchars.txt](hxp-36c3-ctf/flagchars.txt), for example the output from one run was `[['f', 'h'], ['f', 'x'], ['f', 'n'], ['f', 'p'], ['f', 'n'], ['f', 'w']]` (we can see some of the characters of the actual flag `hxp{and_n0w_try_t0_c4tch_m3_w1th0ut_dy1ng}`). Unfortunately I did not manage to find out the order of the flag characters. I did not find out the whole flag. This is a good writeup: - this guy was more intelligent than me and dumped the map automatically using an A* path algorithm (to find all the pits). He used the algorithm also to walk to a tile he wanted to go after having the pits he had to avoid. It was then easy to find out that there are 42 flag characters running around in the map (count until `Congrats, you caught the whole flag.`). The writeup author also found out that the seed which fed the randomness determing the flag characters is time.time() - and ran the same game locally feeding this seed as input to find out the actual character positions. The flag turned out to be `hxp{and_n0w_try_t0_c4tch_m3_w1th0ut_dy1ng}`. -- 2.43.0