![]() |
#1
|
|||
|
|||
using x64_dbg
I am trying find the encryption seeds from a 64bit daemon, and have only experience using Ollydbg, which doesn't debug x64 binaries.
So I started using x64_dbg, but this debugger does not have a field where you can input any parameters such as "-t computer-name 4 ¨Cc license.lic" Can anybody tell me how to pass on arguments to this debugger? rgds |
#2
|
|||
|
|||
im not sure but must be something as this http://x64dbg.com/help/index.htm?page=InitDebug_initdbg_init.htm
but i think there is better use other: x64_dgb "C:\FullPathTo\File.exe" parm1 parm2 -3 -4 -debug not sure if work too: x64_dgb "C:\FullPathTo\File.exe" -t computer-name 4 –c license.lic |
#3
|
|||
|
|||
Hi Apuromafo,
Thanks but none of your suggestions seem to work, I also tried to use using InitDebug & setcommandline, but none of these pass the arguments -t computer_name 4 -c license.lic to the debugger |
#4
|
||||
|
||||
@rcer: check out the FAQ
Just append " -t computer_name 4 -c license.lic" to the current command line. These commands do not work in the command line of windows (like mafo proposed). You have to type them in the command bar (at the bottom of x64dbg). I hope this solves your issue, Mr. eXoDia
__________________
x64dbg: http://x64dbg.com My Blog: http://mrexodia.cf |
The Following User Says Thank You to mr.exodia For This Useful Post: | ||
Artic (09-08-2015) |
#5
|
|||
|
|||
thanks for the tip, but this does not work either, however using the debug - change command line menu option does work, and I am starting to like this debugger
![]() |
#6
|
|||
|
|||
rcer, try ida to debug x64 flexnet targets. Is better with windbg server, and is almost the same thing as the x86 targets.
Good hunt |
#7
|
|||
|
|||
Nikkapedd,
thanks, and I tried this, but I get the following error message when i try to invoke windbg server: "The file can't be loaded by the debugger plugin, please verify that the parameters are valid |
#8
|
|||
|
|||
rcer, you need to download the right version of windbg according with your OS. Then you have to configure ida manually to load the exe file. Open the ida.cgf and search the string: //DBGTOOLS.
Now you have to write the exact location of your windbg installation. Restart ida and you will have the working windbg server. |
#9
|
|||
|
|||
nikkapedd,
Thanks! |
![]() |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
x64_dbg Plugins | ahmadmansoor | x64 OS | 41 | 08-16-2020 15:47 |