tor-ctrl-observer - Tor Connection Destination Viewer

From Whonix
(Redirected from Tor-ctrl-observe)
Jump to navigation Jump to search

Ever wanted to know which information is sent by an application? tor-ctrl-observer shows connection information of applications using Tor.

What tor-ctrl-observer is[edit]

Ever wanted to know which information is sent by an application? tor-ctrl-observer shows connection information of applications using Tor.

Sample printout:

250-stream-status=1094 SENTCONNECT 20 firefox.settings.services.mozilla.com:443
250-stream-status=1094 SUCCEEDED 20 18.64.79.82:443

tor-ctrl-observer is especially useful in combination with Whonix because:
All traffic originating from Whonix-Workstation and Whonix-Gateway is routed over Tor. [1] [2] [3] [4] [5] [6] [7]

It operates in a secure manner by using Tor's control protocol, making visible the information that Tor internally processes and is already prepared to share with users upon request.

tor-ctrl-observer Advantages[edit]

Usage[edit]

In Whonix-Gateway.

1. Open a terminal.

2. Run tor-ctrl-observer.

tor-ctrl-observer

3. Terminate tor-ctrl-observer with signal SIGINT.

Press keyboard keys Ctrl + C.

What tor-ctrl-observer is not[edit]

tor-ctrl-observer does not attempt to be, is not, and cannot be a:

  • Network-level leak test replacement: tor-ctrl-observer only requests connection information from Tor itself. While Tor generally provides this information, if there were bugs in the Tor control protocol, tor-ctrl-observer would not detect them. Similarly, if connections bypass Tor, Tor is unaware of them, and therefore tor-ctrl-observer cannot observe such connections.
  • Tor auditor: For the same reason as above, tor-ctrl-observer cannot be expected to identify bugs in Tor.
  • Tor Controller: Unlike tools such as Nyx, nyx provides details on Tor circuits (Bridges, Tor Entry Guards, and middle or exit relays), but does not show final connection destinations. Conversely, tor-ctrl-observer displays information about final connection destinations.

Forum Discussion[edit]

Tor-ctrl-observer discussion on Whonix forumsarchive.org iconarchive.today icon

See Also[edit]

Footnotes[edit]

  1. Starting from Whonix version 0.2.1, traffic from Whonix-Gateway is also routed over Tor. This approach conceals the use of Whonix from entities monitoring the network.
  2. For preserving the anonymity of a user's Whonix-Workstation activities, it isn't essential to route Whonix-Gateway's own traffic through Tor.
  3. For those interested: Altering DNS settings on Whonix-Gateway in /etc/resolv.conf only impacts DNS requests made by Whonix-Gateway's applications that utilize the system's default DNS resolver. By default, no applications on Whonix-Gateway that generate network traffic utilize this default resolver. All default applications on Whonix-Gateway that produce network traffic (like apt, systemcheckarchive.org iconarchive.today icon, sdwdate) are explicitly configured, or force by uwt wrappers, to use their dedicated Tor SocksPort (refer to Stream Isolation).
  4. Whonix-Workstation's default applications are configured to use dedicated Tor SocksPorts (see Stream Isolation), avoiding the system's default DNS resolver. Any applications in Whonix-Workstation not set up for stream isolation - such as nslookup - will employ the default DNS server configured in Whonix-Workstation (through /etc/network/interfaces), which points to Whonix-Gateway. These DNS requests are then redirected to Tor's DnsPort by the Whonix-Gateway firewall. Changes in Whonix-Gateway's /etc/resolv.conf don't influence Whonix-Workstation's DNS queries.
  5. Traffic produced by the Tor process, which by Debian's default operates under the user debian-tor originating from Whonix-Gateway, can access the internet directly. This is permitted because Linux user account debian-tor is exempted in the Whonix-Gateway Firewall and allowed to use the "regular" internet.
  6. Tor version 0.4.5.6 (with no changes announced at the time of writing), the Tor software predominantly relies on TCP traffic. For further details, see Tor wiki page, chapter UDP. For DNS, please refer to the next footnote.
  7. Tor doesn't depend on, nor uses a functional (system) DNS for most of its operations. IP addresses of Tor directory authorities are hardcoded in the Tor software by Tor developers. Exceptions are:
    • Proxy settings that use proxies with domain names instead of IP addresses.
    • Some Tor pluggable transports such as meek lite, which resolves domains set in url= and front= to IP addresses or snowflake's -front.

We believe security software like Whonix needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 13 year success story and maybe DONATE!