You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2020-01-15-Analyzing-ELF-Binaries-with-Malformed-Headers-Part-3-Solving-A-Corrupted-Keygenme.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -142,7 +142,7 @@ An explanation of the various components of this script is given in the "Analysi
142
142
I will state here though that the most conceptually difficult part of the challenge was determining how to use angr to read a symbolic variable
143
143
representing the password from inside a symbolic file. This is handled in lines 29 - 35 in the script. The trick is to pass the name of the symbolic file as an
144
144
argument when creating the initial program state instead of the pathname of the real file, and then insert this symbolic file into the emulated filesystem
145
-
prior to emulation. When angr emulates the program, the symbolic file will be opened instead of the real password file. The symbolic variable representing the variable will then be read and
145
+
prior to emulation. When angr emulates the program, the symbolic file will be opened instead of the real password file. The symbolic variable representing the password will then be read and
146
146
eventually have solutions computed for it.
147
147
148
148
The file containing the password is called "key.txt", as stated in the code comments. The `G00d P422w0rd` and `B4d P422w0RD` messages are written to this same file,
0 commit comments