commit 24c7090631c941e9be5c86755037998a3ab02acf
parent 413e5c55f8ed8ae1b1885eae05062f556050412a
Author: Louis Burda <quent.burda@gmail.com>
Date: Sat, 13 Apr 2024 18:25:05 +0200
Update notes
Diffstat:
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/solve/notes b/solve/notes
@@ -16,9 +16,15 @@ to avoid another blowup, we use lazy evaluation.
a hacky way to get simulation state output is to use sigalarm and reschedule in the
handler. more standard way is logging.getLogger("..").setLevel(logging.DEBUG)
-
if angr just fails and you know it should be possible - its probably more
-advanced crypto that you would not be able to reverse with symbolic execution anyways
+advanced crypto that you would not be able to reverse with symbolic execution anyways.
+z3 fails silently - love it!
the binarydb is fucked, bad signature matching caused the md5 function to look
like it was caused address sanitizer compile..
+
+for future interest, the binary in the bndb is patched incorrectly!
+
+always google those constants quickly, before wasting time
+
+find out its md5, brute with hashcat after removing two candidates.. 5 min on gtx970
