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
I had a simple executable that was meant for a Reverse Engineering challenge. I wanted to patch a JZ to a JNZ. This worked normally with Ghidra's "Export Binary" function, however I also wanted to try this extension since it is supposed to fix some issues.
After selecting the line and running the script, the produced binary now requires Admin priveleges to run, even though it did not before (the binary produced by Ghidra previously did not have this issue).
Is this normal behaviour? I don't see why that should happen.
I am on Windows 10 21H1 with Ghidra version 10.0
The text was updated successfully, but these errors were encountered:
I had this issue too. Strangely, removing the word "patch" or "patched" from the file name removed this requirement. It seems that Windows must have a "feature" to automatically force files with the word "patch" in their name to run as administrator.
I had a simple executable that was meant for a Reverse Engineering challenge. I wanted to patch a
JZ
to aJNZ
. This worked normally with Ghidra's "Export Binary" function, however I also wanted to try this extension since it is supposed to fix some issues.After selecting the line and running the script, the produced binary now requires Admin priveleges to run, even though it did not before (the binary produced by Ghidra previously did not have this issue).
Is this normal behaviour? I don't see why that should happen.
I am on Windows 10 21H1 with Ghidra version 10.0
The text was updated successfully, but these errors were encountered: