Getting the command line parameters of an executable

[dummzeuch 1386]

I'm currently trying to reverse engineer a tool that consists of a frontend with a really dreadful GUI and a command line program as backend, which is called by that frontend and does the actual work. The idea is to write my own frontend that does some additional preparatory work, then calls the backend and …

 

Read on in the blog post.

Edited April 20, 2023 by dummzeuch

[DJof SD 13]

Thank you for posting the note here and the BLOG entry. It just might be a tool that can help me solve a little problem.

[Fr0sT.Brutal 897]

You're lucky the backend is not controlled via STDIN 🙂

[Der schöne Günther 306]

Why? I think that is actually a pretty decent way.

[dummzeuch 1386]

3 hours ago, Der schöne Günther said:

Why? I think that is actually a pretty decent way.

But quite difficult to reverse engineer. At least compared to the backend just being started with command line parameters.

Actually I'm thinking about also tunneling stdin/out/err with the tool. Stdout is actually used by the backend to pads status information back to the frontend.

Edited April 21, 2023 by dummzeuch

[Fr0sT.Brutal 897]

2 hours ago, Der schöne Günther said:

Why? I think that is actually a pretty decent way.

It's quite simple for backend - if it just a simplest "read input-process-write output-exit or repeat" tool but it's messy for frontend and if you have to be async. Nothing serious of course but lots of non-funny stuff