From 89108a1a02a8f4da29d16951ae3841ce45f00c73 Mon Sep 17 00:00:00 2001 From: "SECURED.ORG" Date: Tue, 21 Nov 2017 17:45:03 -0800 Subject: [PATCH] Update challenge3.md --- flareon4/challenge3.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/flareon4/challenge3.md b/flareon4/challenge3.md index 144c4a3..ad8d191 100644 --- a/flareon4/challenge3.md +++ b/flareon4/challenge3.md @@ -40,7 +40,7 @@ for i in range(size): The 4011E6 will then take the answer array in reverse and do some bit shifting while chaining addition based on 2 bytes because of the usage of ax and cx. This value will eventually equal to 0xFB5E. ![alt text](https://securedorg.github.io/flareon4/images/ch3_aglo.png "algorithm") -Once the answer array runs through the algorithm, and passes the check against 0xFB5E, it will jump to the beginning of the newly modified answer array. This will end up being assembly instructions. If you are making a simple python script, you can use capstone to simply disassembly the new bytes. However, you can always just perform normal debugging. +Once the answer array runs through the algorithm, and passes the check against 0xFB5E, it will jump to the beginning of the newly modified answer array. This will end up being assembly instructions. If you are making a simple python script, you can use capstone to simply disassemble the new bytes. However, you can always just perform normal debugging. The script below brute forces the character "flag" and also disassembles the modified bytes. @@ -98,4 +98,4 @@ for char in range(0, 255): insn.op_str, c)) ``` -[Challenge 2 <- Back](https://securedorg.github.io/flareon4/challenge2) | [Next -> Challenge 4](https://securedorg.github.io/flareon4/challenge4) \ No newline at end of file +[Challenge 2 <- Back](https://securedorg.github.io/flareon4/challenge2) | [Next -> Challenge 4](https://securedorg.github.io/flareon4/challenge4)