


# These defaults are taken from /usr/share/tor/tor-service-defaults-torrcĬookieAuthFile /var/run/tor/thcookie # /usr/share/tor/tor-service-defaults-torrc.anondist-orig # You can find the original upstream tor-service-defaults-torrc under # which will override the defaults found here. # Please use "/etc/tor/torrc" for your custom configuration, # Copyright (C) 2012 - 2014 Patrick Schleizer $$$$ /usr/share/tor/tor-service-defaults-torrc This is optional, note that is not used in the “whonix gw” VM.arm and vidalia use this protocol to communicate with the TOR client.the TOR control protocol should be used, as defined in control-spec.txt.an application can connect to this port and control or get status information from the TOR client.by properly configuring “iptables”, a system can redirect all or some TCP/IP connections though this port.similar to SOCKSPort but used for “transparent proxies”, for example “iptables”.client applications can use this port to perform DNS requests anonymously, whithout needing to use UDP.Tor Browser, IRC: XChat, Mail: Thunderbird with TorBirdy, Instant Messenger, apt-get, gpg, ssh, git, Network Time Synchronization, wget, whonixcheck, BitCoin, TorChat, aptitude, yum, Tor Messenger’s default port.for example, “whonix gw” defines SOCKSPorts for.multiple SOCKSPort can be defined, for multiple isolation levels for different applications.the user can specify circuit isolation flags.the default SOCKS proxy port for TOR is 9050.a “TORified” application should use one of these ports.clients connecting to one of the SOCKS proxy services can have access to the TOR network, as the TOR client will forward their requests trough the TOR network to the final server in the internet.opens a listening socket for SOCKS proxy to the TOR network.I would mention the following configuration options:
#Tor messenger gpg full
You can check the full documentation for torrc files at There are interesting configuration options here. In the “whonix” scenario, it also uses includes the /usr/share/tor/tor-service-defaults-torrc file, so the script also gets that file’s contents. This is the main configuration file file for TOR. We can see the contents of the /etc/tor/torrc file. # Enable Tor through whonixsetup or manually uncomment "DisableNetwork 0" by # /usr/share/tor/tor-service-defaults-torrc # Anything here will override Whonix's own Tor config customizations in # Please see /etc/tor/torrc.examples for help, options, comments etc. # Use this file for your user customizations. # See the file COPYING for copying conditions. $$$$ Analyzing local host TOR environment. More specifically, let’s look at the results for a “whonix gw” virtual machine (Debian). In this second post, I will be analyzing the “ TOR client” installed components in a Linux host, using torhost_report.rb for that purpose.
#Tor messenger gpg series
In the first post in this series I presented the torhost_report.rb reporting script (see original post).
