search

nyxnor / tor-ctrl

Raw use of tor's controller
Other
5 stars 3 forks source link

tor-ctrl-stream not showing all fields of streams #18

Closed nyxnor closed 2 years ago

nyxnor commented 2 years ago

from https://github.com/nyxnor/tor-ctrl/issues/13#issuecomment-1016432749

Adrelanos said: I didn't know what that IP is. Can be found on search engines (check.torproject.org) but that isn't comfortable to find out about unwanted connections. Could you please add reverse DNS as an additional field?

The case is that GETINFO stream-status just show one line per request and change at every new stream update, and that is horrible, very different than GETINFO circuit-status that dumps a lot of lines. Maybe because stream time of life is much shorter than circuits, but anyway... Removing sleep time does not solve it :(, the streams updates faster than that loop can run. So don't know yet what to do here.

About resolving dns, I don't want to send another request to tor-resolve or listening ADDRMAP as I tried here, I would prefer to not use GETINFO stream-status, the method I wish it worked was to show raw streams with SETEVENTS STREAM without closing the connecitons.

nyxnor commented 2 years ago

the major problem of this issue was fixed with changing the mode of tor-ctrl -w from enter to INT signal. Commit coming soon.

nyxnor commented 2 years ago

now it will be print the whole stream event, there are sensitive fields there such as SOCKS_USERNAME and SOCKS_PASSWORD contents if any.

@adrelanos if that is not what the behavior you wante, reopen the issue.

nyxnor commented 2 years ago

trap kill 0 is not killing all process running on the background called by the script, this is printing async replies even after quiting the script.