Package: tor Version: 0.4.9.11-1~questing+1 Architecture: amd64 Maintainer: Peter Palfrader Installed-Size: 3722 Depends: libc6 (>= 2.38), libcap2 (>= 1:2.10), libevent-2.1-7t64 (>= 2.1.8-stable), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 0.0.0~20120605), libssl3t64 (>= 3.0.0), libsystemd0, libzstd1 (>= 1.5.5), zlib1g (>= 1:1.1.4), adduser, lsb-base Recommends: logrotate, tor-geoipdb, torsocks Suggests: mixmaster, torbrowser-launcher, socat, apparmor-utils, nyx, obfs4proxy Conflicts: libssl0.9.8 (<< 0.9.8g-9) Homepage: https://www.torproject.org/ Priority: optional Section: net Filename: pool/main/t/tor/tor_0.4.9.11-1~questing+1_amd64.deb Size: 1395426 SHA256: b1bc48718fade16928f815c97e8f785bef3f91cf93697d220683be0ff711a52f SHA1: 7a12afe5cf08ae249750cd3b6dc771ac2c2ba28e MD5sum: 9fe2762c432417d0b96fd8f3f0499bc0 Description: anonymizing overlay network for TCP Tor is a connection-based low-latency anonymous communication system. . Clients choose a source-routed path through a set of relays, and negotiate a "virtual circuit" through the network, in which each relay knows its predecessor and successor, but no others. Traffic flowing down the circuit is decrypted at each relay, which reveals the downstream relay. . Basically, Tor provides a distributed network of relays. Users bounce their TCP streams (web traffic, ftp, ssh, etc) around the relays, and recipients, observers, and even the relays themselves have difficulty learning which users connected to which destinations. . This package enables only a Tor client by default, but it can also be configured as a relay and/or a hidden service easily. . Client applications can use the Tor network by connecting to the local socks proxy interface provided by your Tor instance. If the application itself does not come with socks support, you can use a socks client such as torsocks. . Note that Tor does no protocol cleaning on application traffic. There is a danger that application protocols and associated programs can be induced to reveal information about the user. Tor depends on Torbutton and similar protocol cleaners to solve this problem. For best protection when web surfing, the Tor Project recommends that you use the Tor Browser Bundle, a standalone tarball that includes static builds of Tor, Torbutton, and a modified Firefox that is patched to fix a variety of privacy bugs. Package: tor-geoipdb Source: tor Version: 0.4.9.11-1~questing+1 Architecture: all Maintainer: Peter Palfrader Installed-Size: 24894 Depends: tor (>= 0.4.9.11-1~questing+1) Breaks: tor (<< 0.2.4.8) Replaces: tor (<< 0.2.4.8) Homepage: https://www.torproject.org/ Priority: optional Section: net Filename: pool/main/t/tor/tor-geoipdb_0.4.9.11-1~questing+1_all.deb Size: 2678142 SHA256: 2c8f936bae94a39bbb2d949faeedb1ba27ff307f52cc334b693c1380fd87b5aa SHA1: 16a3f05884c0a1480ec86fdcae411951cb1103ee MD5sum: 8ab5c5aae560fe8c673d92347e38a285 Description: GeoIP database for Tor This package provides a GeoIP database for Tor, i.e. it maps IPv4 addresses to countries. . Bridge relays (special Tor relays that aren't listed in the main Tor directory) use this information to report which countries they see connections from. These statistics enable the Tor network operators to learn when certain countries start blocking access to bridges. . Clients can also use this to learn what country each relay is in, so Tor controllers like arm or Vidalia can use it, or if they want to configure path selection preferences.