|
5 of the 7 most recent threads in this section are created by you. Do you have to create a thread for each and every question? Many of them are fixed by yourself in minutes. Maybe I'm the only one, but it does annoy me.
@topic:
I guess that there are two approaches (or at least two reasonable approaches I can think of):
1) Hook send / recv or any other socket function that is used by the target. The socket (id) is simply passed to your hook function. If the function is called from different places / with different sockets, try to figure out in which context (e.g. return address) the function is called with the socket you need.
2) Reverse the target and find out where the socket is saved. It has to be saved somewhere as the target needs it to call the socket function with it. If you got the location, you can simply read it. While reversing, you may breakpoint / watch the socket function and their contexts, so the first approach might be an intermediate step to this (imo more elegant) method.
With best regards
Jeoni
|
